Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 72] verilog to nmigen converter (full or partial) needed
From: bugzilla-daemon @ 2020-03-24 14:24 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-72-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=72

--- Comment #22 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
another couple of pieces of code which need "parameterisation":
https://ascslab.org/research/briscv/index.html

L1cache.v and Lxcache.v - the cache-coherence protocol used there
looks particularly good, and it would be nice to be able to see
this code in 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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-03-24 14:22 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=216

--- Comment #16 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
http://sadve.cs.illinois.edu/Publications/isca00.pdf

this paper describes how to partition a cache so that media workloads
do not completely trash the L1 cache.  we will almost certainly need
to implement this because GPU workloads are READ-PROCESS-WRITE, and
even having the data in the L1 cache *at all* is completely pointless
as it's never going to be accessed more than once.

-- 
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] ieee.org
From: Luke Kenneth Casson Leighton @ 2020-03-24 14:06 UTC (permalink / raw)
  To: Libre-RISCV General Development

https://ieeexplore.ieee.org/document/4734919/figures#figures

does anyone have access to this paper?

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] Status on Our RISCV Implementation
From: Luke Kenneth Casson Leighton @ 2020-03-24 13:58 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CFEB7F13-0C2F-4299-A5DA-6BB3D00EA101@gatech.edu>

On Tue, Mar 24, 2020 at 1:11 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:

> > nope.  not for RISC-V.  userspace only.
>
> So I guess we’d have a POWER kernel…

correct.  and POWER TLBs and MMU.

> If a binary tries to call RISCV instructions to set supervisor mode register - how is that handled?

from userspace? fail... just like any other userspace RISC-V program
is not permitted to set a supervisor mode register on any standard
RISC-V system.

there will *be* no supervisor mode RISC-V... therefore implementation
of supervisor mode RISC-V registers is completely unnecessary.

userspace RISC-V is only permitted to set userspace RISC-V CSRs.

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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-03-24 13:55 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=216

--- Comment #15 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://ascslab.org/research/briscv/downloads.html

i wonder... i wonder if it would work if we had multiple L1 caches,
with an N-way crossbar on each (routing to be organised by binary
address bits [4:4+log2(N)-1]) then have a L2 cache underneath that?

or, just actually have multiple L1 caches with a coherent L2 cache
underneath?

-- 
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] Status on Our RISCV Implementation
From: Immanuel, Yehowshua U @ 2020-03-24 13:11 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxmXLMMZPLDpm5RUHM9Bn9Ur35++dmo8QNKzPpxNJ-KDw@mail.gmail.com>

> nope.  not for RISC-V.  userspace only.

So I guess we’d have a POWER kernel…
If a binary tries to call RISCV instructions to set supervisor mode register - how is that handled?

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] Advanced Topics on RISCV
From: Jean-Paul Chaput @ 2020-03-24 13:08 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <48389673-AD71-4168-8116-135C1D419634@gatech.edu>

[-- Attachment #1.1: Type: text/plain, Size: 991 bytes --]

On Tue, 2020-03-24 at 13:00 +0000, Immanuel, Yehowshua U wrote:
> > You can see details here:
> > https://www-soc.lip6.fr/trac/tsar
> 
> Thanks, I see that it scales up to 1024 - that's fantastic.

  Yes. Even above that. We did use free tools for the HDL,
  but unusual ones. So maybe you should concentrate on the
  theoretical mechanisms and avoid banging your head on the
  tools themselves. The prototype, If I remember correctly
  is made in 28nm with on MIPS32 processors.
    The chip was implemented with Cadence however. But the
  HDL models are free.
    We have run NetBSD and Linux on it.

-- 

      .-.     J e a n - P a u l   C h a p u t  /  Administrateur Systeme
      /v\     Jean-Paul.Chaput@lip6.fr
    /(___)\   work: (33) 01.44.27.53.99              
     ^^ ^^    cell:      06.66.25.35.55   home: 09.65.29.83.38

    U P M C   Universite Pierre & Marie Curie
    L I P 6   Laboratoire d'Informatique de Paris VI
    S o C     System On Chip

[-- Attachment #2: Type: text/plain, Size: 177 bytes --]

_______________________________________________
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] Advanced Topics on RISCV
From: Immanuel, Yehowshua U @ 2020-03-24 13:00 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <686f9b58ae6f6a3e11caff9714db66a0406e8b0b.camel@lip6.fr>

> You can see details here:
> https://www-soc.lip6.fr/trac/tsar

Thanks, I see that it scales up to 1024 - that's fantastic.
_______________________________________________
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] Advanced Topics on RISCV
From: Immanuel, Yehowshua U @ 2020-03-24 12:58 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzo=6eDRU8YhBf14JwqOn=S5vijy1+3w6T8wygXoxX2hQ@mail.gmail.com>

