Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* Re: [libre-riscv-dev] 2pm UK time, 17 Jun 2020: Marketnext hackathon preliminary setup and introduction call
From: Yehowshua @ 2020-06-15 18:27 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <D4D469BD-1020-4A85-BEE2-E31A1384BB51@getmailspring.com>



> On Jun 15, 2020, at 2:26 PM, Cole Poirier <colepoirier@gmail.com> wrote:
> 
>>> 
>>> That’s 9PM EST for me.
>>> I’d be glad to hop on.
>> 
>> fantastic.  anyone else?
> 
> Me. 6pm PDT. I'll create a bug report under libre-soc-org

Hold up - meant to say AM. 9AM for me, 6AM for you.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] 2pm UK time, 17 Jun 2020: Marketnext hackathon preliminary setup and introduction call
From: Cole Poirier @ 2020-06-15 18:26 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDw3atuUZ7=fXffyF5u8XXxVUqB+bixm_zg-uaVrys_C1g@mail.gmail.com>

On Jun 15 2020, at 11:09 am, Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:

> On Mon, Jun 15, 2020 at 6:56 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>>  
>>  
>> > if anyone else has time to participate and help pass on knowledge and
>> > answer questions that would be really helpful.  i will follow up with
>> > the call dial-in details when i have them.
>>  
>> That’s 9PM EST for me.
>> I’d be glad to hop on.
>  
> fantastic.  anyone else?

Me. 6pm PDT. I'll create a bug report under libre-soc-org.

Cole

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] 2pm UK time, 17 Jun 2020: Marketnext hackathon preliminary setup and introduction call
From: Luke Kenneth Casson Leighton @ 2020-06-15 18:09 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <AA933562-3783-4FC8-82C7-2ABBD41F57C8@gatech.edu>

On Mon, Jun 15, 2020 at 6:56 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
>
> > if anyone else has time to participate and help pass on knowledge and
> > answer questions that would be really helpful.  i will follow up with
> > the call dial-in details when i have them.
>
> That’s 9PM EST for me.
> I’d be glad to hop on.

fantastic.  anyone else?

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] 2pm UK time, 17 Jun 2020: Marketnext hackathon preliminary setup and introduction call
From: Yehowshua @ 2020-06-15 17:55 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxH=e1vAqcJe6+2f0E7sAv1f4uKzFeUXp=kvLE=OEnobA@mail.gmail.com>


> if anyone else has time to participate and help pass on knowledge and
> answer questions that would be really helpful.  i will follow up with
> the call dial-in details when i have them.

That’s 9PM EST for me.
I’d be glad to hop on.

Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] 2pm UK time, 17 Jun 2020: Marketnext hackathon preliminary setup and introduction call
From: Luke Kenneth Casson Leighton @ 2020-06-15 17:53 UTC (permalink / raw)
  To: Libre-RISCV General Development

we've got a time and a date for the Marketnext introduction.  there
are 8 people / teams confirmed as interested to participate from:

* india
* germany
* france

we are setting a time of 2pm so that there is the possibility of
everyone and anyone else joining in to help go over things, introduce
these potential people to the tasks, and the project in general.  also
to get them up-to-speed with the development environment (thank you
Cole for setting up the scripts for that).

if anyone else has time to participate and help pass on knowledge and
answer questions that would be really helpful.  i will follow up with
the call dial-in details when i have them.

l.

---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Minerva L1 Cache
From: Yehowshua @ 2020-06-15 16:57 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwEQdkfJ+OiN4KTEr3SD8FhVQE0T0Z+1vJek_pi0W_etg@mail.gmail.com>


> maybe.  we will have to evaluate it.  as i explained in the crossover
> message there are other higher priority design requirements that are unique
> and specially required for the design.

I watched the video and read through the pages.
I understood high level what is going on - the details are 
not entirely clear to me at this stage.

At some point, I can imagine that you’ll want to connect
up the memory systems. How much labor do you think 
is needed for this? Assuming I’m free starting at the end of July,
It would probably take me a couple weeks to catch up to speed
on the intricacies of the scoreboard.

Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Minerva L1 Cache
From: Yehowshua @ 2020-06-15 16:46 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwEQdkfJ+OiN4KTEr3SD8FhVQE0T0Z+1vJek_pi0W_etg@mail.gmail.com>

