Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 306] Formal Correctness Proof for ALU pipeline
From: bugzilla-daemon @ 2020-05-20 15:20 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-306-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=331

-- 
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 331] Formal Correctness Proof for LOGICAL pipeline
From: bugzilla-daemon @ 2020-05-20 15:20 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-331-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=306

-- 
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 331] New: Formal Correctness Proof for LOGICAL pipeline
From: bugzilla-daemon @ 2020-05-20 15:20 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 331
           Summary: Formal Correctness Proof for LOGICAL pipeline
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Mac OS
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Formal Verification
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

a formal correctness proof is needed for the POWER9 Logical pipeline

-- 
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 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-20 15:19 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=330

-- 
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 330] create POWER9 Logic Pipeline
From: bugzilla-daemon @ 2020-05-20 15:19 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-330-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=305

-- 
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 330] New: create POWER9 Logic Pipeline
From: bugzilla-daemon @ 2020-05-20 15:19 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 330
           Summary: create POWER9 Logic Pipeline
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Mac OS
            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 pipeline is needed implementing
https://libre-soc.org/openpower/isa/fixedlogical/

-- 
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] daily kan-ban update 20may2020
From: Luke Kenneth Casson Leighton @ 2020-05-20 15:14 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <0777688C-B036-4939-8F33-338E05D1B6EC@getmailspring.com>

On Wed, May 20, 2020 at 3:51 PM Cole Poirier <colepoirier@gmail.com> wrote:

> Yesterday I learned another valuable lesson on the merits of the KISS
> philosophy.

funny man :)

> Today I plan on integrating the Bpermd module into the
> logical pipeline, with tests.

fooocuuuus :)  adding the module to Logical main_stage.py should be
around... maximum 10 lines of code.  really.  not.  difficult.  link
the inputs.  link the outputs.  err... that's it.

btw as a third (incremental) step, after integrating it and putting in
the unit test into soc.fu.logical.test/test_pipe_caller.py, you should
actually be able to integrate the formal proof into the Logical
pipeline as well.

> > * talked with Marketnext about the resource requirements for the May
> > 30 Hackathon.
>
> Is there a document about this on the wiki?

there isn't.  there should be.  however it is up to Marketnext.  the
issue is that i am not sure if they understand quite how high the
resource requirements are, and consequently how long it will take
people in India (and other places across the world) to install the
development environment.

> If not would you mind
> briefly explaining what the parameters and the objectives of the
> hackathon are?

to introduce over 15 different groups / teams / individuals to
Libre-SOC development.

> > * received a message from these guys, they would like to do a review
> > https://radicallyopensecurity.com/
>
> Just took a quick perusal of their website, they look like they share
> our philosophy about digital rights, as well as having a
> 'social-benefit-esque' organizational model. I think their doing a
> review of our processor's security would be welcome help. Your thoughts?

their review is a mandatory requirement as part of the NLNet funding.
i did point out to them that asking to have a private conversation
about their role is not exactly very transparent :)

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] daily kan-ban update 20may2020
From: Cole Poirier @ 2020-05-20 14:50 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDxxHh-1kjXtP-ZB-u5AoGE8b1+zt6XmqVVe1fHTtw5bEA@mail.gmail.com>

On May 20 2020, at 7:14 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> yesterday:
> * more pipeline stuff with michael and cole and jacob.  researched
> TRAP ops in particular

Yesterday I learned another valuable lesson on the merits of the KISS
philosophy. Today I plan on integrating the Bpermd module into the
logical pipeline, with tests.

> * talked with Marketnext about the resource requirements for the May
> 30 Hackathon.

Is there a document about this on the wiki? If not would you mind
briefly explaining what the parameters and the objectives of the
hackathon are?

> * received a message from these guys, they would like to do a review
> https://radicallyopensecurity.com/