> given that AMOs are not very common, they basically get away with this
> approach.  however for massively-parallel SMP systems (64 cores or
> greater) this approach would begin to result in significant contention
> and slow-down of certain tasks.

So how would you get around this for >64 core RISCV CPU?

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] Advanced Topics on RISCV
From: Jean-Paul Chaput @ 2020-03-24 12:23 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <0F80A1BC-0241-49FE-B374-B4F1D8F3F5BD@gatech.edu>

[-- Attachment #1.1: Type: text/plain, Size: 2604 bytes --]



Hello Immanuel,

About manycores, we did a lot of work on that topic in our lab
(Sorbonne Université/LIP6). I send you a reference toward the
project we developed. This is a huge lot of work and may take
a lot of time to understand. But, we made a real chip with
16 cores to prove it works (and it do work). I cannot give you
more technical information as it not my field of expertise.

You must distinguish two case:

* Multi cores ( < 16) in that case, simpler solutions can be
  used.

* Many cores ( > 16) in this case, the TSAR project can be
  of interest.

TSAR (Tera-Scale ARchitecture).

You can see details here:
    https://www-soc.lip6.fr/trac/tsar

Best regards,


PS: Already signaled it to Luke.


On Tue, 2020-03-24 at 11:51 +0000, Immanuel, Yehowshua U wrote:
> I’ve read through the Spike page and a good portion of the simpleV page.
> 
> My two goals at the moment are:
> 1. Understand how RISCV handles multiple processes and does page walking
> 2. Understand how multicore ROSCV would work
> 
> I’m hoping to play with FreeRTOS soon so I can run through its codebase for setting up
> page tables.
> Also, do you know if spike tests the special instructions like exception instructions?
> Also, what RISCV instructions would a kernel use to set up the pagetables?
> 
> Lastly, do you know any good resources for intro to multicore systems? RISCV doesn’t
> seem to have any multicore specific instructions. My current questions would include
> things like:
> 
> 1. How can the kernel assign tasks to a certain core? If you have a process with
> multiple threads, it would make sense to spread out the threads among available
> processors instead of concentrating them on a single core. How might this work with
> respect to RISCV?
> 
> 2. Does the hardware ensure cache coherency - that is - externally - software sees one
> big cache all though I imagine each core would have a local cache that would have to
> communicate with other caches?
> 
> Yehowshua
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
-- 

      .-.     J e a n - P a u l   C h a p u t  /  Administrateur Systeme
      /v\     Jean-Paul.Chaput@lip6.fr
    /(___)\   work: (33) 01.44.27.53.99              
     ^^ ^^    cell:      06.66.25.35.55   home: 09.65.29.83.38

    U P M C   Universite Pierre & Marie Curie
    L I P 6   Laboratoire d'Informatique de Paris VI
    S o C     System On Chip

[-- Attachment #2: Type: text/plain, Size: 177 bytes --]

_______________________________________________
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] Status on Our RISCV Implementation
From: Luke Kenneth Casson Leighton @ 2020-03-24 12:07 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <A6C778B3-04E3-47D4-A28A-B6AC55D4A604@gatech.edu>

On Tue, Mar 24, 2020 at 11:39 AM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> I’m curious, what is the status of our RISCV implementation.
>
> Do we have:
> 1. A decoder - I’m pretty sure we do

using minerva: it will need updating to RV64GC

> 2. A page table walker

nope.  not for RISC-V.

> 3. FPU support

yes.

> 4. Supervisor/Hypervisor mode support?

nope.  not for RISC-V.  userspace only.

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] Advanced Topics on RISCV
From: Luke Kenneth Casson Leighton @ 2020-03-24 12:06 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <0F80A1BC-0241-49FE-B374-B4F1D8F3F5BD@gatech.edu>