> 
> maybe.  we will have to evaluate it.  as i explained in the crossover
> message there are other higher priority design requirements that are unique
> and specially required for the design.

I watched the video and read through the pages.
I understood high level what is going on - the details are 
not entirely clear to me at this stage.

At some point, I can imagine that you’ll want to connect
up the memory systems. How much labor do you think 
is needed for this? Assuming I’m free starting at the end of July,
It would probably take me a couple weeks to catch up to speed
on the intricacies of the scoreboard.

Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] daily kan-ban update 15jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-15 15:11 UTC (permalink / raw)
  To: Libre-RISCV General Development

yesterday:

* sorted byte-reversal issue in LD/ST sim code, matched against qemu,
sorted the hardware to match (including lbrrx)
* added budgets to the NLNet Wishbone Grant which cover documentation
and the POWER9 core.
* added a new list libre-soc-bugs and moved bugzilla-daemon to report
all bugreports to that new list (*not* libre-riscv-dev)
* investigated and tracked down a wishbone SRAM slave that will help
us do testing.

today:

* added in the LD/ST unit tests into test_core.py and disabled them
pending an investigation into why the LDSTCompUnit remains "busy"
after the 1st instruction.

rest of day:

* look at why the 2nd LD/ST instruction remains "busy" in test_core.py
where in the test_ldst_compunit.py it is fine
* if that's found quickly, continue investigating the next step which
is to first add in an instruction "reader" (I-Cache path) and second
to point the PC at it and actually get instructions from an actual
I-Cache / SRAM.

with so many unit tests demonstrating functionally correct behaviour
of the various instructions (corner-cases notwithstanding) i should
have actual basic program execution pretty much straight away.

l.

---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Minerva L1 Cache
From: Luke Kenneth Casson Leighton @ 2020-06-15  4:32 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <909D7BCD-8ADB-438F-BCA7-44437DC92A99@gatech.edu>

On Monday, June 15, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

>
> > I’m currently working on writing a Minerva like nMigen
> > cache that supports as many sets as desired - hopefully
> > we can use that.
>
> I need a cache with arbitrary amount of sets for my thesis
> anyways


ah ok now this makes sense.


>  so - might be useful in a LibreSOC context too.


maybe.  we will have to evaluate it.  as i explained in the crossover
message there are other higher priority design requirements that are unique
and specially required for the design.

l.



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Minerva L1 Cache
From: Luke Kenneth Casson Leighton @ 2020-06-15  4:30 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <FD000400-6178-4570-836F-709FE3F468C0@gatech.edu>

On Monday, June 15, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

> And more generally, if I understand things correctly:
> Our memory architecture is the following?
>
> cpu -> MMU -> L1 Cache -> main memory?


the diagram i drew, which took several weeks to design and review on here
and comp.arch, which i have referred you to a couple of times but have
noted each time, puzzlingly, did not result in any engagement or questions,
contains the layout.

i wondered if perhaps this is because this is a high traffic list and you
have been so busy on other important things.

here is the page again:

https://libre-soc.org/3d_gpu/architecture/memory_and_cache/

there are other locations and discussions however this diagram is key.

the multiple LDST CompUnits can produce up to *SIXTEEN* 64 bit LDST
requests.

these are "funneled", grouped, and directed to *separate* odd/even L1
Caches, each being 128 bit wide.  the split decision uses bit 4 of the
address.

the TLB and MMU i have not been able to get to because there is so much
else to do, first.

without that funneling (merging) we simply could not meet a GPU workload.

All LDST operations (all 16 of them) have the potential to be merged in a
single cycle.  in reality only 8 are likely to be merged.

it is important therefore to appreciate that this architectural strategy
has been designed and evaluated over a 2 year period to give "reasonable"
64 bit scalar performance, yet 2 to 4x that performance if certain criteria
are met such as if FP32 sequential (element atrided) vector workloads are
issued.