Just took a quick perusal of their website, they look like they share
our philosophy about digital rights, as well as having a
'social-benefit-esque' organizational model. I think their doing a
review of our processor's security would be welcome help. Your thoughts?

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

* [libre-riscv-dev] [Bug 318] fix LDSTCompUnit
From: bugzilla-daemon @ 2020-05-20 14:40 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-318-13@https.bugs.libre-soc.org/>

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

--- Comment #18 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
Cesar, fyi:

https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=c501606b20c74050fb0d422ff886a7d9fb2a6a96

very straightforward, no disruption at all, due to a hack
of making MultiCompUnit look exactly like it was.

-- 
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 306] Formal Correctness Proof for ALU pipeline
From: bugzilla-daemon @ 2020-05-20 14:16 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-306-13@https.bugs.libre-soc.org/>

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

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
* OP_EXTS proof
https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=32d9da2bd849d3ae9b59bdec7a4add0c35908922

* OP_CMP and OP_CMPEQB proof
https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=ca79ab18a7fa9bdabeca860448d79b5d11dc222f

-- 
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] daily kan-ban update 20may2020
From: Luke Kenneth Casson Leighton @ 2020-05-20 14:14 UTC (permalink / raw)
  To: Libre-RISCV General Development

yesterday:
* more pipeline stuff with michael and cole and jacob.  researched
TRAP ops in particular
* identified that MUL and DIV have similar register allocation to
SHIFT and LOGICAL
* moved MUL and DIV ops to their own respective Function Unit
(power_enums.py, csv files)
* talked with Marketnext about the resource requirements for the May
30 Hackathon.
* worked out from this image that we need to do pretty much the same thing: give
  each FunctionUnit a "consistent uniform interface" of its register
port allocation.
  https://libre-soc.org/3d_gpu/6600_scoreboard_fu_regs.png

this morning:
* created nmutil exts helper function and used it everywhere (OP_EXTS
and other places)
* helped Jean-Paul to understand the requirements for regular
coriolis2 layout of the Dep Matrices

today:

* send an agenda to Hugh, Tim, Yehowshua for the bi-weekly OpenPOWER conf call
* received a message from these guys, they would like to do a review
https://radicallyopensecurity.com/
* start putting an "API / Spec" system together for Function Units, to
be able to connect Regfiles to ports.
* do the "Record" conversion of CompALU (part of the API/Spec for FUs)

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

* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-20 14:01 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>

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

--- Comment #81 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
Created attachment 61
  --> https://bugs.libre-soc.org/attachment.cgi?id=61&action=edit
ALU main stage

hilarious.  the actual OP_ADD, OP_CMPEQB, OP_CMP and OP_EXTS operations
are ridiculously small compared to the support infrastructure: regfile,
DMs, everything basically.

i'd heard that routing of data is by far and above the majority of
a CPU: it's kind-of illuminating to actually see how small an ALU
can be.

-- 
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 329] coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-05-20 12:41 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>

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

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
i just also added a second one to experiment8 as an illustration, it is an
FU-Regs Matrix with the following parameters:

* Number of Regs:                          4 (to keep it small as a demo)
* Number of Function Units:                3 (likewise)
* Number of Regfile Read ports protected:  2
* Number of Regfile Write ports protected: 2

these numbers can and will vary.  we have *four* Register Files to
protect with these Matrices.  five when we have FP support.

-- 
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 329] coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-05-20 12:34 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>

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

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
Created attachment 60
  --> https://bugs.libre-soc.org/attachment.cgi?id=60&action=edit
combination of two matrices showing how they are used

-- 
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 329] coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-05-20 12:33 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>

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

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
Created attachment 59
  --> https://bugs.libre-soc.org/attachment.cgi?id=59&action=edit
fu-regs matrix screenshot

-- 
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 329] coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-05-20 12:33 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>

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

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
Created attachment 58
  --> https://bugs.libre-soc.org/attachment.cgi?id=58&action=edit
fu-fu matrix screenshot

