* Re: [libre-riscv-dev] Introduction
From: Staf Verhaegen @ 2020-06-16 8:50 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <6FD98A7F-B751-48AE-8829-0CBD38F1CFF6@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 582 bytes --]
Cole Poirier schreef op ma 15-06-2020 om 18:09 [-0700]:
>
>
> Yes that’s precisely what inspired this idea, Luke and I were talking about Kanban and I started to think of ways we could enhance it to use all of the data from the bugzilla rest API.
Have you guys validated gitlab ?
It seems you guys are trying to reinvent the wheel. gitlab for example
has issue boards, supports check lists in issues etc.
gitlab the company may not be better the Microsoft but the source code
is free. You can host your own gitlab, like the LIP6 people are doing.
greets,
Staf.
[-- 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] Introduction
From: Cole Poirier @ 2020-06-16 3:30 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5e988DJXpocp30cHYX9p8F_+AsBVz310xfm216OJtOtQ@mail.gmail.com>
> On Jun 15, 2020, at 8:04 PM, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> At least C++ is type safe, printf is a security nightmare, especially
> when using a dynamic format string.
Yikes!
> Also, openstreetmaps is definitely the place to get data if building a
> maps application. It's good enough that Apple used it to jump start
> their maps app (unfortunately without giving credit -- they got into
> deep trouble for that)
Yeah it’s the standard 2nd semester 2nd year ECE project at the University of Toronto, and they use openstreetmaps. Oh apple!
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 15jun2020
From: Jacob Lifshay @ 2020-06-16 3:08 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDy+jJ6ifvjMSOrn51v-Bs6qdXa6ZELT_r8TDRH7qx8uyQ@mail.gmail.com>
planning on working on the div pipeline today, many other things have
distracted from that.
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] Introduction
From: Jacob Lifshay @ 2020-06-16 3:03 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <6FD98A7F-B751-48AE-8829-0CBD38F1CFF6@gmail.com>
On Mon, Jun 15, 2020 at 6:09 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
>
> > On Jun 15, 2020, at 3:51 PM, Jacob Lifshay <programmerjake@gmail.com> wrote:
> >
> > You may want to learn Rust since it's being used for Kazan (the Vulkan 3D
> > graphics driver), as well as an IEEE 754 reference floating-point
> > implementation, an algebraic numbers library (basically computing using
> > exact real numbers using *lots* of number theory magic; the reference FP
> > implementation uses it to do arithmetic), and a few other parts of our
> > project.
> >
> > Also, I find Rust to be awesome coming from a background in C/C++. No more
> > mysterious SIGSEGV or buffer overflows! (had quite a few of those in the
> > old C++ version of my Minecraft-like game.) Also, Rust makes it easy to
> > manage your source code when building a project since it has an awesome
> > package/build manager named cargo. It's the #1 most loved language on
> > stackoverflow 4 years in a row for a good reason! (I'll just leave it at
> > that for now, I could go on for pages)
> >
> > https://stackoverflow.blog/2020/01/20/what-is-rust-and-why-is-it-so-popular/
>
> Hehe Jacob I’m a kindred spirit. While she was writing a google maps clone for school in c++ I tried to help her once or twice and she got annoyed at how many times I got frustrated at simple things like “cout << endl” and said “this would be so much easier in rust!”
At least C++ is type safe, printf is a security nightmare, especially
when using a dynamic format string.
Also, openstreetmaps is definitely the place to get data if building a
maps application. It's good enough that Apple used it to jump start
their maps app (unfortunately without giving credit -- they got into
deep trouble for that)
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] Minerva L1 Cache
From: Cole Poirier @ 2020-06-16 1:58 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwdh13WjzASgbWtX1MGUbfySAT3sFKhoC-0HYa3tJMtig@mail.gmail.com>
> On Jun 15, 2020, at 6:54 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> On Tuesday, June 16, 2020, Cole Poirier <colepoirier@gmail.com> wrote:
>
>> wiki page and also calm my growing sense of being overwhelmed. Order and
>> prioritization once done will quell this.
>
>
> use the priority field thing on the bugtracker
I need something much more substantial than that where I can get quite granular and use checklists and other tools. Will get this implemented in time on the to-be-built bugzilla front end, but until then I will be using a tool that has this functionality privately to organize my thoughts and mirroring my conclusions on the bug tracker and my wiki.
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] Minerva L1 Cache
From: Luke Kenneth Casson Leighton @ 2020-06-16 1:53 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <AB600EE9-F7C0-4B64-8620-D1029524C0EA@gmail.com>
On Tuesday, June 16, 2020, Cole Poirier <colepoirier@gmail.com> wrote:
> wiki page and also calm my growing sense of being overwhelmed. Order and
> prioritization once done will quell this.
use the priority field thing on the bugtracker.
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] Minerva L1 Cache
From: Cole Poirier @ 2020-06-16 1:39 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw-Rb1PT=-82wr3Rx_kjo8pUBWPQRQJ-DWac_22yVGAbA@mail.gmail.com>
> On Jun 15, 2020, at 2:55 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> at line 114 a response is expected to come back indicating that the
> address is "ok" or that there was an error [currently this is ignored,
> because there's no exception code - Cole - TRAP pipeline....]
Will work on this tomorrow. Just trying to get my head above water with organizing all of my new tasks and onboarding the two new members (hehe my sisters). Will spend 1/3 of my time tomorrow on *actual* work that furthers the product, spend the other two thirds helping Anais get setup and learning nmigen, and if not finishing hopefully getting half way through organizing my todos. So I can finally update my wiki page and also calm my growing sense of being overwhelmed. Order and prioritization once done will quell this.
Col
_______________________________________________
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] Introduction
From: Cole Poirier @ 2020-06-16 1:09 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7coX-Y7fo=BDQ+_Ju3gsZqyJY3w1KS3SLy+UNE9o6Z9Q@mail.gmail.com>
> On Jun 15, 2020, at 3:51 PM, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> You may want to learn Rust since it's being used for Kazan (the Vulkan 3D
> graphics driver), as well as an IEEE 754 reference floating-point
> implementation, an algebraic numbers library (basically computing using
> exact real numbers using *lots* of number theory magic; the reference FP
> implementation uses it to do arithmetic), and a few other parts of our
> project.
>
> Also, I find Rust to be awesome coming from a background in C/C++. No more
> mysterious SIGSEGV or buffer overflows! (had quite a few of those in the
> old C++ version of my Minecraft-like game.) Also, Rust makes it easy to
> manage your source code when building a project since it has an awesome
> package/build manager named cargo. It's the #1 most loved language on
> stackoverflow 4 years in a row for a good reason! (I'll just leave it at
> that for now, I could go on for pages)
>
> https://stackoverflow.blog/2020/01/20/what-is-rust-and-why-is-it-so-popular/
Hehe Jacob I’m a kindred spirit. While she was writing a google maps clone for school in c++ I tried to help her once or twice and she got annoyed at how many times I got frustrated at simple things like “cout << endl” and said “this would be so much easier in rust!”
> That would be really helpful, currently we don't have a very good solution
> (manually updating pages on the wiki when we remember).
Yes that’s precisely what inspired this idea, Luke and I were talking about Kanban and I started to think of ways we could enhance it to use all of the data from the bugzilla rest API. Too many emails are currently being sent that don’t get raised as bug reports and the whole structure of bugzilla while very useful for discussions, is not good for keeping track of things from a high level. This should eventually help cover budgets and road maps as well. I’ll just be cloning different functionality from various kanban/planner type online services, and adapting them to precisely fit our needs.
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] L1 cache and GPU workloads
From: Jacob Lifshay @ 2020-06-16 0:20 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxJmVR=hNgRiBGLJ4DZkjY5BcrihapTjfEZ43vJL8r0hw@mail.gmail.com>
On Sun, Jun 14, 2020, 21:04 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> <snip>
> to explain (summarising detailed and indepth discussions that have taken
> place over the past year and a half, learning from many different people):
>
> because we are splitting into twin L1 caches, and because GPU parallel
> non-overlapping workloads (particularly texture data) make ineffective use
> of L1 caches, expanding the tag size may not be of as much value as might
> otherwise be expected.
>
> it would be much more useful to add "cache line pinning" such that a GPU
> workload only uses a fractional percentage of the cache.
>
> this would stop a massively parallel non-overlapping workload from flooding
> the L1 Cache with data that is neverrrr going to be referred to agai.
>
Do note that a lot of a GPU workload will be rewriting a memory chunk over
and over again because of triangles being drawn on top of other triangles,
as well as using several potentially-colliding memory buffers and textures,
where it's quite common to load from the same section of texture
repeatedly, since each texture sampling operation will read a potentially
large group of adjacent pixels (called a footprint) in order to interpolate
between them.
Also, we want our processor to be good at CPU tasks as well, so having a L1
cache with more than 2 sets is advantageous.
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] Minerva L1 Cache
From: Luke Kenneth Casson Leighton @ 2020-06-16 0:03 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <EC2F0B70-33B0-4FCC-B2D3-F1918F36140C@gatech.edu>
On Mon, Jun 15, 2020 at 11:20 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> >
> > I reached out to Jean Paul
>
> Sorry, Jean Francois - not Jean Paul.
ah good. donations _are_ available. last time they said, "oh we work
for a company, we couldn't possibly take _donations_" *face-palm*...
now of course things have changed, maybe they will not turn down
money, ehn? *sigh*.
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] using debian on a mac
From: Luke Kenneth Casson Leighton @ 2020-06-16 0:01 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7hu1KDhXF21YG5DRQ=uK3JDoFQ8AJAbxsgNAhJ3ZHH_w@mail.gmail.com>
On Mon, Jun 15, 2020 at 11:20 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> One thing you could do is run debian on an external USB drive -- when
> installing debian maybe put the /boot partition on the mac's internal
> storage and the / partition on the USB drive. That's what I'm doing for my
> home server, since it's an Odroid XU4
i love those!
ReFIND / ReFIT should allow booting from an external USB drive,
absolutely no problem.
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] Introduction
From: Luke Kenneth Casson Leighton @ 2020-06-15 23:59 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7coX-Y7fo=BDQ+_Ju3gsZqyJY3w1KS3SLy+UNE9o6Z9Q@mail.gmail.com>
On Mon, Jun 15, 2020 at 11:51 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> That would be really helpful, currently we don't have a very good solution
> (manually updating pages on the wiki when we remember).
on everybody's home page i've dropped a link to bugzilla with
"assigned bugs". your one is there, too, jacob:
https://libre-soc.org/programmerjake/
the homepage is how we keep track of who did what and consequently
whether they'll receive donations. consequently it's kiiinda in
everyone's interests to follow the protocol of keeping it up-to-date.
that way i don't have to do it. or, let me put it another way: if i
do, i'll consider it "administrative tasks" and allocate myself 10% of
the donation! :)
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] Yehowshua Tasks
From: Luke Kenneth Casson Leighton @ 2020-06-15 23:55 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <338F2BAA-7632-49AD-9769-12ECF1B52F84@gatech.edu>
On Mon, Jun 15, 2020 at 11:47 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> Hello again Luke,
>
> As I wrap up my thesis, I’d like to get into the flow of things more.
> I can put I about four hours a day on LibreSOC.
fantastic. that's a _lot_.
> 1. What are some tasks I can get started with right away?
(btw all of these, start by raising a bugreport. i'll catch up
tomorrow and link them in to various dependent tasks).
an immediately useful task: a unit test for harry ho's sram.py (which
the comments on the pull for nmigen-soc say he didn't have time to do)
would be invaluable. i will do a repo tomorrow for that.
some comments in soc/minerva/cache.py! there's virtually none - at
all - in the entire codebase, and it's a serious problem. the
comment-to-code ratio in soc is somewhere between 5% and sometimes as
high as 20%. minerva? 0% to 1%. cache.py is *zero* comments.
some references to *any* kind of online documentation about "what kind
of cache this is".
also, parameterising of the minerva code so that address and data
widths can be selected (128-bit, 64-bit, 32-bit)
also another useful task: LDSTSplitter needs to have the data bitwidth
multiplied by 8. rather embarrassingly i forgot to do that, and
consequently the mask is *bit* level not *byte* level :)
this involves multiplying ashift1 and ashift2 by 8, as well as using
the same Repl trick as used in LenExpand on mask1 and mask2:
l = []
print ("llen", llen)
for i in range(llen):
l.append(Repl(mask[i], 8))
comb += BYTEEXPANDED_mask.eq(Cat(*l))
that little trick turns a 16 *bit* mask into a 16 *byte* mask, where
each byte is either 0b00000000 or 0b11111111
the *expanded* masks can then be applied here:
comb += ld1.ld_i.eq((self.st_data_i << ashift1) &
BYTEEXPANDED_mask1)
comb += ld2.ld_i.eq((self.st_data_i >> ashift2) &
BYTEEXPANDED_mask2)
and at that point, LDSTSplitter is ready for use in DualPortSplitter
(or, we code-morph LDSTSplitter *into* DualPortSplitter).
this is how we will be dealing with mis-aligned requests (exactly as
in the diagram), so it's kinda strategically important.
> Mainly related to nMigen - I don’t have patience for QEMU
> right now. Last time I did extensive QEMU work was a pretty
> painful experience about a year ago.
yeh we're not going to modify qemu: the level of optimisations they've
added is far beyond the understandability we need at the moment.
_using_ qemu (see soc/simulator/test_sim.py) is a different matter.
> 2. I can go ahead and write a bench test for Minerva’s cache.
>
> 3. Also, how can I get more familiar with the LD/ST comp unit
> including the dual cache even/odd architecture from the YouTube
> video you linked to earlier today?
run the following - and carefully examine both the ilang file using
yosys "show", and load the resultant vcd files in gtkwave. they are
in order of simplest (lowest level leaf nodes) right the way up to
where things are at the moment.
* soc/experiment/l0_cache.py
see TestL0Cache. this will run a couple of LDs and STs directly.
they go straight into a TestMemory instance.
* soc/experiment/compldst_multi.py
(which sigh after getting the next tests working, that one doesn't.
will fix it tomorrow)
this will run some LD/STs through the Computation Unit interface.
this is pretty much exactly as described in Mitch's book... except
it's been converted to multi-signal (one REQ/GO per *register* rather
than a "global read" and "global write")
LDSTCompUnit is a more advanced (more REQ/GO signals) version of an
ALU MultiCompUnit. it is probably also worthwhile checking
soc/experiment/test/test_compalu_multi.py as well (which Cesar has
been working on).
see https://bugs.libre-soc.org/show_bug.cgi?id=336 and
https://bugs.libre-soc.org/show_bug.cgi?id=312
bear in mind that REQ/GO are basically ready/valid signalling and
follow the EXACT same protocol followed by AXI4 and Wishbone
signalling.
* soc/fu/compunit/test/test_ldst_compunit.py
this one runs *actual LD/ST instructions*, after actually decoding
them (with PowerDecode2) and throws the input in using the REQ/GO
protocol, followed by waiting for (and confirming) the output is as
expected using (surprise) the REQ/GO protocol. it also enumerates the
ISA Simulator memory and checks that the memory modifications are
identical
* soc/simple/test/test_core.py
this one runs *all* available unit tests - actual instructions, again
after actually decoding them. if you want to "only" test the LD/ST
ones, go to the bottom of the file and comment out everything but the
LDSTUnitTest.
the difference between this and test_ldst_compunit.py is it actually
grabs the inputs needed to go to the LDSTCompUnit (and all others)
*from the register file*. and likewise on output REQ/GO, puts the
results into the regfile.
the REQ/GO is *DIRECTLY* synchronised with the Regfile read-enable /
write-enable for the active port.
regarding the Dual Port Splitter: this code hasn't been written yet,
although the pieces are in place (use ctags -R and vim ":tag
{insertkeyword}" to navigate to these classes)
* DualPortSplitter
* LDSTSplitter
* LenExpand
* PortInterface
* DataMerger (this will be relevant later - not straight away)
> Is it related to the memory Hierarchy section in Mitch Alsup’s
> computer architecture chapter 10?
almost - not quite. i've had to go far beyond that although the
basics are there.
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] Introduction
From: Jacob Lifshay @ 2020-06-15 22:51 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAKdzrAz4XnsYNXrrc2Au5ci9XaqHNWO3iEwPtPxcQ4x0jcG=Cw@mail.gmail.com>
On Mon, Jun 15, 2020, 13:13 Anais Poirier <anais.shiraz@gmail.com> wrote:
> Hello All,
>
> My name is Anais, I'm a third year electrical and computer engineering
> student at the University of Toronto, and I am Cole Poirier's sister! I'm
> most interested in gaining knowledge and experience working on a hardware
> project.
Glad to have more people helping out!
I have limited experience with Assembly and Verilog as well as
> extensive experience with c/c++
You may want to learn Rust since it's being used for Kazan (the Vulkan 3D
graphics driver), as well as an IEEE 754 reference floating-point
implementation, an algebraic numbers library (basically computing using
exact real numbers using *lots* of number theory magic; the reference FP
implementation uses it to do arithmetic), and a few other parts of our
project.
Also, I find Rust to be awesome coming from a background in C/C++. No more
mysterious SIGSEGV or buffer overflows! (had quite a few of those in the
old C++ version of my Minecraft-like game.) Also, Rust makes it easy to
manage your source code when building a project since it has an awesome
package/build manager named cargo. It's the #1 most loved language on
stackoverflow 4 years in a row for a good reason! (I'll just leave it at
that for now, I could go on for pages)
https://stackoverflow.blog/2020/01/20/what-is-rust-and-why-is-it-so-popular/
but I am excited to learn Nmigen and hope
> to contribute to the Power Core. I am also the one who created the visual
> slides for the pitch last week and would like to help with the Elm
> Kanban/bug tracker visual front end for Bugzilla.
>
That would be really helpful, currently we don't have a very good solution
(manually updating pages on the wiki when we remember).
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
* [libre-riscv-dev] Yehowshua Tasks
From: Yehowshua @ 2020-06-15 22:47 UTC (permalink / raw)
To: Libre-RISCV General Development
Hello again Luke,
As I wrap up my thesis, I’d like to get into the flow of things more.
I can put I about four hours a day on LibreSOC.
1. What are some tasks I can get started with right away?
Mainly related to nMigen - I don’t have patience for QEMU
right now. Last time I did extensive QEMU work was a pretty
painful experience about a year ago.
2. I can go ahead and write a bench test for Minerva’s cache.
3. Also, how can I get more familiar with the LD/ST comp unit
including the dual cache even/odd architecture from the YouTube
video you linked to earlier today?
Is it related to the memory Hierarchy section in Mitch Alsup’s
computer architecture chapter 10?
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] using debian on a mac
From: Jacob Lifshay @ 2020-06-15 22:20 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <8E6E70EE-DE5E-44E3-AC63-DDC020530DE6@gatech.edu>
On Mon, Jun 15, 2020, 14:09 Yehowshua <yimmanuel3@gatech.edu> wrote:
> >
> > this could result in something incredibly important being missed, and
> > we have to become OS debugging experts to find out why.
>
> When I can afford a desktop, I’ll use Debian.
>
> Mac doesn’t have much storage for now so don’t want to do QEMU or dual
> boot.
>
One thing you could do is run debian on an external USB drive -- when
installing debian maybe put the /boot partition on the mac's internal
storage and the / partition on the USB drive. That's what I'm doing for my
home server, since it's an Odroid XU4 that boots off a (slow) sd card then
uses a much faster external USB 3 128GB flash drive as the root filesystem
-- it's worked just fine for several years. It also has a 6TB hdd attached
to it.
One consideration is you will probably want to spend a bit more to get a
faster USB drive -- maybe just get a USB to 2.5" sata drive adaptor and a
cheap SSD.
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] Minerva L1 Cache
From: Yehowshua @ 2020-06-15 22:19 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <F1BA77AC-E94C-4025-B476-F6E19D1ED1F2@gatech.edu>
>
> I reached out to Jean Paul
Sorry, Jean Francois - not Jean Paul.
Keep mixing them up.
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] Minerva L1 Cache
From: Luke Kenneth Casson Leighton @ 2020-06-15 21:54 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <36A521C7-583F-4562-8932-509898538E9B@gatech.edu>
On Mon, Jun 15, 2020 at 10:08 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> >
> > there *is* a test_cache.py already in that directory.
> > (i'm currently making all imports explicit)
>
> Right this is the formal.
>
> The formal doesn’t make it clear how to actually
> use the thing.
sigh this is what Samuel Falvo pointed out: he advocates two unit
tests. one formal, one standard. the formal one does code-coverage,
the standard one acts more as a "tutorial and demo".
minerva is missing that.
> Another question: what is the interface you want to the cache?
> I think you said you wanted to go with Minerva’s loadstore frontend?
yes. basically adapt this:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/experiment/l0_cache.py;hb=HEAD
so that it instead talks this:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/minerva/units/loadstore.py;hb=HEAD#l13
right now, L0CacheBuffer is talking *directly* to the nmigen Memory
rdport / wrport:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/experiment/l0_cache.py;hb=HEAD#l400
if those direct calls are replaced with calls that are compatible with
the Minerva LoadStoreUnitInterface, adapted to 64-bit-wide, then for a
1st version approximation we're "done".
the next task on from that
>
> Could be a bit tricky as the loadstore frontend uses stage specific
> bit masks.
LoadStoreUnitInterface.x_mask? that's perfect. it's exactly what's
needed. those are i assume byte-level write-enable lines, exactly as
needed. now, it's only 4 bits because the data width is only 32 bit:
those need to be expanded to 64 bit.
LDSTSplitter - when it's time to add that - *might* take care of the
128 bit cache-line requirement, however might not. we may simply have
to internally not be compliant with Wishbone for the paths between
L0CacheBuffer and LoadStoreUnitInterface.
this would mean LSUI.x_mask being 16 bit wide, x_store_data being 128
bit, m_load_data being 128 bit. and the L1 cache likewise widened to
128 bit, and given a 16 bit byte-enable line.
*that* - on the other side of the L1 cache - where it talks to actual
Wishbone - would be where a split to 2x 64-bit outgoing Wishbone
interfaces would be needed.
> Might be easier to morph the L1 cache to your needs directly.
>
> From your video, it seems that there is no instruction cache vs. data cache.
the video covers the data cache only. the instruction cache is
"normal" and we should - unit tests notwithstanding - be able to just
drop minerva I-Cache (units/fetch.py, adapting PCSelector) directly
into place.
the only reason i haven't done that already is because i don't feel
comfortable doing it without the proper unit tests confirming that
they're functional.
> Can you specify what interface you want to see from the cache’s perspective?
> I suspect the only change we need to make is set s1_stall to Const(0), and disable
> s2_addr in Minerva’s L1Cache.
i honestly don't know, i haven't investigated the code closely (only
just literally got to the point where it's needed) will try to go over
it.
*thinks*.... ah. we *do* actually have an AGEN phase, if that's what s1 is for?
at line 112 this is addr which is of type Data record which includes
an "ok" signal not just "data".
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/experiment/l0_cache.py;hb=HEAD#l112
at line 114 a response is expected to come back indicating that the
address is "ok" or that there was an error [currently this is ignored,
because there's no exception code - Cole - TRAP pipeline....]
and there *will* be a potential delay between the s1 reservation phase
and the s2 (commit) phase. the AGEN phase should say "yes you can, if
you acknowledge it, safely proceed. i will reserve the cache line
until you tell me go or cancel".
equally (particularly right now) the acknowledgement may actually be
combinatorial and immediate, so both these scenarios (delay, no-delay)
need to be taken into consideration, between s1 and s2.
btw, for later (when the scoreboards are added): up until that
"proceed or cancel" point, the Shadow Matrices will "hold" the actual
commit (s2 stage). ONLY when the s1 stage has said "yes if you really
want to do this it is absolutely safe to proceed, guaranteed 100%
success", *then* the shadow is dropped and the commit to memory
allowed to proceed.
if however that error comes back at the AGEN stage (s1), then the
Shadow Matrices are told "activate go-die, please - kill *EVERYTHING*
that is downstream of this instruction, *right* now".
so, ignoring scoreboards for now: it does indeed look like the Minerva
cache - and the LoadStoreUnitInterface - is precisely and exactly what
we need.
just modified to 64 bit wide data buses, and 48 bit address buses.
actually, parameteriseable with defaults to those values would be
better.
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 15jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-15 21:21 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <E17EA9BD-CFB6-414F-BA3C-117CCD48E775@getmailspring.com>
On Mon, Jun 15, 2020 at 10:12 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
> Yesterday: Mostly processing the huge list of todos I generated over my
> 3 hour convo with Luke on Saturday, as well as running some errands.
:)
_______________________________________________
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 15jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-15 21:20 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <A3CC338E-A1BB-46A6-8347-760CA3881DBD@gatech.edu>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Mon, Jun 15, 2020 at 9:04 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> >
> > what i might do for now is just drop in a small SRAM just to get
> > something working.
>
> You might already know, but you can do an SRAM like so:
yes - been using that as part of a semi-integrated thing in TstL0CacheBuffer:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/experiment/l0_cache.py;hb=HEAD#l507
which in turn uses TestMemory:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/experiment/testmem.py;hb=HEAD
which in turn uses nmigen Memory
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] Introduction
From: Luke Kenneth Casson Leighton @ 2020-06-15 21:17 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200615211538.hlqecjsk5yrliybp@topoi.pooq.com>
On Mon, Jun 15, 2020 at 10:15 PM Hendrik Boom <hendrik@topoi.pooq.com> wrote:
> > so it's actually *really serious* not to be using the exact same
> > development workflow as everyone else.
>
> Any chance the Mac might find problems the Debian doesn't?
given that it's python - and the tools (yosys etc.) that are
generating the HDL, and running the simulations on python (etc.) - not
in the slightest.
the only way that a mac would be actually useful is if it was a POWER9 core.
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] Introduction
From: Luke Kenneth Casson Leighton @ 2020-06-15 21:16 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <F247B4E4-3BC7-451A-8AEC-D20C4CBF4513@gatech.edu>
On Mon, Jun 15, 2020 at 10:13 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> Actually - I can do testing in Debian docker.
cool!
> Share the filesystem with docker mount.
yes :)
you only actually need around... 3-4 GBytes, if that. a full OS is
*not* needed. no GUI, no window manager - nothing. run Cole's
scripts and you should be up and installed very rapidly.
https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=hdl-dev-repos;hb=HEAD
https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=install-apt-reqs;hb=HEAD
https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=yosys-et-al;hb=HEAD
l.
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] Introduction
From: Hendrik Boom @ 2020-06-15 21:15 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDwvfxDLw1LYkOfYQTXhTJO7BFaH1DcmZxDQs-xUz2cfjg@mail.gmail.com>
On Mon, Jun 15, 2020 at 09:49:05PM +0100, Luke Kenneth Casson Leighton wrote:
> On Mon, Jun 15, 2020 at 9:28 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
> >
> > Also, I believe Cole had mentioned that you’re using a Mac?
>
> ah. right. okay. we're not supporting macs, and we're not going to
> do development on macs. there are two aspects to this:
>
> 1). when it comes to the ASIC layout, it is absolutely critical - and
> is Industry Standard Practice - to have full reproducible builds. not
> even the username is different. everyone doing the builds sets up
> carbon-copy machines, where you could literally do a file-system
> byte-level comparison and find absolutely everything is the same.
>
> this is abbbsolutely essential when you are about to drop USD $5m on a
> chip tape-out... oh but the last person who checked the build used
> some totally different library and now "it doesn't work", finding the
> discrepancy results in time lost, you miss the tape-out window
> entirely, and the company loses a USD $100 million dollar deal because
> of it.
>
> so it's actually *really serious* not to be using the exact same
> development workflow as everyone else.
Any chance the Mac might find problems the Debian doesn't?
-- 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] Introduction
From: Luke Kenneth Casson Leighton @ 2020-06-15 21:13 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <8E6E70EE-DE5E-44E3-AC63-DDC020530DE6@gatech.edu>
On Mon, Jun 15, 2020 at 10:08 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> >
> > this could result in something incredibly important being missed, and
> > we have to become OS debugging experts to find out why.
>
> When I can afford a desktop, I’ll use Debian.
biggest amount of RAM you can get. i know someone (Rudi) who last
year bought 128 GB of DDR4 RAM, a USD 1000 motherboard, and then spent
USD 2,000 on the actual processor. he said getting it into Thailand
was a real nuisance: it's so powerful that it's export-restricted (!)
> Mac doesn’t have much storage for now so don’t want to do QEMU or dual boot.
ahh yeh that's a pain. ah well, we work with what we have.
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] Introduction
From: Yehowshua @ 2020-06-15 21:13 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <8E6E70EE-DE5E-44E3-AC63-DDC020530DE6@gatech.edu>
Actually - I can do testing in Debian docker.
Share the filesystem with docker mount.
Fair enough!
Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
page: 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