* Re: [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-09 19:01 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDyws116d9oKzSPhx6MpH-8C-ncfd+uPH6D6hgVG7+63Cg@mail.gmail.com>
On Jun 9 2020, at 3:34 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> 0:49 - billions of cryptocurrency is lost if the hardware wallet
> cryptochip cannot be trusted.
>
> that's the "fear" version. do we want to present a "fear" strategy?
> (you know what i mean)
>
> rework:
>
> 0:49 - cryptocurrency hardware wallets and banking identification
> terminals containing cryptochips can be trusted if the hardware is
> formally verified and the entire HDL available for a full independent
> audit.
Thanks, I like that formulation much better. I'll make these edits on
the wiki page, and send a link with the updated video later today. Or
Yehowshua may be able to embed the presentation. We will see.
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] wishbone does not have byte-enable (but it does have user-tags)
From: Cole Poirier @ 2020-06-09 19:18 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDzJk8kSdabL3P9VCaE-UyusYtTpBC6kH6LovoucjxJNTQ@mail.gmail.com>
On Jun 9 2020, at 10:10 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> also i've noticed that there is the concept of user and cycle "tags"
> which can be optionally added. this would give us a way to do
> cache-line tagging and many other things.
I have an ignorant question about wishbone. Is it possible that there is
functionality in OpenCAPI that would be beneficial to extend wishbone
with, and not time prohibitive (not for Oct 2020 tapeout but for the
quad-core gpu capable version)? This is assuming that implementing a
part of OpenCAPI in wishbone is legally permitted, which I am also
ignorant of.
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] mortbopet/Ripes: A graphical processor simulator and assembly editor for the RISC-V ISA
From: Cole Poirier @ 2020-06-09 19:25 UTC (permalink / raw)
To: Libre-RISCV General Development
Hi Libre-SOC developers,
I came across this graphical processor simulator for the RISC-V ISA:
https://github.com/mortbopet/Ripes. Is this possibly valuable to us?
Would it be possible for us to use this as a foundation or is it too
specific to RISC-V?
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 325] create POWER9 TRAP pipeline
From: bugzilla-daemon @ 2020-06-09 19: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 #90 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #89)
> ok so i added two new signals to Decode2Execute1Type, called
> traptype and trapaddr. the idea is that rather than get main_stage.py
> to *hard-code* what type of trap it is, and *hard-code* the address to
> jump to, the *decoder* says what the trap type is, and where to jump to.
>
> in this way we can detect interrupts, privileged instructions, and so on,
> in the *decoder*.
>
> unfortunately... this means that the decoder needs access to MSR. whoops.
> this is slightly unfortunate, because up until now, PowerDecoder2 needed
> absolutely nothing - no information *at all* - about the "state". didn't
> need the PC, didn't need anything.
>
>
> + with m.If(op.internal_op == InternalOp.OP_TRAP):
> + comb += e.traptype.eq(TT_TRAP) # request trap interrupt
> + comb += e.trapaddr.eq(0x70) # addr=0x700 (strip first nibble)
> +
> + return m
>
> + # privileged instruction
> + with m.If(instr_is_privileged(m, op.internal_op, e.insn) &
> + msr[MSR_PR]):
> + # privileged instruction trap
> + comb += op.internal_op.eq(InternalOp.OP_TRAP)
> + comb += e.traptype.eq(TT_PRIV) # request privileged instruction
> + comb += e.trapaddr.eq(0x70) # addr=0x700 (strip first nibble)
Very cool. Can you comment on the implications of the decoder needing access to
MSR here? or is that meant to be a comment on a different bug report. If so,
please link it here, because I'd like to understand the decoder better. Going
to finally get to try the learning process involving gtkwave today!
--
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 09jun2020
From: Cole Poirier @ 2020-06-09 19:35 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDyugeW9YALUA3gXEvLdMVDStt62ODw4wcJfuK5icMZ+3A@mail.gmail.com>
On Jun 9 2020, at 6:11 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> yesterday:
>
> * reviewed slide deck
Thank you Luke, your help so far has already made the slide deck much
better. Looking forward to your comments as you have time to read. Not
as much of a rush now since the pitch has been moved to next wednesday :)
Yesterday: spent entire day writing slide deck
> * a bit on TRAP including adding a privilege testing function
> today:
>
> * a bit more on OP_TRAP
Today:
I'm excited to start writing unit tests for the TRAP pipeline today, and
to use the learning methodology you laid out on bug 325 for me that
involves looking at gtkwave timing diagrams.
_______________________________________________
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] mortbopet/Ripes: A graphical processor simulator and assembly editor for the RISC-V ISA
From: Luke Kenneth Casson Leighton @ 2020-06-09 20:13 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <700E837A-1AD9-40CD-90AD-04A3F6A308CF@getmailspring.com>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Tue, Jun 9, 2020 at 8:25 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
> Hi Libre-SOC developers,
>
> I came across this graphical processor simulator for the RISC-V ISA:
> https://github.com/mortbopet/Ripes. Is this possibly valuable to us?
> Would it be possible for us to use this as a foundation
maybe.
> or is it too specific to RISC-V?
there's a subdirectory "processors" which tends to suggest it may have
been planned to have more than one.
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 09jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-09 20:15 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <44227E61-E658-4CBA-9ECE-CC4A193E3471@getmailspring.com>
On Tue, Jun 9, 2020 at 8:35 PM Cole Poirier <colepoirier@gmail.com> wrote:
> Today:
>
> I'm excited to start writing unit tests for the TRAP pipeline today, and
> to use the learning methodology you laid out on bug 325 for me that
> involves looking at gtkwave timing diagrams.
with michael having added the qemu-execution thing, you should now
first be able to add a "twi" (or tdi) instruction unit test to that,
first.
this will allow you to check that the *simulator* is correct.
then after you know that the *simulator* is correct, the same unit
test can be used in test_pipe_caller.py, and in that way you will then
be able to test that the *hardware* is correct.
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] wishbone does not have byte-enable (but it does have user-tags)
From: Luke Kenneth Casson Leighton @ 2020-06-09 20:17 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <35364624-676C-430C-A1EE-C9B88B12128C@getmailspring.com>
On Tue, Jun 9, 2020 at 8:18 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
> On Jun 9 2020, at 10:10 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> > also i've noticed that there is the concept of user and cycle "tags"
> > which can be optionally added. this would give us a way to do
> > cache-line tagging and many other things.
>
> I have an ignorant question about wishbone. Is it possible that there is
> functionality in OpenCAPI that would be beneficial to extend wishbone
> with,
honestly absolutely no idea. someone else might know.
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 325] create POWER9 TRAP pipeline
From: bugzilla-daemon @ 2020-06-09 20:59 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 #91 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #90)
> (In reply to Luke Kenneth Casson Leighton from comment #89)
> > ok so i added two new signals to Decode2Execute1Type, called
> > traptype and trapaddr. the idea is that rather than get main_stage.py
> > to *hard-code* what type of trap it is, and *hard-code* the address to
> > jump to, the *decoder* says what the trap type is, and where to jump to.
> >
> > in this way we can detect interrupts, privileged instructions, and so on,
> > in the *decoder*.
> >
> > unfortunately... this means that the decoder needs access to MSR. whoops.
> > this is slightly unfortunate, because up until now, PowerDecoder2 needed
> > absolutely nothing - no information *at all* - about the "state". didn't
> > need the PC, didn't need anything.
> >
> >
> > + with m.If(op.internal_op == InternalOp.OP_TRAP):
> > + comb += e.traptype.eq(TT_TRAP) # request trap interrupt
> > + comb += e.trapaddr.eq(0x70) # addr=0x700 (strip first nibble)
> > +
> > + return m
> >
> > + # privileged instruction
> > + with m.If(instr_is_privileged(m, op.internal_op, e.insn) &
> > + msr[MSR_PR]):
> > + # privileged instruction trap
> > + comb += op.internal_op.eq(InternalOp.OP_TRAP)
> > + comb += e.traptype.eq(TT_PRIV) # request privileged instruction
> > + comb += e.trapaddr.eq(0x70) # addr=0x700 (strip first nibble)
>
> Very cool. Can you comment on the implications of the decoder needing access
> to MSR here?
sigh it's annoying. however given that we gave to pass state information
around, containing the PC, adding the MSR to that,state is not so bad. it's
just that it messes with dependency tracking.
> or is that meant to be a comment on a different bug report. If
> so, please link it here, because I'd like to understand the decoder better.
the decoder's really not difficult. funnily enough i updated this page
https://libre-soc.org/Documentation/SOC/index/
it links to PowerDecoder. the thing yo remember is that there is no hardcoded
list of junk. i will edit the page further, or we discuss on list. thus
bugrrport us intended for TRAP
--
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 09jun2020
From: Cole Poirier @ 2020-06-09 21:01 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDxcRF8mmQrGBwewE82fuhWq2G4RwrXmJmmcPOjzaWN0CQ@mail.gmail.com>
On Jun 9 2020, at 1:15 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> with michael having added the qemu-execution thing, you should now
> first be able to add a "twi" (or tdi) instruction unit test to that,
> first.
This is filling in the pseudo-code for the soc/decoder/isa/caller.py?
> this will allow you to check that the *simulator* is correct.
How do I use qemu to verify that the simulator is correct? Sorry I've
looked on the bug report and the wiki? Is there a wiki page with the
procedure? If not, what's the procedure I should follow?
> then after you know that the *simulator* is correct, the same unit
> test can be used in test_pipe_caller.py, and in that way you will then
> be able to test that the *hardware* is correct.
Sounds like a plan.
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] daily kan-ban update 09jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-09 21:48 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <AB73C9E5-F9FC-4FD7-802E-B04DE2533149@getmailspring.com>
On Tue, Jun 9, 2020 at 10:01 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
> On Jun 9 2020, at 1:15 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> > with michael having added the qemu-execution thing, you should now
> > first be able to add a "twi" (or tdi) instruction unit test to that,
> > first.
>
> This is filling in the pseudo-code for the soc/decoder/isa/caller.py?
yeees... however the first thing to do is write the unit test. then
you have a means by which the code in caller.py py will be... called.
without writing the unit test, you have no way to call that code,
therefore how can you know if what you write is correct?
> > this will allow you to check that the *simulator* is correct.
>
> How do I use qemu to verify that the simulator is correct?
well, first we recall that it was michael who added the code, under
the recent bugreport from monday. so we do this:
$ git log > /tmp/f
then, we open up that file, and grep "Michael". that shows this line:
commit 613b15043fc7302c8ad4495b6bff65063eb1c0e3
Author: Michael Nolan <mtnolan2640@gmail.com>
Date: Mon Jun 8 13:36:57 2020 -0400
Restore test_sim.py, begin modifying it for testing against qemu
that looks about right, doesn't it? (i don't know the answer, either,
however i am simply following a deductive reasoning trail, from
evidence left by michael).
so let's do a git diff
$ git diff 613b15 3a0b0f
and that shows (just as the comment says) a file called test_sim.py.
from the top of the diff it shows that that test_sim.py file is in
soc/simulator/test_sim.py
so now we know where that file is.
> Sorry I've
> looked on the bug report and the wiki? Is there a wiki page with the
> procedure? If not, what's the procedure I should follow?
you need to think through a process of deducing this information for yourself.
looking at that file, it's a unit test, isn't it? and it has the
exact same "run_tst_program" pattern that's in the test_pipe_caller.py
programs, doesn't it?
therefore, logically, if we put instructions in a unit test listing,
we expect them to be run, yes?
and if you look at test_sim.py's "run_tst_program()" function, we can
see that it has two aspects: the first being that the simulator's
"run_tst" function is called, and the second that the qemu
run_program() function is called.
each of those will modify their respective register files, and
qemu_register_compare walks through them and compares them, doesn't
it?
this really isn't hard to deduce!
therefore to test twi, we add a new unit test to that file, and run
it. now, it *may* fail (because it's a trap, and we don't actually
know how qemu will react to that). we'll cross that bridge when we
come to it, ok? we expect at least the PC to be changed to 0x700, so
will have to work out how to get the PC out of qemu.
in essence, here, there is a series - a chain - of logical deductive
reasoning that allows us, from a few well-known sources that we have
access to, to find the information that was sought.
being able to do this, regardless of the size of the codebase and
regardless of whether quotes documentation quotes exists, is an
absolutely essential and critically important skill.
it is however important that you appreciate and have confidence that
you *can* in fact deploy such techniques (or others like it) in order
to find what you seek.
when this particular technique has failed me (due to the codebase size
being over a quarter of a million lines) i have been known to print it
out entirely on double-sided double-column pages (where an 80 char
limit has been absolutely essential in meeting that), and literally
going through absolutely every single page in the course of a day,
speed-reading flicking one by one, to get a "subconscious" handle on
the codebase that then allows me to go "i've seen that before" and
stand a chance of being able to find it relatively quickly.
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] daily kan-ban update 09jun2020
From: Alain D D Williams @ 2020-06-09 21:49 UTC (permalink / raw)
To: nLibre-RISCV General Development
Sigh ... trying to get bzkanban working ......
I implemented the latest bugzilla - this works nicely (bugzilla that is, not bzkanban)
If you want to play with it you need to put this into your /etc/hosts
46.235.227.77 bugs-5.0.6.libre-soc.org
I can make that the current bugzilla if it does not break anything.
So: I then got bugzilla (5.0.6) working under another Debian 10 machine under
nginx with postgresql - that works.
Blood on my keyboard when I tried to get bzkanban working.
Run up Apache and, after a couple of sillies, it works - bugzilla and bzkanban I mean.
Flip back & forth between the two - never under works nginx, always under
apache. I'm stopping - there is an Einstein quote popping up in my head.
So: if you want bzkanban - I can install apache & replace nginx. I'm *****ed
if I can see another way.
Is there a good reason for needing nginx ?
I'm off to bed.
--
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256 https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>
_______________________________________________
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: Hendrik Boom @ 2020-06-09 22:01 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAEg7hun9a8OZz3YOE+VxLr=mmzHeasO1mypntVd6zYm4x1sH9A@mail.gmail.com>
On Mon, Jun 08, 2020 at 06:17:17PM -0700, Cole Poirier wrote:
> Thank you Staf, Lauri, Hendrick, Jacob, and Luke, your provided
> insights, criticisms, and questions have allowed me to make a much
> more informative script for Wednesday's pitch. I'm still working on
> the revised script, however I now have a work-in-progress polished
> version of the presentation to show. There's a 1 min recorded video of
> the presentation available on youtube (unlisted) here
> (https://www.youtube.com/watch?v=0alD47XlsbM) if you'd like to take a
> look. Unfortunately youtube has lowered the quality. Also the
> script/text on the slides in the video is out of date and will be
> updated tomorrow.
Looked at it today. Seems somewhat OK, but on a few pages there's too
much text to read for the short time the page is on-screen.
-- hendrik
_______________________________________________
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 09jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-09 22:07 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxTQS-h-uqTfPkpfLmisMOpE7RL-F0bMLpw-510nNTeeg@mail.gmail.com>
euurrgh took a while
powerpc64-linux-gnu-gdb -interpreter=mi
~-data-list-register-names
^done,register-names=["r0","r1","r2","r3","r4","r5","r6","r7","r8","r9","r10","r11","r12","r13","r14","r15","r16","r17","r18","r19","r20","r21","r22","r23","r24","r25","r26","r27","r28","r29","r30","r31","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9","f10","f11","f12","f13","f14","f15","f16","f17","f18","f19","f20","f21","f22","f23","f24","f25","f26","f27","f28","f29","f30","f31","pc","msr","cnd","lr","cnt","xer","fpscr","mq"
ah HA! one of those is the condition register!
_______________________________________________
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 370] need a way to co-simulate hardware, qemu, microwatt, simulator, side-by-side
From: bugzilla-daemon @ 2020-06-09 22:08 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-370-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=370
--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
powerpc64-linux-gnu-gdb -interpreter=mi
~-data-list-register-names
^done,register-names=["r0","r1","r2","r3","r4","r5","r6","r7","r8","r9","r10","r11","r12","r13","r14","r15","r16","r17","r18","r19","r20","r21","r22","r23","r24","r25","r26","r27","r28","r29","r30","r31","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9","f10","f11","f12","f13","f14","f15","f16","f17","f18","f19","f20","f21","f22","f23","f24","f25","f26","f27","f28","f29","f30","f31","pc","msr","cnd","lr","cnt","xer","fpscr","mq"
that should do the trick. we can get at MSR, CR0-7 (cnd), XER, PC, LR, cnt is
probably CTR, mq i have no idea.
--
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 372] New: create cycle-accurate JIT-compiler-based processor simulator
From: bugzilla-daemon @ 2020-06-09 22:43 UTC (permalink / raw)
To: libre-riscv-dev
https://bugs.libre-soc.org/show_bug.cgi?id=372
Bug ID: 372
Summary: create cycle-accurate JIT-compiler-based processor
simulator
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Source Code
Assignee: lkcl@lkcl.net
Reporter: programmerjake@gmail.com
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
This could allow simulating our processor model much faster than most other
methods.
--
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 372] create cycle-accurate JIT-compiler-based processor simulator
From: bugzilla-daemon @ 2020-06-09 22:44 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-372-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=372
Jacob Lifshay <programmerjake@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|--- |Low
Assignee|lkcl@lkcl.net |programmerjake@gmail.com
CC| |programmerjake@gmail.com
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 372] create cycle-accurate JIT-compiler-based processor simulator
From: bugzilla-daemon @ 2020-06-09 22:46 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-372-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=372
--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
this will likely need to happen after the october tapeout, if at all.
--
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 09jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-09 22:48 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200609214936.GH14030@phcomp.co.uk>
On Tue, Jun 9, 2020 at 10:49 PM Alain D D Williams <addw@phcomp.co.uk> wrote:
>
> Sigh ... trying to get bzkanban working ......
>
> I implemented the latest bugzilla - this works nicely (bugzilla that is, not bzkanban)
>
> If you want to play with it you need to put this into your /etc/hosts
>
> 46.235.227.77 bugs-5.0.6.libre-soc.org
nicely done, alain. actually we can probably put that into the dns.
>
> I can make that the current bugzilla if it does not break anything.
>
>
> So: I then got bugzilla (5.0.6) working under another Debian 10 machine under
> nginx with postgresql - that works.
>
> Blood on my keyboard when I tried to get bzkanban working.
>
> Run up Apache and, after a couple of sillies, it works - bugzilla and bzkanban I mean.
hurrah!
> Flip back & forth between the two - never under works nginx, always under
> apache. I'm stopping - there is an Einstein quote popping up in my head.
:)
>
> So: if you want bzkanban - I can install apache & replace nginx. I'm *****ed
> if I can see another way.
>
> Is there a good reason for needing nginx ?
mmm... i switched all my web services (including for clients) over to
it after learning of its lower workload and greater security by
design.
if it's getting in the way, although it makes me slightly nervous we
can flip over to it.
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 372] create cycle-accurate JIT-compiler-based processor simulator
From: bugzilla-daemon @ 2020-06-09 22:53 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-372-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=372
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lkcl@lkcl.net
--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #0)
> This could allow simulating our processor model much faster than most other
> methods.
pearpc already contains both a JIT and a cycle-accurate mode.
there is also power-gem5 which was recently updated to be capable of
running a linux kernel (and the 500mb/sec memory leak fixed).
both of these are written in c / c++ and are extremely fast.
is there a compelling reason to, using an appropriate colloquialism,
"reinvent the wheel?"
(the main purpose of deliberately writing the simulator in python was to get
"working knowledge" handle on POWER9 internals: it's served that
purpose extremely well, and also very deliberately uses the exact same
POWER instruction decoder as used in the 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] AMD ISAs
From: Yehowshua @ 2020-06-09 23:15 UTC (permalink / raw)
To: Libre-RISCV General Development
All of AMDs ISA are open here.
https://gpuopen.com/documentation/amd-isa-documentation/ <https://gpuopen.com/documentation/amd-isa-documentation/>
It may be worthwhile trying to make our GPU “appear” to be an AMD device.
We wouldn’t have to write any drivers. At all.
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] AMD ISAs
From: Yehowshua @ 2020-06-09 23:16 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <1448919C-8B02-48C8-9B0D-9C03C64E1765@gatech.edu>
We could have a fake "PCIE AMD-like GPU" that AMD drivers talk to.
This device then issues instructions on the CPU/GPU hybrid.
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 372] create cycle-accurate JIT-compiler-based processor simulator
From: bugzilla-daemon @ 2020-06-09 23:17 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-372-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=372
--- Comment #3 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #2)
> (In reply to Jacob Lifshay from comment #0)
> > This could allow simulating our processor model much faster than most other
> > methods.
>
> pearpc already contains both a JIT and a cycle-accurate mode.
> there is also power-gem5 which was recently updated to be capable of
> running a linux kernel (and the 500mb/sec memory leak fixed).
>
> both of these are written in c / c++ and are extremely fast.
>
> is there a compelling reason to, using an appropriate colloquialism,
> "reinvent the wheel?"
I haven't heard of a simulator that is cycle-accurate and JIT-compiled at the
same time, all the ones I've seen before are one or the other (perhaps
dynamically switchable) but not both simultaneously.
This bug report was mostly just to record my idea since it would be useful,
rather than a strict requirement.
This could be used to do things like run a few tens or hundreds of billions of
cycles on a fpga and check that the entire pipeline state matches the simulator
exactly -- unless the simulator is quite fast, that isn't very practical simply
because the existing simulators are too slow or not cycle-accurate.
This is like a bounded-cycle-count formal proof (icr the right term) except
that we can run it for millions or billions of times as many cycles.
--
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] AMD ISAs
From: Yehowshua @ 2020-06-09 23:18 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <5B866D98-D803-4268-A0BC-3246E604BA33@gatech.edu>
I still support the path of writing our own drivers tailored to our
hybrid device in the future - but the AMD approach could definitely
be a low resistance path for our initial efforts.
Thoughts?
Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] AMD ISAs
From: Luke Kenneth Casson Leighton @ 2020-06-09 23:21 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <1448919C-8B02-48C8-9B0D-9C03C64E1765@gatech.edu>
On Wed, Jun 10, 2020 at 12:15 AM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> All of AMDs ISA are open here.
> https://gpuopen.com/documentation/amd-isa-documentation/ <https://gpuopen.com/documentation/amd-isa-documentation/>
>
> It may be worthwhile trying to make our GPU “appear” to be an AMD device.
the problem with doing so is that the processor effectively becomes
"Dual ISA". everyone that we've talked to with significant experience
in processor design has raised eyebrows at the complexity involved in
a dual-ISA design.
it is not an insurmountable issue: it just should in no way be
underestimated, for the trade-off of not having to write any kinds of
drivers.
in addition, we need to consider that the level of instruction
compression (which reduces shared L1 I-Cache usage) anticipated
through the hardware-level compression in SimpleV will be completely
unobtainable for AMDGPU ISA interoperability... because we will be
forced *to* have AMDGPU ISA interoperability.
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
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