-- 
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 329] coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-05-20 12:30 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>

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

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
jean-paul i have added this example to soclayout as experiment8

https://git.libre-soc.org/?p=soclayout.git;a=commitdiff;h=1866a4346044f65a23a0905d8e6ec9883a5f8070

this is a typical basic example: 

there are going to be approximately... 6 "pairs" of these matrices.
they are "pairs" because there are two types:

* FU-Regs - stands for Function Unit to Registers Matrix
* FU-FU   - stands for ... well the obvious

variants include:

* Shadow Matrix
* Memory-Address-Conflict Matrix
* augmentation on the Registers to set multiple entries simultaneously

the last thing we need is to go full manual layout on these, with so
many variants.

-- 
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 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-05-20 12:20 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=329

-- 
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 329] coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-05-20 12:20 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=217

-- 
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 329] coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-05-20 12:20 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
    parent task for|                            |203
  budget allocation|                            |
    NLnet milestone|---                         |NLNet.2019.Coriolis2

-- 
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 329] New: coriolis2 experiment layout for Dependency Matrices
From: bugzilla-daemon @ 2020-05-20 12:18 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 329
           Summary: coriolis2 experiment layout for Dependency Matrices
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Hardware Layout
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

Created attachment 57
  --> https://bugs.libre-soc.org/attachment.cgi?id=57&action=edit
quick preliminary test ilang from soc/scoreboard/test_mem_fu_matrix.py

we need a quick example to demonstrate how the Dependency Matrices would
look so that coriolis2 can do the layout in a regular fashion.  this
even though they may convert from DFF to SRNAND, so the layout needs to
be dynamic, rather than explicit naming of cells.

also, some of the cells may be augmented by additional "setting" logic
that needs to go into every row (not yet written), so any explicit
manually-created layout that hunts for explicit cell names is going to
have to be redone, and not only redone, duplicated manual work several
times.

this is why the idea exists to identify sub-groups of cells by way of
netlist path analysis, and have them placed by Etesian in regular grid
fashion.

-- 
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 70] evaluate Bus Architectures
From: bugzilla-daemon @ 2020-05-20 11:35 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-70-13@https.bugs.libre-soc.org/>

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

--- Comment #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #11)
> discovered that there are already quite a few protocols that are much more
> widely used than omnixtend that support cache coherent memory access over a
> network: google "rdma cache coherent"

adding "wishbone" to that and opensparc T1 comes up
https://www.oracle.com/technetwork/systems/opensparc/opensparc-internals-book-1500271.pdf

-- 
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] daily kan-ban update 19may2020
From: Luke Kenneth Casson Leighton @ 2020-05-20 11:28 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <20200520083952.d529549c1c76f458e7cc3258@platen-software.de>

On Wed, May 20, 2020 at 7:39 AM Tobias Platen
<libre-soc@platen-software.de> wrote:

> On Tue, 19 May 2020 I was re-reading 'ScoreBoard Mechanics1.pdf' and 'ScoreBoard Mechanics2.pdf'.

they're kinda fascinating, aren't they?

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

* [libre-riscv-dev] [Bug 70] evaluate Bus Architectures
From: bugzilla-daemon @ 2020-05-20  6:47 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-70-13@https.bugs.libre-soc.org/>

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

--- Comment #11 from Jacob Lifshay <programmerjake@gmail.com> ---
discovered that there are already quite a few protocols that are much more
widely used than omnixtend that support cache coherent memory access over a
network: google "rdma cache coherent"

-- 
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] daily kan-ban update 19may2020
From: Tobias Platen @ 2020-05-20  6:39 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDwRS5yHWa=qnyZhCe5tux6Q=9KiXvxg5M_x21=GZ5tnaw@mail.gmail.com>

On Tue, 19 May 2020 I was re-reading 'ScoreBoard Mechanics1.pdf' and 'ScoreBoard Mechanics2.pdf'.

_______________________________________________
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