Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 296] idea: cyclic buffer between FUs and register file
From: bugzilla-daemon @ 2020-05-01 20:23 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-296-13@https.bugs.libre-soc.org/>

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

--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #7)

> That's true for correctness, but not for performance. Delaying 20 cycles on
> every forwarding operation would seriously reduce the performance, probably
> by at least 10x, so, obviously, that should be avoided.

sorry, i meant, "delayed not deliberately but because the total bandwidth
(paths) between FU-result latches and FU-input latches is limited".

whether that path is via the regfile or via a forwarding bus doesn't matter:
if the forwarding bus isn't available for 5-10 cycles, there's always the
write-port on the regfile.

Mitch's analysis was, i believe, that we should expect a ratio of... what
was it... 1.3 reg reads to writes?  i.e. each result produced by one FU is
"consumed" by an average of 1.3 other FUs.

he noted that, therefore, even if the forwarding bus is used just once,
forwarding to just one other FU before the value is dropped on the floor,
in a cascade it actually saves a lot of regfile activity.

unfortunately, to reduce this regfile pressure assumes that you can detect
write-after-write and also "discards".  that *is* possible, however the
discussion was now over a year ago, and we simply haven't got time in
this round to make the necessary DM modifications.

so what we will gain with a forwarding bus is: decreased latency.  this because
with the register file being a bottleneck, even one extra bus (fwd) means that
some of the operations that would otherwise need to have waited for the write
(and followup read) through the regfile, instead may start that much earlier.

yes, ultimately: if access to that forwarding bus (which _will_ itself be
resource-contended) can be done early (same clock cycle, even), obviously that
latency is decreased much more.

summary: for a 6600-based DM system it's strongly desirable for the fwd
bus to be same (or 1 clock) cycle: it's not however a make-or-break mandatory
requirement.  for an in-order system, on the other hand, it's not only
far more difficult to *add* a forwarding bus, it is, if i recall correctly,
timing-critical.  i.e. the consequences of missing the slot are that the
entire pipeline (right the way back to issue) is forced to stall.

-- 
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 297] nmutil "flatten" function already exists
From: bugzilla-daemon @ 2020-05-01 20:51 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-297-13@https.bugs.libre-soc.org/>

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

--- Comment #1 from whitequark@whitequark.org ---
Anything that starts with _ is a private function according to Python
conventions and can be changed or removed without notice by nMigen.

-- 
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 297] nmutil "flatten" function already exists
From: bugzilla-daemon @ 2020-05-01 21:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-297-13@https.bugs.libre-soc.org/>

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

--- Comment #2 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to whitequark from comment #1)
> Anything that starts with _ is a private function according to Python
> conventions and can be changed or removed without notice by nMigen.

That's what I thought. Would you be open to changing `flatten` to a public API,
or should we just keep using the duplicate in nmutil?

-- 
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] Verilog book
From: Hendrik Boom @ 2020-05-01 21:43 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <20200501200857.urmih2lbv7bgsp3e@topoi.pooq.com>

On Fri, May 01, 2020 at 04:08:57PM -0400, Hendrik Boom wrote:
> Springer is allowing a number of books to be downloaded for free during 
> the Covid-19 pandemic.
> 
> I found the Quick Start to Verilog, in case anyone is interested:
> 
> https://link.springer.com/book/10.1007/978-3-030-10552-5

And there are a few more related books in the main book list.

> 
> The main book list is at:
> https://link.springer.com/search?facet-content-type=Book&package=mat-covid19_textbooks
> 
> -- hendrik
> 
> 
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

_______________________________________________
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 297] nmutil "flatten" function already exists
From: bugzilla-daemon @ 2020-05-01 21:55 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-297-13@https.bugs.libre-soc.org/>

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

--- Comment #3 from whitequark@whitequark.org ---
> Would you be open to changing `flatten` to a public API

Why should it be a public API of nmigen? It's a general purpose utility
function for iterables. It should be a public API of itertools, or another
package like that.

-- 
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 297] nmutil "flatten" function already exists
From: bugzilla-daemon @ 2020-05-01 22:00 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-297-13@https.bugs.libre-soc.org/>

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