On Tue, Mar 24, 2020 at 11:52 AM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:

> I’ve read through the Spike page and a good portion of the simpleV page.

it's ultimately quite simple in concept: the details are where it gets hairy

> My two goals at the moment are:
> 1. Understand how RISCV handles multiple processes and does page walking

ok so SV will not help you there: it doesn't have anything to do with PTW (etc.)

multiple processes are handled by context-swapping.  register and CSR
state are "saved", the new process selected, and its state "swapped
in" to registers and CSRs.  the last thing that's swapped over is: the
Program Counter.

PTW - you'll need to do quite a bit of research into virtual memory,
TLBs, etc. first.

> 2. Understand how multicore RISCV would work

you'll need to look up "Weak Memory Model" (as opposed to "Total Store
Order").  then look up AMO (atomic memory operations).

> I’m hoping to play with FreeRTOS soon so I can run through its codebase for setting up page tables.

that's a good idea.

> Also, do you know if spike tests the special instructions like exception instructions? Also, what RISCV instructions would a kernel use to set up the pagetables?
>
> Lastly, do you know any good resources for intro to multicore systems? RISCV doesn’t seem to have any multicore specific instructions.

correct.  it has LR/SC semantics on atomic operations, and it is
entirely up to the *operating system* - the kernel - to use these in
an effective way in order to guarantee that memory corruption between
processes does not occur.

*that is all there is to it*.

> My current questions would include things like:
>
> 1. How can the kernel assign tasks to a certain core? If you have a process with multiple threads, it would make sense to spread out the threads among available processors instead of concentrating them on a single core. How might this work with respect to RISCV?

just like it would on any multi-core operating system which was
running on an SMP-capable hardware.  there's absolutely no difference
here.


> 2. Does the hardware ensure cache coherency -

nnnope.  that's what a "Weak Memory Model" is.

> that is - externally - software sees one big cache all though I imagine each core would have a local cache that would have to communicate with other caches?

nnope.

that's why LR/SC atomic semantics exist.  look up AMO.  these are then
used to do kernel-level spin-locks, mutexes etc. all of which are a
hard requirement for sorting out memory clashes.

from my (brief) look at several RISC-V SMP implementations, the
takeaway that i got was: most implementations actually put the AMO ALU
*actually in the L2 cache* (!) - one *single* AMO ALU - accessible
*ONLY* over an exclusive bus such that ONLY one core may use it at any
given time.

thus, atomicity of the Atomic Memory Operations - crucial to - are
done by way of resource contention / starvation, rather than "actual
atomic but parallel memory operation detection and clash avoidance".

given that AMOs are not very common, they basically get away with this
approach.  however for massively-parallel SMP systems (64 cores or
greater) this approach would begin to result in significant contention
and slow-down of certain tasks.

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 257] Implement demo Load/Store queueing algorithm
From: bugzilla-daemon @ 2020-03-24 11:54 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-257-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=257

--- Comment #16 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://groups.google.com/forum/#!topic/comp.arch/cbGAlcCjiZE

started a discussion here, see what happens.

-- 
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] Advanced Topics on RISCV
From: Immanuel, Yehowshua U @ 2020-03-24 11:51 UTC (permalink / raw)
  To: Libre-RISCV General Development

I’ve read through the Spike page and a good portion of the simpleV page.

My two goals at the moment are:
1. Understand how RISCV handles multiple processes and does page walking
2. Understand how multicore ROSCV would work

I’m hoping to play with FreeRTOS soon so I can run through its codebase for setting up page tables.
Also, do you know if spike tests the special instructions like exception instructions? Also, what RISCV instructions would a kernel use to set up the pagetables?