this eliminates many of the N to N crossbars that would obliterate any
chance of us being able to claim low power consumption as well as make the
routing and layout absolute hell.

it really is a hybrid VPUGPUCPU not a "CPU pretending to be a GPU" or the
other way round.

l.




-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Minerva L1 Cache
From: Luke Kenneth Casson Leighton @ 2020-06-15  4:04 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <8A42B0DD-1009-49A4-AEB9-DBE04836FAAE@gatech.edu>

On Monday, June 15, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

> I was running through the nMIgen Minerva Cache
> codebase and would like to point out that it only
> has support for two sets.


yes.  this was noted and discussed a couple of months ago.

 It can have an arbitrary
> amount of tags, but is fixed at two sets which is
> probably notably too low performance for what
> we want.
>
> I’m currently working on writing a Minerva like nMigen
> cache that supports as many sets as desired - hopefully
> we can use that.


that would be great, if we were only doing a high performance general
purpose vector engine, because general purpose compute workloads have
unpredictable data characteristics for which multiple sets would be an
ideal solution.

for GPU workloads it is important to appreciate that to be useful.and
useable, there is more involved than just designing a set upgrade, which
needs to be discussed and understood before spending time doing work.

no disrespect intended: do you not feel that it would have been better to
ask that, particularly on a complex project that has had over 2 years
architectural design work done on it, and on which you have not had time to
get up to speed?

there is no problem highlighting a potential performance flaw however going
direct from that to an announcement to start work, without consultation or
evaluation, is... puzzling.

to explain (summarising detailed and indepth discussions that have taken
place over the past year and a half, learning from many different people):

because we are splitting into twin L1 caches, and because GPU parallel
non-overlapping workloads (particularly texture data) make ineffective use
of L1 caches, expanding the tag size may not be of as much value as might
otherwise be expected.

it would be much more useful to add "cache line pinning" such that a GPU
workload only uses a fractional percentage of the cache.

this would stop a massively parallel non-overlapping workload from flooding
the L1 Cache with data that is neverrrr going to be referred to agai.

i discussed this only 2 days ago.

in earlier discussions before that, which you have also not seen, i
suggested simply modifying the minerva one (keeping the formal correctness
proof functional is a critical part of the project, and they are very hard
to write).

we need arbitrary bitwidth as well.  128 bit minimum and the option of 256
bit for later.

also it is imperative to have the L1 cache support individual byte-enable
lines *not* a single overwrite/update line.

this because the byte enable lines are a critical part of the L0CacheBuffer
merge strategy for Vector workloads.

if you check the L0/L1 Cache diagram i drew out, the plan is to connect a
*pair* of 64 bit wishbone interfaces to the L1 cache (ignoring that there
are two L1 D Caches for now)

each pair is individually activated based on whether any of the 8
byte-enable lines are activated.

thus if there is a cache flush and only the top 64 bits have changed only
one 64 bit wishbone write is required.

these byte-enable (wen) lines directly correspond with wishbone byteselect
lines.

bottom line, feel free to spend the time doing that work if you so choose
however i have to advise you in advance that it is unlikely to be useful
and consequently the chances of receiving NLNet donations for completing it
are slim.

it *might* be useful for the ICache however this again will need evaluation
and discussion under a bugreport i.e. following software engineering
practices rather than arbitrarily going ahead without consultation.  once
consensus is reached as to the potential usefulness, then a budget could be
allocated.

i am raising an eyebrow here at this puzzling action however do not wish to
discourage you, merely steer and redirect your energies and initiative to
somewhere productive that will help us achieve our goal on this complex
project.

if you have any questions about the architecture which took 2 years to plan
and design please do ask them.  also if you would like to ask what would be
useful to work on, that is within your skillset, that you would enjoy,
please also do so without hesitation.

sorry to have to point all of these things out.

l.



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Minerva L1 Cache
From: Yehowshua @ 2020-06-15  3:24 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <8A42B0DD-1009-49A4-AEB9-DBE04836FAAE@gatech.edu>

> 
> I was running through the nMIgen Minerva Cache
> codebase and would like to point out that it only 
> has support for two sets. 