Jacob Lifshay <programmerjake@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|whitequark@whitequark.org   |lkcl@lkcl.net

--- Comment #4 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to whitequark from comment #3)
> > Would you be open to changing `flatten` to a public API
> 
> Why should it be a public API of nmigen? It's a general purpose utility
> function for iterables. It should be a public API of itertools, or another
> package like that.

yeah, makes sense.

Luke, unless you want to pursue that option, I'll let you close this as
won't-fix.

-- 
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 297] nmutil "flatten" function already exists
From: bugzilla-daemon @ 2020-05-01 23:04 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-297-13@https.bugs.libre-soc.org/>

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

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
sigh.  it has to be a public function of a pacjsge... by us.  named nmutil.

-- 
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 298] consider using sum-addressed decoder in L1 cache (maybe also L1 I cache)
From: bugzilla-daemon @ 2020-05-01 23:21 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-298-13@https.bugs.libre-soc.org/>

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

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-May/006196.html

-- 
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 299] New: improve memory clash detection
From: bugzilla-daemon @ 2020-05-01 23:39 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 299
           Summary: improve memory clash detection
           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: ---

https://groups.google.com/d/msg/comp.arch/leXwF1j7Z-A/S1t_EHumAQAJ

see this message (and the one before it).

must work through to see if there is a way to combine the Mem Hazard Matrix
logic with addr match and spot interleaved LDs and STs that do not clash.

at the moment, *any* LD will stop future STs from going through.  *any* ST
likewise stops LDs from going through.

it *may* be possible to use addr match on LSBs to determine which interleaved
LDs and STs can be separated into batches of LDs and batches of STs.

-- 
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 296] idea: cyclic buffer between FUs and register file
From: bugzilla-daemon @ 2020-05-02  2:01 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-296-13@https.bugs.libre-soc.org/>

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

--- Comment #9 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://groups.google.com/d/msg/comp.arch/qeMsE7UxvlI/t6QtE4C2AQAJ

idea: one cyxlic buffer *at every FunctionUnit* and turn the buses into general
data buses.

-- 
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] Documenting the SOC tree Repository
From: Yehowshua @ 2020-05-02  3:09 UTC (permalink / raw)
  To: Libre-RISCV General Development

I’m reading the rather large SOC repository right now.
I’m creating documentation as I go along.
This may take a few weeks.

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] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-05-02  4:00 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@https.bugs.libre-soc.org/>

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

Yehowshua <yimmanuel3@gatech.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yimmanuel3@gatech.edu

--- Comment #135 from Yehowshua <yimmanuel3@gatech.edu> ---
We shouldn't be pulling the the ISA from the wiki.
This is because I can edit the Wiki and break the codebase.

-- 
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] Documenting the SOC tree Repository
From: Luke Kenneth Casson Leighton @ 2020-05-02  4:40 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <27116EB9-8FC7-4043-8328-ED7516EE6641@gatech.edu>

On Saturday, May 2, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

> I’m reading the rather large SOC repository right now.


it's not that biig.  err is it?

the IEEE754FPU one i know is around 10,000 lines.  as python projects go
that's pretty small.

I’m creating documentation as I go along.


fantastic.  i do recommend leaving out minerva except perhaps some
commentary about it at the top level, that we intend to borrow its use of
wishbone and its L1 I and D cache code, to save on both development and
unit test time.

in particular it has a formal correctness proof for the L1 cache.

sadly we didn't yet put in an NLNet grant request to cover documentation,
which we still could do if you like?


one suggestion / request, if you create a page to describe some classes
(whatever) please do cross-reference them *in the actual code*.

make sure to commit and push pretty much immediately.  under no
circumstances go "i'll commit these and wait a few days before pushing
them".


> This may take a few weeks.


not a surprise.

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] Documenting the SOC tree Repository
From: Yehowshua @ 2020-05-02  4:42 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDz8W8SsEVuZiLReHCH763LBriSWSOjs+pTMpgUo061gXA@mail.gmail.com>



