* Re: [libre-riscv-dev] Request for input and technical expertise for Systèmes Libres Amazon Alexa IOT Pitch 10-JUN-2020
From: Jacob Lifshay @ 2020-06-08 0:29 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwDMFuONT=LtAkE7cJx-=ZPkmKAhb-7fYOr+LoQDDkGkQ@mail.gmail.com>
On Sun, Jun 7, 2020, 16:56 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Mon, Jun 8, 2020 at 12:42 AM Cole Poirier <colepoirier@gmail.com>
> wrote:
> >
> > Hi Libre-SOC Developers,
> >
> > I have been working on a first draft of the script/contents of a
> > presentation pitching Libre-SOC to Amazon Alexa's IOT division. I have
> > put what I've been able to come up with on my own on a wiki page here:
> https://libre-soc.org/Systemes_Libres_Amazon_Alexa_IOT_Pitch_10-JUN-2020/.
>
> (i moved it to here, sorry!
>
> https://libre-soc.org/systemes_libre/Systemes_Libres_Amazon_Alexa_IOT_Pitch_10-JUN-2020/
> )
>
> > If you can, please review what I have written and edit, rearrange, and
> > add relevant points as you see fit. I would appriciate help specifically
> > in filling in or correcting technical details or false claims that I
> > have made.
>
I added some notes.
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
* Re: [libre-riscv-dev] "simple" core
From: Yehowshua @ 2020-06-08 0:27 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyVvef2FTsT6H-JU_6OoWd2UHDgLWJ9nLbPxqLEZ7d3Rg@mail.gmail.com>
> core.py really is *very* simple. its execution model is as follows:
>
> * receive instruction
> * decode instruction
> * identify through bitmasking which pipeline can handle it
> * enable *only* the MultiCompUnit managing that pipeline
> * wait for it to indicate that it is not busy (this includes regfile writing)
> * move on to the next instruction.
This is great to hear.
Keep up the great work.
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] "simple" core
From: Cole Poirier @ 2020-06-08 0:10 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDxf0VqGugNp_OAhNhWOs51ENHKanb_shhUfFw=MLxEEdg@mail.gmail.com>
On Jun 7 2020, at 5:06 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Mon, Jun 8, 2020 at 1:01 AM Cole Poirier <colepoirier@gmail.com> wrote:
>
>> Thanks! Although I haven't done that yet acutally, I'm trying to get to
>> it this evening but the Systemes Libres pitch has taken up most of my
>> afternoon. Will send you and Yehowshua an email about this shortly.
>
> 1am here. consider me "asleep". l.
Hehe you're doing better than last night. Rest up :)
_______________________________________________
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] "simple" core
From: Luke Kenneth Casson Leighton @ 2020-06-08 0:06 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <B6551DE7-16FD-4ED1-B4AC-B759AE78EDDD@getmailspring.com>
On Mon, Jun 8, 2020 at 1:01 AM Cole Poirier <colepoirier@gmail.com> wrote:
> Thanks! Although I haven't done that yet acutally, I'm trying to get to
> it this evening but the Systemes Libres pitch has taken up most of my
> afternoon. Will send you and Yehowshua an email about this shortly.
1am here. consider me "asleep". 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] "simple" core
From: Cole Poirier @ 2020-06-08 0:01 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDy2WS=_-7dbu3LGHBZxP7UgjDSthZBveahPHuSByyLE9g@mail.gmail.com>
On Jun 7 2020, at 4:58 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Mon, Jun 8, 2020 at 12:54 AM Cole Poirier <colepoirier@gmail.com> wrote:
>
>> > python3 soc/simple/test/test_core.py
>>
>> Just ran it. SO COOL!!
>
> :)
>
> i have to get LDSTCompUnit operational (the L0CacheBuffer memory
> alignment), then i'm happier adding it in. right now it hangs if you
> send it two instructions, for example - we can't have that as it would
> stop core.py from working, as well.
>
>> Looking forward to seeing this all come together as the rest has so far.
>> And hopefully contributing a little :)
>
> you already are! when you've added one instruction into the unit tests
> for TRAP, that's basically (even with one instruction) when it can go
> straight in. other tests can be added later.
>
> l.
Thanks! Although I haven't done that yet acutally, I'm trying to get to
it this evening but the Systemes Libres pitch has taken up most of my
afternoon. Will send you and Yehowshua an email about this shortly.
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] "simple" core
From: Luke Kenneth Casson Leighton @ 2020-06-07 23:58 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <C4C83C38-D2A7-4531-9B36-CAEAED9181DF@getmailspring.com>
On Mon, Jun 8, 2020 at 12:54 AM Cole Poirier <colepoirier@gmail.com> wrote:
> > python3 soc/simple/test/test_core.py
>
> Just ran it. SO COOL!!
:)
i have to get LDSTCompUnit operational (the L0CacheBuffer memory
alignment), then i'm happier adding it in. right now it hangs if you
send it two instructions, for example - we can't have that as it would
stop core.py from working, as well.
> Looking forward to seeing this all come together as the rest has so far.
> And hopefully contributing a little :)
you already are! when you've added one instruction into the unit tests
for TRAP, that's basically (even with one instruction) when it can go
straight in. other tests can be added later.
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] Request for input and technical expertise for Systèmes Libres Amazon Alexa IOT Pitch 10-JUN-2020
From: Luke Kenneth Casson Leighton @ 2020-06-07 23:55 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <A6C1638B-AEE9-4046-A57C-99631DF873A9@getmailspring.com>
On Mon, Jun 8, 2020 at 12:42 AM Cole Poirier <colepoirier@gmail.com> wrote:
>
> Hi Libre-SOC Developers,
>
> I have been working on a first draft of the script/contents of a
> presentation pitching Libre-SOC to Amazon Alexa's IOT division. I have
> put what I've been able to come up with on my own on a wiki page here: https://libre-soc.org/Systemes_Libres_Amazon_Alexa_IOT_Pitch_10-JUN-2020/.
(i moved it to here, sorry!
https://libre-soc.org/systemes_libre/Systemes_Libres_Amazon_Alexa_IOT_Pitch_10-JUN-2020/
)
> If you can, please review what I have written and edit, rearrange, and
> add relevant points as you see fit. I would appriciate help specifically
> in filling in or correcting technical details or false claims that I
> have made.
"GPU is in ADDITION to CPU (2 processors, 2 ISAs, 2 compilers)"
the idea being, it's 3 things, where as the presentation is made,
voice goes down, down, down. punch, punch, punch.
i've done a little bit more, do take a look.
l.
> Thank you, your help will be essential in putting together an impressive
> and polished presentation for our potential customers at Amazon Alexa's
> IOT division.
>
> Cole
>
> _______________________________________________
> 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
* Re: [libre-riscv-dev] "simple" core
From: Cole Poirier @ 2020-06-07 23:54 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDyVvef2FTsT6H-JU_6OoWd2UHDgLWJ9nLbPxqLEZ7d3Rg@mail.gmail.com>
On Jun 7 2020, at 4:31 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> the simple core is taking shape as a combination of all the pipelines,
> connected to the (5) types of register files. all unit tests that
> have been developed to test *individual* pipelines have been borrowed
> through inheritance, to run against the register files, this time.
> you can try it out as:
>
> python3 soc/simple/test/test_core.py
Just ran it. SO COOL!!
> the next phases will involve:
>
> * adding in LDSTCompUnit
> * adding in minerva wishbone L1 I-Cache code (including bypass mode)
> * including the pre-written scoreboard "Instruction Queue" code
> * linking up NIA to the IQ, to fetch instructions and pass them to the decoder.
>
> at that point we will have an actual core that is capable of executing
> instructions on its own. after that, we have a basis for carrying out
> further code-morphs, to add the precise-capable augmented scoreboard
> and so on.
>
> l.
Looking forward to seeing this all come together as the rest has so far.
And hopefully contributing a little :)
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-06-07 23:42 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-216-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=216
--- Comment #58 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
worked out that this:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/minerva/wishbone.py;hb=HEAD
is exactly what we need to do the arbitration of odd/even dual ports.
actually there could be four 64-bit wishbone buses, each seeking
arbitration onto the one 64-bit memory bus:
* LSB 64-bit half of the 128-bit ODD L0CacheBuffer Port interface
* MSB 64-bit half of the 128-bit ODD L0CacheBuffer Port interface
* LSB 64-bit half of the 128-bit EVEN L0CacheBuffer Port interface
* MSB 64-bit half of the 128-bit EVEN L0CacheBuffer Port interface
the detection as to whether any given one of these should be enabled
is simply done by ORing the relevent sections of the 16-bit byte-enable
column line (wen / ren). this comes directly from the "en" lines
from DataMerger.
* half (8) of the Datamerger byte-enable lines will go to enabling
one of the 64-bit Wishbone interfaces
* the other half (8) will go to the other one.
--
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] Request for input and technical expertise for Systèmes Libres Amazon Alexa IOT Pitch 10-JUN-2020
From: Cole Poirier @ 2020-06-07 23:42 UTC (permalink / raw)
To: Libre-RISCV General Development
Hi Libre-SOC Developers,
I have been working on a first draft of the script/contents of a
presentation pitching Libre-SOC to Amazon Alexa's IOT division. I have
put what I've been able to come up with on my own on a wiki page here: https://libre-soc.org/Systemes_Libres_Amazon_Alexa_IOT_Pitch_10-JUN-2020/.
If you can, please review what I have written and edit, rearrange, and
add relevant points as you see fit. I would appriciate help specifically
in filling in or correcting technical details or false claims that I
have made.
Thank you, your help will be essential in putting together an impressive
and polished presentation for our potential customers at Amazon Alexa's
IOT division.
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] "simple" core
From: Luke Kenneth Casson Leighton @ 2020-06-07 23:31 UTC (permalink / raw)
To: Libre-RISCV General Development
the simple core is taking shape as a combination of all the pipelines,
connected to the (5) types of register files. all unit tests that
have been developed to test *individual* pipelines have been borrowed
through inheritance, to run against the register files, this time.
you can try it out as:
python3 soc/simple/test/test_core.py
core.py really is *very* simple. its execution model is as follows:
* receive instruction
* decode instruction
* identify through bitmasking which pipeline can handle it
* enable *only* the MultiCompUnit managing that pipeline
* wait for it to indicate that it is not busy (this includes regfile writing)
* move on to the next instruction.
each MultiCompUnit, of which there are currently five connected up
(ALU, Logical, ShiftRot, CR, Branch), has a number of "operand in" and
"result out" ports. the register files have been *deliberately*
spec'd to match one-for-one the maximum number of ports of each
regfile type needed.
therefore, for example: whilst no other MCU needs INT 2W (2 write
ports), LDSTCompUnit *does* need 2 write ports and consequently the
INT regfile has been allocated 2W. another example: CR requires
*three* read ports *and* the "full" (32-bit) CR, and consequently the
CR regfile is 4R (1 full, 3 4-bit).
this dramatically simplifies the code needed to connect up the MCUs to
the Regfiles, because the port allocations (resource contention aside)
is one-to-one.
the majority of the code in core.py (at present) involves reorganising
"regspecs" into a dictionary-of-dictionaries-of-lists. the structure
is:
* first dictionary key is the register file TYPE (INT, CR, SPRs)
* second dictionary key is the register port NAME (cr0, ra, rb, XER_so)
* list contains the *Function Unit* and operand/result read/write port
that list (on a per-file, per-regname basis) therefore contains *all*
Function Units that wish to contend for that register file port, and,
consequently, it is a simple matter of:
* A. creating a PriorityPicker to select one and *ONLY* one Function
Unit that is permitted to access that port at any one time
* B. creating a Broadcast Bus (fan-in in the case of write, fan-out in
the case of read) connecting regfile port to Function Unit port.
the next phases will involve:
* adding in LDSTCompUnit
* adding in minerva wishbone L1 I-Cache code (including bypass mode)
* including the pre-written scoreboard "Instruction Queue" code
* linking up NIA to the IQ, to fetch instructions and pass them to the decoder.
at that point we will have an actual core that is capable of executing
instructions on its own. after that, we have a basis for carrying out
further code-morphs, to add the precise-capable augmented scoreboard
and so on.
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 368] Need one example unit test of how to run some assembly code "qemu vs simulator" rather than "qemu vs hardware"
From: bugzilla-daemon @ 2020-06-07 23:02 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-368-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=368
--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #4)
> Oh, since the actual debug interface uses gdb and has nothing to do with
> qemu, it might be possible to run the generated programs under gdb on power
> hardware.
oh of course. and... hmmm... here's an idea.
if an option can be added which allows that to be done through ssh,
we'd be able to work locally and not have to
have a full dev environment on talos1.libre-soc.org (each).
one utterly cool way of doing remote python execution:
https://github.com/tomerfiliba/rpyc
he invented a packet format and a protocol that contains commands
like "dir()" so you get back the list of objects, and so on. even
exceptions are properly transferred.
once "on" that remote system, the only library that would need to
be installed on the *remote* system: pygdbmi.
--
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-07 22:55 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 #54 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cesar Strauss from comment #53)
> commit 71a791cf5f05bd5858fdc60f4ccdca936edc1d75
> Author: Cesar Strauss <cestrauss@gmail.com>
> Date: Sun Jun 7 16:32:11 2020 -0300
>
> Make the test ALU conform to the valid/ready protocol
>
> Adjust the test case accordingly.
>
> It was definitively not a one-line change. But it was fun.
oh good! :)
> Select any other operation than MUL, ADD, or SHR, and it will do a
> combinatorial subtraction, with zero-delay and no registering.
>
> The interesting thing about zero-delay is that, due to the absence of an
> internal register, it will not release the input data until the result is
> transferred out.
oh wait... that's a *combinatorial* ALU? iinteresting. i wonder
what that could be used for.
hmmm i tried putting OP_NOP in there, and both compunit1 and parallel
locked up. this tends to indicate a combinatorial loop. any clues?
> Basically, the handshake signals of the input and output ports are directly
> connected between them, only the data is modified between the ports.
>
> Nice change, working with RTL again. Will go back to the parallel unit
> tests, now.
:)
--
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 368] Need one example unit test of how to run some assembly code "qemu vs simulator" rather than "qemu vs hardware"
From: bugzilla-daemon @ 2020-06-07 22:48 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-368-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=368
--- Comment #4 from Michael Nolan <mtnolan2640@gmail.com> ---
Oh, since the actual debug interface uses gdb and has nothing to do with qemu,
it might be possible to run the generated programs under gdb on power hardware.
--
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 368] Need one example unit test of how to run some assembly code "qemu vs simulator" rather than "qemu vs hardware"
From: bugzilla-daemon @ 2020-06-07 22:47 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-368-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=368
--- Comment #3 from Michael Nolan <mtnolan2640@gmail.com> ---
We could also do what I did originally. It's not particularly elegant, but at
the end of a program where I wanted to check CR, I manually added a mfcr
$some_register to the end. It won't allow us to check everything in lockstep,
but it will let us verify that the two simulators produce the same results for
a given program.
--
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 366] Create new buzilla product "Systemes Libres Organization"
From: bugzilla-daemon @ 2020-06-07 22:45 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-366-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=366
--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #3)
> Since there hasn't been any discussion of this yet, but I need a place to
> share the pitch that I'm working on to get technical and 'polish' feedback,
> I would like to create a page for collaborative editing of the pitch deck on
> the wiki. Titled "Systemes Libres Amazon Alexa IOT Pitch 10-JUN-2020".
fine with me? suggest link from here https://libre-soc.org/systemes_libre/
--
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 366] Create new buzilla product "Systemes Libres Organization"
From: bugzilla-daemon @ 2020-06-07 22:39 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-366-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=366
--- Comment #3 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Cole Poirier from comment #2)
> (In reply to Luke Kenneth Casson Leighton from comment #1)
> > i like this idea: it does however have implications that systemes-libre
> > (the Company) is the same as "Libre-SOC the .org", which is not the case.
> > i have no problem with using libre-soc as an interim home for SL.
>
> I see your point. Is this the place to clarify the relationship between the
> two entities? I think that this kind of clarification that needs to be
> handled in an organized and publicly documented manner, which is why I was
> recommending we use the libre-soc-org mailing list. Once this is clarified,
> perhaps it is actually a systemes-libres-org mailing list that is needed?
Since there hasn't been any discussion of this yet, but I need a place to share
the pitch that I'm working on to get technical and 'polish' feedback, I would
like to create a page for collaborative editing of the pitch deck on the wiki.
Titled "Systemes Libres Amazon Alexa IOT Pitch 10-JUN-2020". I think before I
do so however I need input/permission on whether this is allowed/the right
approach from Yehowshua, Luke, or Jacob, because I don't understand the exact
nature of the relationship between Libre-SOC and Systemes Libre.
--
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 368] Need one example unit test of how to run some assembly code "qemu vs simulator" rather than "qemu vs hardware"
From: bugzilla-daemon @ 2020-06-07 22:39 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-368-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=368
--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #1)
> Ok, I did this quite a while ago, testing against my crappy handwritten
> python simulator. I'll give testing against the pseudocode simulator
> tomorrow a go.
that would be superb.
> Beware, from what I remember only general purpose registers work. qemu-gdb
> seemed to have a bug (or maybe it's qemu? idk) where you couldn't read out
> XER, CR, and friends directly from gdb.
hmmm... we could cheat, in a similar way to how gdb itself works: substitute
some instructions, actually execute mfcrf and mfmsr etc. directly putting
the result into a register, read *that*, then restore them afterwards.
or, it could just be that python-gdb doesn't have the capability added yet.
at least however if we can check int registers, then another hack-way to
do it would be to actually add, into the assembly listing being emulated,
the instruction to copy out to RT. it's a bad hack.
--
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 325] create POWER9 TRAP pipeline
From: bugzilla-daemon @ 2020-06-07 22:34 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-325-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=325
--- Comment #85 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #83)
> (In reply to Cole Poirier from comment #81)
> > (In reply to Luke Kenneth Casson Leighton from comment #80)
> i basically disregarded entirely the statement at the top of the POWER v3.0B
> PDF, "this pseudocode is in no way intended to be an executable language"
> and did exactly that. teehee
Seems to have saved us many months of work!
> > Ah, so just translating that
> > psuedo code into the TRAP method of ISACaller?
>
> yeeees :)
Makes sense :)
> so i saw the latest commit, and added some TODO comments. if you
> can do them *at the same time* as actually adding things in
> caller.py ISACAller.TRAP, then you will see clearly the direct connection
> between the two.
Perfect, will do.
> oh - yes, add a test_twi (or test_tdi) as well, you will have to
> set an initial register RA, such as:
>
> initial_regs = [0] * 32
> initial_regs[2] = random.randint(0, (1<<32)-1)
>
> or maybe do a fixed number, initially, so you know exactly what
> you are testing against. remember if you set initial_regs[2]
> then that means that "RA" in the instruction has to be 2.
> from fixedtrap.mdwn:
>
> D-Form
>
> * twi TO,RA,SI
>
> therefore, what you put in the listing, would have to be twi TO,-->2<--,SI
>
>
> TO is a bitfield, saying whether you want to compare equals, greater,
> less-than etc. etc.
>
> SI is an immediate that you want to compare against register RA.
>
> so just pick something that, *manually*, you know will be "equal", or
> something.
Thanks, very helpful, will do as well.
--
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 368] Need one example unit test of how to run some assembly code "qemu vs simulator" rather than "qemu vs hardware"
From: bugzilla-daemon @ 2020-06-07 22:34 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-368-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=368
Michael Nolan <mtnolan2640@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mtnolan2640@gmail.com
--- Comment #1 from Michael Nolan <mtnolan2640@gmail.com> ---
Ok, I did this quite a while ago, testing against my crappy handwritten python
simulator. I'll give testing against the pseudocode simulator tomorrow a go.
Beware, from what I remember only general purpose registers work. qemu-gdb
seemed to have a bug (or maybe it's qemu? idk) where you couldn't read out XER,
CR, and friends directly from gdb.
--
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 325] create POWER9 TRAP pipeline
From: bugzilla-daemon @ 2020-06-07 22:32 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-325-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=325
--- Comment #84 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #82)
> (In reply to Cole Poirier from comment #79)
> > (In reply to Luke Kenneth Casson Leighton from comment #75)
>
> > > the normal solution for this is to "call in" something that *is* known,
> > > and that would be the qemu emulator. except we kinda need some help from
> > > michael to do that in a short timescale, or we need to investigate it
> > > in a longer one. given that there's a critical task needed (investigating
> > > the CR bit-ordering) i'd rather we not pull him off of that.
> >
> > So until we have the known qemu emulator I should just try writing
> > appropriate unit tests for when we have the emulator working? Should I raise
> > a bug report for investigating the qemu powerpc emulator on a longer
> > timescale?
>
> yes please.
>
> > What should I say in the bug description?
>
> that we need one example unit test of how to run some assembly code
> "qemu vs simulator" rather than "qemu vs hardware"
>
> or, even just "qemu with some asserts" but looking *exactly* like how
> it's done in the simulator, right now.
>
> and that ultimately it should be possible to have a runtime switch
> (or a suite of tests) that allow us to verify *aaalll* the simulator
> test_pipe_caller.py tests, in the following way:
>
> * simulator vs qemu
> * qemu vs hardware
> * hardware vs simulator
>
> later i would very much like to be able to add microwatt to that list.
Done https://bugs.libre-soc.org/show_bug.cgi?id=368
--
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 368] New: Need one example unit test of how to run some assembly code "qemu vs simulator" rather than "qemu vs hardware"
From: bugzilla-daemon @ 2020-06-07 22:31 UTC (permalink / raw)
To: libre-riscv-dev
https://bugs.libre-soc.org/show_bug.cgi?id=368
Bug ID: 368
Summary: Need one example unit test of how to run some assembly
code "qemu vs simulator" rather than "qemu vs
hardware"
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: PC
OS: Linux
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Formal Verification
Assignee: lkcl@lkcl.net
Reporter: colepoirier@gmail.com
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
We need one example unit test of how to run some assembly code
"qemu vs simulator" rather than "qemu vs hardware"
or, even just "qemu with some asserts" but looking *exactly* like how
it's done in the simulator, right now.
and that ultimately it should be possible to have a runtime switch
(or a suite of tests) that allow us to verify *aaalll* the simulator
test_pipe_caller.py tests, in the following way:
* simulator vs qemu
* qemu vs hardware
* hardware vs simulator
later i would very much like to be able to add microwatt to that list.
<https://bugs.libre-soc.org/show_bug.cgi?id=325#c82>
--
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 365] ROCM/Libre-SOC GPU Opcode interoperability
From: bugzilla-daemon @ 2020-06-07 21:39 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-365-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=365
--- Comment #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Yehowshua from comment #11)
> (In reply to Jacob Lifshay from comment #7)
> > From what I understand, ROCm is only for OpenCL/CUDA-style compute, it
> > doesn't implement the Vulkan or OpenGL APIs:
> > https://github.com/RadeonOpenCompute/ROCm/issues/706
> > https://github.com/RadeonOpenCompute/ROCm/issues/131
>
> Hi Jacob, you are correct - however - Mesa has a Vulkan implementation that
> can sit on top of ROCM.
from 706:
"ROCm is AMD's compute stack. If you want Vulkan support, you have two options.
1) the Mesa community RADV driver or 2) AMD's AMDVLK driver (which should be
also part of their AMDGPU-PRO driver)."
my interpretation of that is that he hasn't explicitly said "no" (which is
where the confusion comes about), he's said, "if you want vulkan, you need RADV
or AMDVLK" from which we *deduce* that there is no connection between the two.
now, given that AMDGPU llvm support is now upstream, it *might* be the case
that two out of three of these projects *happen* to use the exact same
AMDGPU llvm compiler support.
my understanding of AMDVLK - jacob will be able to clarify - is that it's
a radically different approach, basically a sort-of effort to port and
libre-license what was formerly a proprietary Win32 driver to linux, where
the team working on it were isolated from what went into the upstream
AMDGPU llvm.
--
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 325] create POWER9 TRAP pipeline
From: bugzilla-daemon @ 2020-06-07 21:31 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-325-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=325
--- Comment #83 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #81)
> (In reply to Luke Kenneth Casson Leighton from comment #80)
> > it is... however look at the PDF SPEC (or see comment #1 which contains
> > the pseudo-code. that's not a function, is it?
>
> No indeed it seems more similar to a keyword.
i basically disregarded entirely the statement at the top of the POWER v3.0B
PDF, "this pseudocode is in no way intended to be an executable language"
and did exactly that. teehee
> Ah, so just translating that
> psuedo code into the TRAP method of ISACaller?
yeeees :)
> > @inject()
> > def op_twi(self, RA):
> > a = EXTS(RA[32:64])
> > if lt(a, EXTS(SI)) & TO[0]:self.TRAP()
> > if gt(a, EXTS(SI)) & TO[1]:self.TRAP()
> >
> >
> > *now* it can call the function which was added in caller.py, *now* we
> > can get that function to make the required modifications to the SPRs
> > and to the PC (NIA - Next Instruction Address).
>
> Aha, this is actually starting to make A LOT of sense :)
ta-daaaa :)
so i saw the latest commit, and added some TODO comments. if you
can do them *at the same time* as actually adding things in
caller.py ISACAller.TRAP, then you will see clearly the direct connection
between the two.
oh - yes, add a test_twi (or test_tdi) as well, you will have to
set an initial register RA, such as:
initial_regs = [0] * 32
initial_regs[2] = random.randint(0, (1<<32)-1)
or maybe do a fixed number, initially, so you know exactly what
you are testing against. remember if you set initial_regs[2]
then that means that "RA" in the instruction has to be 2.
from fixedtrap.mdwn:
D-Form
* twi TO,RA,SI
therefore, what you put in the listing, would have to be twi TO,-->2<--,SI
TO is a bitfield, saying whether you want to compare equals, greater, less-than
etc. etc.
SI is an immediate that you want to compare against register RA.
so just pick something that, *manually*, you know will be "equal", or
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 365] ROCM/Libre-SOC GPU Opcode interoperability
From: bugzilla-daemon @ 2020-06-07 21:23 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-365-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=365
--- Comment #11 from Yehowshua <yimmanuel3@gatech.edu> ---
(In reply to Jacob Lifshay from comment #7)
> From what I understand, ROCm is only for OpenCL/CUDA-style compute, it
> doesn't implement the Vulkan or OpenGL APIs:
> https://github.com/RadeonOpenCompute/ROCm/issues/706
> https://github.com/RadeonOpenCompute/ROCm/issues/131
Hi Jacob, you are correct - however - Mesa has a Vulkan implementation that can
sit on top of ROCM.
--
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: next prev 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