Pardon me. This should have said two ways.
Line 18 in cache.py

Yehowshua

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Minerva L1 Cache
From: Yehowshua @ 2020-06-15  3:09 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <8A42B0DD-1009-49A4-AEB9-DBE04836FAAE@gatech.edu>

And more generally, if I understand things correctly:
Our memory architecture is the following?

cpu -> MMU -> L1 Cache -> main memory?

Yehowshua

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Minerva L1 Cache
From: Yehowshua @ 2020-06-15  3:02 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <8A42B0DD-1009-49A4-AEB9-DBE04836FAAE@gatech.edu>


> I’m currently working on writing a Minerva like nMigen 
> cache that supports as many sets as desired - hopefully
> we can use that.

I need a cache with arbitrary amount of sets for my thesis
anyways so - might be useful in a LibreSOC context too.

Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] Minerva L1 Cache
From: Yehowshua @ 2020-06-15  2:41 UTC (permalink / raw)
  To: Libre-RISCV General Development

I was running through the nMIgen Minerva Cache
codebase and would like to point out that it only 
has support for two sets. It can have an arbitrary
amount of tags, but is fixed at two sets which is 
probably notably too low performance for what 
we want.

I’m currently working on writing a Minerva like nMigen 
cache that supports as many sets as desired - hopefully
we can use that.

Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] bugzilla tracking messages now moved to libre-soc-bugs@libre-soc.org
From: Luke Kenneth Casson Leighton @ 2020-06-15  1:17 UTC (permalink / raw)
  To: Libre-RISCV General Development

as per subject.

if you would like to keep track of the bugreports list, it is now separate
and you will need to subscribe to it, explicitly.

archives are at lists.libre-soc.org.

publicinbox is subscribed to it so there is a git backed archive which you
can also checkout, this needs confirming however.  i will follow up later.

l.






-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 385] ReservationStations MultiCompUnit unit test needed
From: bugzilla-daemon @ 2020-06-15  0:32 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-385-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=385

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|lkcl@lkcl.net               |cestrauss@gmail.com

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 385] New: ReservationStations MultiCompUnit unit test needed
From: bugzilla-daemon @ 2020-06-15  0:29 UTC (permalink / raw)
  To: libre-riscv-dev

https://bugs.libre-soc.org/show_bug.cgi?id=385

            Bug ID: 385
           Summary: ReservationStations MultiCompUnit unit test needed
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: Other
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

a version of test_inout_mux_pipe.py, similar to the unit tests for IEEE754FP,
is needed that uses MultiCompUnit.

where the IEEE754FP and inoutmux tests will send in tracked data and match it
up, the next phase is to put MultiCompUnit frontends on those and send and
receive data via the MultiCompUnit protocol.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 336] ALU CompUnit needs to recognise that RA (src1) can be zero
From: bugzilla-daemon @ 2020-06-14 23:42 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-336-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=336