> On May 2, 2020, at 12:40 AM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> 
> sadly we didn't yet put in an NLNet grant request to cover documentation,
> which we still could do if you like?

Don’t worry about NLNet for me. Should things go according to plan, I should be doing this full time come August anyways.

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] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-05-02  5:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@https.bugs.libre-soc.org/>

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

--- Comment #136 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
if someone starts doing that i will ban them, recover the wiki with a git
reversion, then add a password to the frontend to prevent it happening again.

ikiwiki was specifically chosen because of the use of git as a backend.

i prefer to trust people.

-- 
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 296] idea: cyclic buffer between FUs and register file
From: bugzilla-daemon @ 2020-05-02 13:15 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-296-13@https.bugs.libre-soc.org/>

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

--- Comment #10 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
as can be seen from the comp.arch discussion, a cyclic buffer on *each Function
Unit*
seems to have some advantages over just having a global cyclic buffer.

in particular, we discussed 18 months ago the merits of an idea by Mitch Alsup
to use *only* 1R-or-1W SRAMs on the regfile, with serial reads followed by
FMAC (the example) pipeline stages and a single write.  it's extremely
efficient
resource-utilisation on parallel workloads.

the problem with that idea is that it absolutely sucks for scalar code.

turns out that if we have a cyclic buffer and turn the "dedicated" RD1/2/3
WR1/2
Broadcast Buses into "general-purpose read / write buses", that we get the best
of both worlds:

* in the scalar case, a 3-operand FunctionUnit may use *three* Broadcast Buses
  to receive operand1, operand2 and operand3 in a single cycle

* in the parallel case (or during heavy loading) the lack of availability of
  all but one of the available buses does *not* stop a Function Unit from
  receiving its operands.  even if it takes 3 cycles to receive operands over
  just the one Bus, the fact that it will *also* take 3 cycles to rotate those
  values into the correct Operand Latches *does not matter*

(Yehowshua, this is partly where / why the extra gates of a Benes / Butterfly
Network are overkill: *all* operands need to be delivered before the operation
can proceed, which leaves time to shuffle things into place).

what does need to be thought through is to preserve the read/write
Dependencies.
the crucial one is not reads: those can drop their dependency the moment that
the operand is received (even into the cyclic buffer), however writes
definitely
cannot.

whilst they can be _delivered_ via the forwarding bus, the Function Unit *must*
remain busy (not be sent a "Go_Write" signal which will tell it to drop the
dependency) until its result has reached the regfile.

and "in any of the cyclic buffers" is *not* the regfile.

so that needs a little more thought.

-- 
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 296] idea: cyclic buffer between FUs and register file
From: bugzilla-daemon @ 2020-05-02 15:02 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-296-13@https.bugs.libre-soc.org/>

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

--- Comment #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
hmm hmm, the other big concern: just as with a Tomasulo Algorithm, the
Register "ID" (or... what was it... the CAM Row Number or something)
has to be:

(a) Broadcast onto each Common Data Bus along with the value
(b) stored in each and every Function Unit (which means getting it
    *to* that FU as well as having a comparator)

now, the trade-off between making that ID an unary number or a binary number
is:

* we will have around 20 Function Units
* there will be 5 ports (and therefore 5 CDBs: 3-read, 2-write)

therefore in binary:

* there will be 500 wires for a 5-bit RegisterID coming *in* to Function
  Units
* there will be 500 wires going *out* of Function Units onto CDBs
* 500 XOR gates will be needed to perform comparisons, and that's a power
  hit that we get on EVERY clock cycle (!)

in unary:

* there will be a whopping THREE THOUSAND wires coming in for a 32-bit
  unary RegisterID
* there will be three thousand going out onto the CDB (!!)
* there would be 3,000 AND gates needed, however the power hit will *only*
  be from a maximum of 5x20=100 of those going active in any one clock cycle
  because they're unary-encoded, and only 1/32 of the 3,200 bits is ever
  active, rather than *all* (5) bits active in the binary case.

to be honest, neither of these is particularly attractive! :)

compare and contrast this with the way that the 6600 works:

* The Register Port Buses, although global in nature, are direct-connected
  from Function Unit Operands to *specific* Regfile ports.
* A-Units (address Units) have 2-in, 1-out and those are wired to Regfile
  RD ports 1,2 and Regfile WR port 1
* B-Units (algorithmic units) i think likewise have 2-in, 1-out, and
  go to RD ports 3,4 and Regfile WR port 2
* X-Units have 1-in, 1-out and go to RD port 5 and WR port 3.

therefore:

* the FU-Regs Dependency Matrix captures the information about which regs
  *on which port* each FU shall read (or write) from
* this in an IMPLICIT fashion such that there is NO possibility for the
  value being broadcast to be picked up by a second Function Unit

i.e. the Register ID itself is *NOT* actually transmitted over the Bus,
at all.  it's just down to "information capture", back at the FU-Regs
Dependency Matrix.


i wonder... i wonder if there's a way to compute the amount of "shifting"
that would be required, by each FunctionUnit, and have *that* transmitted
to the FU, instead?  this would only be a 2-bit value (assuming a maximum
of 4 read-ports).

it goes like this:

* each row of the FU-Regs Dependency Matrix has captured (already, this
  is part of the job of the FU-Regs DM) which registers the FU requires.
  this *already* encodes which FU Operand Ports it needs
* when a CDB is available, we know its index ID.
* at the time that the CDB is available, we also know, back in the DM,
  which FU Operand Port index requires that value
* the DIFFERENCE between these two indices as binary values becomes EXACTLY
  the amount of shifting required, should the value be transmitted over
  that available CDB.

it's not a vast amount of gates (a 2-bit subtractor per FU per port) and
it's only 2 bits of information to be sent to each Function Unit.  note
however that each FU needs a *different* shift-diff value to be transmitted
to it, for each broadcast value on that CDB!

so if a 2-bit subtractor is... ermm... 10 gates(?) then that's:

* 10 (appx) gates for the subtractor (it doesn't need carry)
* times 20 for the number of Function Units
* times 5 for 3RD Operands and 2WR operands

1000 gates, as an adjunct to the FU-Regs Dependency Matrix.

however the number of wires is:

* 2 for the shift-diff value
* times 20 for FUs
* times 5 for the operands

a total of 200 wires and *that's* tolerable.

compare this to XOR being four gates, where in the binary-broadcast we'd have
5x20x5 wires (500) but we'd have two THOUSAND gates.

-- 
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] GItlab For SOC repo
From: Yehowshua @ 2020-05-02 18:45 UTC (permalink / raw)
  To: Libre-RISCV General Development

Are we currently using a gitlab mirror on our SOC repo?
I saw a ciyaml there…

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] GItlab For SOC repo
From: Yehowshua @ 2020-05-02 18:47 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <A834A1B9-5B29-411C-8EFF-75562B46B596@gatech.edu>

Also - we have some experimental files in the SOC repo.
I think it is a good practice to make an experimental branch instead.

Thoughts?

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] GItlab For SOC repo
From: Luke Kenneth Casson Leighton @ 2020-05-02 19:30 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <A834A1B9-5B29-411C-8EFF-75562B46B596@gatech.edu>

On Saturday, May 2, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

> Are we currently using a gitlab mirror on our SOC repo?


yes.  partly.   it's for CI running on salsa.




> I saw a ciyaml there…
>
> Yehowshua
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
>


-- 
---
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] Documenting the SOC tree Repository
From: Yehowshua @ 2020-05-02 20:59 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDz8W8SsEVuZiLReHCH763LBriSWSOjs+pTMpgUo061gXA@mail.gmail.com>

Also - I’d like to clean up the decoder a bit. I’ll go ahead and make a branch and push to that…

I’ll have you guys review periodically.

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] Needed Subset of POWER
From: Yehowshua @ 2020-05-02 22:07 UTC (permalink / raw)
  To: Libre-RISCV General Development

Hello all,
	I’m reading through the Power ISA manual. What subset of POWER are we doing for the first single core revision?

What is the minimal subset of POWER that we can get away with for an operational Linux kernel?