Lastly, do you know any good resources for intro to multicore systems? RISCV doesn’t seem to have any multicore specific instructions. My current questions would include things like:

1. How can the kernel assign tasks to a certain core? If you have a process with multiple threads, it would make sense to spread out the threads among available processors instead of concentrating them on a single core. How might this work with respect to RISCV?

2. Does the hardware ensure cache coherency - that is - externally - software sees one big cache all though I imagine each core would have a local cache that would have to communicate with other caches?

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] Status on Our RISCV Implementation
From: Immanuel, Yehowshua U @ 2020-03-24 11:39 UTC (permalink / raw)
  To: Libre-RISCV General Development

I’m curious, what is the status of our RISCV implementation.

Do we have:
1. A decoder - I’m pretty sure we do
2. A page table walker
3. FPU support
4. Supervisor/Hypervisor mode support?

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 257] Implement demo Load/Store queueing algorithm
From: bugzilla-daemon @ 2020-03-24 11:16 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-257-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=257

--- Comment #15 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
*facepalm*... i managed to get all the way to a successful unit test
before noticing that i'd set up the code to LD/ST *bits*... not bytes :)

am currently adding ST splitting: drawing this diagram helped:

https://libre-riscv.org/3d_gpu/ld_st_splitter.png

-- 
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 72] verilog to nmigen converter (full or partial) needed
From: bugzilla-daemon @ 2020-03-24 10:50 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-72-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=72

--- Comment #21 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
actually the top priority is mulRecFN, however it needs some of the other
macros / functions to work.

see mulRecFN.v - at the link in comment #20, no there is no online git repo,
there is only a .zip file.

-- 
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] Next tasks for the Libre-SOC
From: Luke Kenneth Casson Leighton @ 2020-03-24 10:48 UTC (permalink / raw)
  To: Libre-RISCV General Development, Tobias Platen
In-Reply-To: <20200324102318.16d66fda34ecc32c96fd57df@platen-software.de>

On Tue, Mar 24, 2020 at 10:37 AM Tobias Platen
<hacks2019@platen-software.de> wrote:
>
> I've now worked on the NLNet 2019 Coriolis2 Layout proposal [1] and now I'm looking for new tasks that I'll do next.

always see "bugs assigned to me".  in this case, because i'm not
"you", i did a search for bugs assigned to
hacks2019@platen-software.de:
http://bugs.libre-riscv.org/buglist.cgi?email1=hacks2019%40platen-software.de&emailassigned_to1=1&emailtype1=substring&list_id=557&query_format=advanced&resolution=---

i am also half-way through *manual* conversion of mulRecFN.v and woo,
the completely-uncommented logic, there, is ridiculously obtuse and
impossible to actually understand what the hell is going on.

we need that logic because it forms the basis of the FMAC rules.  and
we need a FP MAC.

if you can get mulRecFN *and all dependent macros/functions* working
that would be extremely helpful.

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] Next tasks for the Libre-SOC
From: Tobias Platen @ 2020-03-24  9:23 UTC (permalink / raw)
  To: libre-riscv-dev

I've now worked on the NLNet 2019 Coriolis2 Layout proposal [1] and now I'm looking for new tasks that I'll do next. 

Tobias Platen

[1] http://bugs.libre-riscv.org/show_bug.cgi?id=178

_______________________________________________
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-03-24  8:50 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #101 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #100)
> one issue with qemu is that it doesn't properly implement everything -- for
> example, it doesn't appear to implement the FPSCR.FR bit

yuck

> (I've been reading
> its source as an additional reference for simple-soft-float).

ok so when it comes to FP we can't expect that to work.  by then we should be a
long way forward at least with running something.

-- 
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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-24  6:14 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #100 from Jacob Lifshay <programmerjake@gmail.com> ---
one issue with qemu is that it doesn't properly implement everything -- for
example, it doesn't appear to implement the FPSCR.FR bit (I've been reading its
source as an additional reference for simple-soft-float).