--- Comment #60 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cesar Strauss from comment #59)
> Created attachment 64 [details]
> Suggested pipeline design for the ALU Comp Unit
> 
> (In reply to Luke Kenneth Casson Leighton from comment #58)
> > (In reply to Cesar Strauss from comment #57)
> > > I don't really recall being much afflicted by this sort of issue. But then,
> > > I normally try to avoid using latches as much as possible, this may be the
> > > reason.
> > 
> > yyeah they're not a "normal" way to do FSMs.  however with some aspects being
> > combinatorial and some being sync, we can't use "standard" techniques.
> 
> Did you consider implementing the ALU CompUnit as a pipeline?

you mean, MultiCompUnit itself?  if so: this would violate the mission-critical
protocol, the purpose for which MultiCompUnit exists.

MultiCompUnit *must not* abandon its data.  its absolutely must track the
operands from start to finish.

we call this a "Phase-aware Function Unit".  "phase-aware" because it
absolutely
has to keep track of the start time and completion time.
failure to do so would be absolutely disastrous.

a pipeline *abandons* its data.  it says "here, you deal with it, i'm
abdicating
all responsibility for data-tracking".  i.e. once the data is in the pipeline,
there is *no hardware* in the actual pipeline itself which tracks or handles
responsibility for tracking the completion of that result.

this was the subject of a rather excruciating discussion on comp.arch: it
became
clear that there simply does not exist an Industry-standard or Computer Science
term that covers "Function Units which track data from operand to result".

one had to be invented, and the best that could be thought of was "Phase-aware
Function Unit"

for an out-of-order system, it is absolutely imperative that we have
Phase-aware Function Units, and that "management" task is what MultiCompUnit
is for.

a pipeline *cannot* fulfil that role.  by definition and by design.

however.... MultiCompUnit can *MANAGE* pipelines... by using the ready/valid
protocol.

and if we have multiple MultiCompUnit front-ends onto a single pipeline,
*now* we have Reservation Stations.

and that's what the ReservationStations class is for:
https://git.libre-soc.org/?p=nmutil.git;a=blob;f=src/nmutil/concurrentunit.py;hb=HEAD#l40


> I can give it a try, in parallel with other tasks. It would be a nice way to
> learn more about the pipeline API.

actually we do need a ReservationStation version of a MultiCompUnit unit test.
a 2 or 3 stage "real" but dummy pipeline (simply passing its input through to
its output, maybe doing +1 on each stage or something, or, heck, doing ADD
would be perfectly on)

then there would be 4 to 5 MultiCompUnits wired up to a ReservationStation
version
of that pipeline (see nmutil multipipe.py)

the unit test would then be an adaptation of the test_inout_mux_pipe.py test,
throwing multiple inputs in and seeing if they come out successfully at the
end.

https://git.libre-soc.org/?p=nmutil.git;a=blob;f=src/nmutil/test/test_inout_mux_pipe.py;hb=HEAD

there's some other code i can refer you to, if you're interested
(and we should raise a new bugreport for it)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 336] ALU CompUnit needs to recognise that RA (src1) can be zero
From: bugzilla-daemon @ 2020-06-14 23:21 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-336-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=336

--- Comment #59 from Cesar Strauss <cestrauss@gmail.com> ---
Created attachment 64
  --> https://bugs.libre-soc.org/attachment.cgi?id=64&action=edit
Suggested pipeline design for the ALU Comp Unit

(In reply to Luke Kenneth Casson Leighton from comment #58)
> (In reply to Cesar Strauss from comment #57)
> > I don't really recall being much afflicted by this sort of issue. But then,
> > I normally try to avoid using latches as much as possible, this may be the
> > reason.
> 
> yyeah they're not a "normal" way to do FSMs.  however with some aspects being
> combinatorial and some being sync, we can't use "standard" techniques.

Did you consider implementing the ALU CompUnit as a pipeline?

I have put some thought into it. See the attached diagram.

First, consider that rel / go protocol seems to be compatible with the valid /
ready protocol, by connecting n.ready_o->rd.rel_i and rd.go_o->n.valid_i.
Likewise on the dest port. A pass-thru stage helps, I think.

In the idle state, the switches will be set as shown, disconnecting the
pipeline from the input and output ports, connecting them instead to a full
sink and empty source respectively. So, there can be no activity on these
ports.

At issue time, you transition the dest switch from straight to crossed. Also,
in each parallel arm, choose either one of the src or imm switches to cross.

The barrier / combiner joins the input data, and outputs n.valid_o only when
both p.valid_o are active. And then, it copies n.ready_i to both p.ready_i.
This combiner takes care to inform the ALU that all its operands input are
valid.

The ALU outputs directly to the dest port. holding the data itself, according
to the protocol, until the dest port can accept it.

Notice the little need for FSMs and latches in the design. The total complexity
is divided in manageable pieces, tucked inside the pipeline stages.

If all stages work in isolation, we can be confident that the design will work
when put together.

Does it make sense?

I think it is worth investing the time to implement this. If it turns up that
it works, we can be more confident on the design. Even apply the same principle
to LDSTCompUnit.

I can give it a try, in parallel with other tasks. It would be a nice way to
learn more about the pipeline API.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-06-14 23:16 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=184

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |libre-soc-bugs@lists.libre-
                   |                            |soc.org

--- Comment #23 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
i've created libre-soc-bugs@lists.libre-soc.org
the next major task is to move almost every "cc" in all 385 bugs
over to that list (except for the new "Organisation" ones)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] effects of powered-off chip sections on current leakage
From: Cesar Strauss @ 2020-06-14 22:08 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAC2bXD6bOLp5tS0=Q27RNkP9FpA4xFmrhqv1zJCwTaGd9h1qCQ@mail.gmail.com>

Em 14/06/2020 17:07, Jacob Lifshay escreveu:
> On Sun, Jun 14, 2020, 04:31 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>> ok so if there's an actual MOSFET that cuts power to those planes,
>> there's nothing to "resist", so the idea that you came up with of
>> cutting power entirely has merit that needs a proper investigation.
> 
> 
> After a little looking around, I didn't see anything that unambiguously
> stated that turning off the power planes will reduce leakage power, however
> basically everyone I found seemed to imply that.
> 
> https://en.wikipedia.org/wiki/Power_gating

Remember also to isolate any inputs, otherwise they will tend to power
the core, and generally create a load on the line.

Happened to me the other day.

I have two board connected by I2C. I power down just one, and the power
led stays on. Power off the other instead, and the I2C bus on the first
becomes unusable.

Regards,

Cesar

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] effects of powered-off chip sections on current leakage
From: Jacob Lifshay @ 2020-06-14 20:07 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyOoEPF-bqBSAQug5Wgw1SSTbtSz7-crA1ccRtbM21QJw@mail.gmail.com>

On Sun, Jun 14, 2020, 04:31 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Sun, Jun 14, 2020 at 6:06 AM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > Please explain in more detail, perhaps with some supporting references --
> > it still makes close to zero sense to me how additional unused silicon
> area
> > could affect the rest of the chip, since that area itself couldn't be
> > drawing any power since all wires into it that are at 0V due to the power
> > rails and I/O signals being switched off.
>
> beyond the fact that it occurs, i do not know the details.  i had a
> mentor who explained it to me, and (in the case of the GPS
> correlators) a second person confirmed it.
>
> it is something to do with the fact that a transistor is not a perfect
> isolator, and that it is both a resistor and a capacitor.  the
> resistance, when there is zero power applied to the Drain, is
> extremely small but it is *not* zero, between the two planes that are
>

assuming you meant resistance is extremely large but not infinity.
extremely small means a very large current would flow.

directly above and below the transistor (one VDD - +ve voltage, one
> VSS - GND)
>

from what I understand, the leakage current is mostly caused by a
combination of gate and other insulator defects, quantum tunneling, and
minority carriers. Those basically act as a resistor between the source,
drain, and gate.

If the block is not switching, we can ignore any capacitive effects since
the capacitors won't be charging or discharging.

We will probably want a separate clock and reset domain for each power
domain.


> ok so if there's an actual MOSFET that cuts power to those planes,
> there's nothing to "resist", so the idea that you came up with of
> cutting power entirely has merit that needs a proper investigation.


After a little looking around, I didn't see anything that unambiguously
stated that turning off the power planes will reduce leakage power, however
basically everyone I found seemed to imply that.

https://en.wikipedia.org/wiki/Power_gating

Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 375] Finding new project members who can help with complex detailed work such as LDSTCompUnit
From: bugzilla-daemon @ 2020-06-14 19:35 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-375-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=375

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
this guy.

https://www.reddit.com/user/HarryHo90sHK/
https://github.com/m-labs/nmigen-soc/pull/6

except there is no obvious email address for him, online.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 382] nmigen wishbone Memory object needed
From: bugzilla-daemon @ 2020-06-14 19:14 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-382-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=382

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
found one

https://codecov.io/gh/m-labs/nmigen-soc/pull/6/diff?src=pr&el=tree#diff-bm1pZ2VuX3NvYy93aXNoYm9uZS9zcmFtLnB5


https://github.com/m-labs/nmigen-soc/pull/6

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

page:   latest

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git