There are lots and lots of features such as:

```
Decimal Floating-Point Support Operations: Add imme- diate forms of DFP Test Significance instructions.
```

Do we have to implement all these “icing” instructions eventually to be POWER certified?

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] Documenting the SOC tree Repository
From: Luke Kenneth Casson Leighton @ 2020-05-02 23:24 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <15B29048-8343-4683-9724-85A5307A6E1B@gatech.edu>

On Saturday, May 2, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

> Also - I’d like to clean up the decoder a bit. I’ll go ahead and make a
> branch and push to that


i really do not like branches.  please, really: do not use them except
under absolute dire critically necessary circumstances.  i documented thus
in HDL_workflow.


> I’ll have you guys review periodically.


please, follow the HDL_workflow.  it is there for a reason.

use the unit tests, make sure anything you do works 100%.  work
incrementally (5 to 15 lines per commit is perfectly acceptable) and commit
directly to the master branch.  do not be afraid to make 20 to 40 commits
*a day*.  untested code that is comoletely unused is perfectly fine.

yes it means that you really do have to be certain that what you commit is
going to work, and that's the whole point.

by working in master, you *have* to be strict, keep to small changes, and
keep constantly in touch.

not "periodically commit because i'm hiding what i am working on because i
don't want anyone to see it in case they criticise it because it's neither
perfect nor complete"

that is *not* collaboration!

so if you find that you are not 100% confident, because a unit test is
missing, write and commit the unit test, *then* make the incremental
change, make sure the unit tests pass, and then git push.

this is described on http://libre-soc.org/HDL_workflow

if you absolutely must make large changes, they can be done by writing the
leaf nodes of alternatives, then when it comes to changing the code that
uses the alternatives, writing classes with alternative implementations
that are *dynamically chosen* at runtime, through a config file and so on.

there's other techniques as well.

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] Needed Subset of POWER
From: Luke Kenneth Casson Leighton @ 2020-05-02 23:34 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <C838DC92-64B8-4FD3-A6FE-C45F4444761D@gatech.edu>

On Saturday, May 2, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:

> Hello all,
>         I’m reading through the Power ISA manual. What subset of POWER are
> we doing for the first single core revision?


not vector, that's for sure.  it's half the 1200 pages.  we do however need
to come up with an interoperability  solution for not having them.


>
> What is the minimal subset of POWER that we can get away with for an
> operational Linux kernel?


a GPIO subsystem, interrupts, MMU (RADIX), integer, branch, LD/ST,
hypervisor, SPRs, and a little bit more.

FP not needed.  see power-gem5 simulator branch.  am on phone. links in
bugzilla somewhere.  search "gem5".


> There are lots and lots of features such as:
>
> ```
> Decimal Floating-Point Support Operations: Add imme- diate forms of DFP
> Test Significance instructions.


not that.  not transactions, either


> ```
>
> Do we have to implement all these “icing” instructions eventually to be
> POWER certified?


i hear this is still being decided.

i do not speak for the Foundation, my understanding is, it will probably be
*guided* by what microwatt can reasonably implement.

asking IBM is unfortunately not quite... how can i put it.... because they
have incrementally got to such a staggering level of functionality over so
many years i'm not quite certain that they are truly aware how high the bar
has become.

microwatt and chiselwatt development will help them to appreciate that.

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] Documenting the SOC tree Repository
From: Yehowshua @ 2020-05-03  0:08 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyMasGzb-jqu1nhrsddW0D4DNsAD0v100s17OMJ8-BhTA@mail.gmail.com>



> On May 2, 2020, at 7:24 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> 
> i really do not like branches. 

OK no branches. I’d like to move the CSVs to the soc repo, and then do an iframe to the git tree raw to display in the wiki.

I can wrap it in a little js to get the browser to render the csv as a table.

It doesn’t make sense to submodule the entire wiki in the SOC repo just for some tables. That’s structurally wrong.

Moving the CSVs directly into the SOC repo is low priority for me now - but, I’m just putting it out there - its something that needs to be addressed sooner than later.

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

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