-- 
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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-24  1:49 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #99 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/virtualization_administration_guide/sect-vish-dump

crashdump --memory only would get a .elf file with memory and registers.

executing a bare metal .bin file under qemu with a small memory would give
something not too massive to parse

https://github.com/eliben/pyelftools/blob/master/examples/dwarf_decode_address.py

hmm it seems there are at least 2 different python elf parsers.

the only thing we have to watch, these are big dependencies we're pulling in
(i'm on a mobile 4G connection). luckily i have qemu already installed

-- 
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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-24  1:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #98 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/simulator/test_sim.py;hb=HEAD

y'know... the comment "checked this against qemu" got me thinking. this looks
like it could be used to actually run any of:

* qemu
* the simulator
* the score6600 engine
* pearpc
* gem5

i know qemu can be run in bare metal mode, console only, for example.  it would
not be cycle accurate however would give us a jumpstart on running really basic
programs.

-- 
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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-23 21:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #97 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #96)
> (In reply to Luke Kenneth Casson Leighton from comment #95)
> 
> > yes.  however adding a power frontend on it as we found ain't so bad.  can
> > use the same code.
> > 
> > if you look here you can see how basic the test simulator is
> > https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/experiment/score6600.
> > py;h=babce2439233f84c262c08795b873a6167197ec9;hb=HEAD#l859
> > 
> > adjusting that so it uses InternalOp is... er... not hard? :)
> 
> Luke, looks like you and I are doing different things...? It looks to me
> like score6600 is actual hardware, not a simulator.

i'd literally just moved RegSim and MemorySim into their own folder, you put
internalop_sim.py in the same location.

they should be pretty much identical in function.


> I have basic simulator
> I'm working on here
> https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/simulator/
> internalop_sim.py;h=813dd19c40e21283d000fd597074a2cb38595a8a;
> hb=e95b4372c5163bb6f753c92d8445d4af7f117457 - I took some of the elements
> from score6600 (like the register and memory file) and modified them to get
> a basic simulator, which I'm testing along side a real power machine. Were
> you going for something different...?

take a look at sim.py it is near identical to what you did :)

although you have, i think, also added a decoder on it?  so what you wrote can
take actual power instructions, is that right?

sim.py "tracks" what the real hardware does.  so the idea is that after running
the exact same instructions through each, and waiting for the instruction queue
to indicate "no longer busy processing", we can do a memory-memory compare and
a regfile-regfile compare and they should be *exactly* the same.

i wrote a function which does exactly that, one for mem and one for regfile.

unfortunately because this is a multiissue  OoO design we cannot take a
snapshot at a given time and say "yeah this will be exactly the same", you have
to pause, wait for outstanding ops, *then* snapshot.

that "pause" means unfortunately that it affects internal state, because FUs
are emptying rather than being filled with new operations.

but, it is the best we can do.

oh btw, one really important thing to remember: at sone point the sim will do
dynamic SIMD just like in the PartitionedSignal.  code to reuse in
InternalOpSim has already been written... in the PartitionedSignal unit tests!

and, actually, hm, we could probably just lift that code wholesale into a class
then rework the psig unit test to use it, *and* use that same code here.

-- 
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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-23 20:12 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #96 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #95)

> yes.  however adding a power frontend on it as we found ain't so bad.  can
> use the same code.
> 
> if you look here you can see how basic the test simulator is
> https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/experiment/score6600.
> py;h=babce2439233f84c262c08795b873a6167197ec9;hb=HEAD#l859
> 
> adjusting that so it uses InternalOp is... er... not hard? :)

Luke, looks like you and I are doing different things...? It looks to me like
score6600 is actual hardware, not a simulator. I have basic simulator I'm
working on here
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/simulator/internalop_sim.py;h=813dd19c40e21283d000fd597074a2cb38595a8a;hb=e95b4372c5163bb6f753c92d8445d4af7f117457
- I took some of the elements from score6600 (like the register and memory
file) and modified them to get a basic simulator, which I'm testing along side
a real power machine. Were you going for something different...?

-- 
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