* Re: [libre-riscv-dev] PPC on Talos and Playstation 3
From: Jacob Lifshay @ 2020-03-29 20:35 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAF1D9AC-F167-4B48-AE93-BADA36932AE8@gatech.edu>
On Sun, Mar 29, 2020, 13:18 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:
> So I was wondering how to run unit tests for the PPC FPU.
I'm planning on making files containing the list of test cases and expected
outputs by using the talos. That way, the unit tests can be run on any
computer without requiring a power processor.
We can obviously do this on the Talos server, but also playstation 3.
>
> I have some old PPC Macs, but they are 32 bit not 64 bit.
>
> Sony’s playstation 3 however is ppc64. Also, Sony officially supported
> Linux on PS3 FAT models only which you can pick up on eBay for $50 - $70.
>
another option is one of the power macs, since they are 64-bit and can have
multiple faster cores (unlike the PS3's single power core -- the cell
broadband engine cores are not power cores) and are much more easily
upgradable. I've seen some for around $100.
I know debian works on them since I used to have one but got rid of it when
moving several years ago.
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] Building Docker Containers
From: Cole Poirier @ 2020-03-29 20:51 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4P_1ZONMmqQ+tc92JiOTB4JHVW96akVwDvtZgX+HWvvg@mail.gmail.com>
On Mar 29 2020, at 1:02 pm, Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Sun, Mar 29, 2020, 12:58 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>> it would be good to have Makefiles and/or install.sh scripts and other
>> automated install things which can be called by people setting up from
>> scratch.
>
> The gitlab CI can be set up such that it just runs the install script, if
> needed. currently, the script is short enough that I don't think that's
> necessary.
> The install script and/or gitlab CI just runs the required make, setup.py,
> and/or cargo build commands.
>
> Jacob
Luke, I'm doing this on the Kazan gitlab in the libre-soc-dev-env-setup
repository
(https://salsa.debian.org/Kazan-team/libre-soc-dev-env-setup). I'm
planing on making many smaller scripts that each do only one spefic
thing (eg. install yosys, install all general software prereqs from apt,
etc.). These scripts can then be combined as needed for specific
purposes/set-ups. I will write the basic use cases as these
purpose-specific aggregations, specifically the entirety of the HDL
workflow setup.
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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-29 20:57 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=271
--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
what do you think of the idea of adding signals with the same name as
the fields?
btw i'm starting that mini-parser and will be looking to drop a dictionary
of the name of the instruction's form (Form-X) into the exec context, to
test them.
so actually creating signals (again, automatically and/or programmatically)
makes things slightly easier.
--
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] PPC on Talos and Playstation 3
From: Luke Kenneth Casson Leighton @ 2020-03-29 21:01 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAF1D9AC-F167-4B48-AE93-BADA36932AE8@gatech.edu>
On Sun, Mar 29, 2020 at 9:18 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> So I was wondering how to run unit tests for the PPC FPU. We can obviously do this on the Talos server, but also playstation 3.
>
> I have some old PPC Macs, but they are 32 bit not 64 bit.
>
> Sony’s playstation 3 however is ppc64. Also, Sony officially supported Linux on PS3 FAT models only which you can pick up on eBay for $50 - $70.
https://wiki.debian.org/PS3
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] Building Docker Containers
From: Luke Kenneth Casson Leighton @ 2020-03-29 21:12 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <09CE786B-DB06-49FE-88F1-AD2316DC25BA@getmailspring.com>
On Sun, Mar 29, 2020 at 9:52 PM Cole Poirier <colepoirier@gmail.com> wrote:
>
> On Mar 29 2020, at 1:02 pm, Jacob Lifshay <programmerjake@gmail.com> wrote:
> > On Sun, Mar 29, 2020, 12:58 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> > wrote:
> >> it would be good to have Makefiles and/or install.sh scripts and other
> >> automated install things which can be called by people setting up from
> >> scratch.
> >
> > The gitlab CI can be set up such that it just runs the install script, if
> > needed. currently, the script is short enough that I don't think that's
> > necessary.
> > The install script and/or gitlab CI just runs the required make, setup.py,
> > and/or cargo build commands.
> >
> > Jacob
>
> Luke, I'm doing this on the Kazan gitlab in the libre-soc-dev-env-setup
> repository
> (https://salsa.debian.org/Kazan-team/libre-soc-dev-env-setup).
i'd very much prefer that a resource - not managed by, not backed up
by, and not with the name of our overall project - on which we will
have people being critically dependent, "go to this random third party
website on which we are guests if you want to run install scripts to
get started" - is not the first place that we direct people to.
you see how that really doesn't look like we know what we're doing?
it's absolutely fine if we were a little team with a small goal that
didn't matter in the slightest, and, particularly, if we were not
seeking USD $10m investment i'd say "sure, use external third party
hosting on which we're guest users, advertising their kindness, and
that of the hosting company rather than our own competence".
so can you please give me a name for a repository that you'd like to
be created: i will create it on git.libre-riscv.org, set you (and
anyone else) as read-writers, and we can use that, yes?
if you'd like to mirror that elsewhere, you're more than welcome to do
so (as in: nobody can stop you). however the primary location - and
primary advertised location - really does have to be this project's
*own* services. not a random third party one, no matter how "good"
that service is.
> I'm
> planing on making many smaller scripts that each do only one spefic
> thing (eg. install yosys, install all general software prereqs from apt,
> etc.).
that's a really good idea. i wonder... i wonder if ikiwiki objects to
git submodules? it shouldn't....
if the scripting repo can be dropped (as a separate repo) into the
ikiwiki as a subdirectory, the scripts - and any documents - should
appear there directly as pages on the wiki.
> These scripts can then be combined as needed for specific
> purposes/set-ups. I will write the basic use cases as these
> purpose-specific aggregations, specifically the entirety of the HDL
> workflow setup.
look forward to it, as we will have interns for coriolis2 and i'd like
them to be able to get up and running with the exact same environment
in as short a time as possible.
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] Building Docker Containers
From: Cole Poirier @ 2020-03-29 21:34 UTC (permalink / raw)
To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDz3k4a1v3dereCQZtcaqjo4sG-bq59zfmF6Wk80ds0RVQ@mail.gmail.com>
On Mar 29 2020, at 2:12 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Sun, Mar 29, 2020 at 9:52 PM Cole Poirier <colepoirier@gmail.com> wrote:
>> Luke, I'm doing this on the Kazan gitlab in the libre-soc-dev-env-setup
>> repository (https://salsa.debian.org/Kazan-team/libre-soc-dev-env-setup).
> i'd very much prefer that a resource - not managed by, not backed up
> by, and not with the name of our overall project - on which we will
> have people being critically dependent, "go to this random third party
> website on which we are guests if you want to run install scripts to
> get started" - is not the first place that we direct people to.
>
> you see how that really doesn't look like we know what we're doing?
>
> it's absolutely fine if we were a little team with a small goal that
> didn't matter in the slightest, and, particularly, if we were not
> seeking USD $10m investment i'd say "sure, use external third party
> hosting on which we're guest users, advertising their kindness, and
> that of the hosting company rather than our own competence".
>
> so can you please give me a name for a repository that you'd like to
> be created: i will create it on git.libre-riscv.org, set you (and
> anyone else) as read-writers, and we can use that, yes?
>
> if you'd like to mirror that elsewhere, you're more than welcome to do
> so (as in: nobody can stop you). however the primary location - and
> primary advertised location - really does have to be this project's
> *own* services. not a random third party one, no matter how "good"
> that service is.
I'm with you completely Luke, I just thought to do this on gitlab
because it was on my mind while concurrently working on these env setup
scripts and the gitlab jacob-build-server setup script. I think our git
repo will be a much better place for this. Unfortunately, I'm currently
using a Debian desktop that I setup as a test, and wasn't planning on
using long term. Because of this I neglected to set it up properly using
the username that I would like to appear on my development work, so now
the name of the computer and the certs I used it to generate for my
libre-soc access are not my own. Before I step into the git repo fully,
I'd like to take this figurative milestone as an opprotunity to
reinstall my setup, and send you my new public key sometime today or
tomorrow. Is that alright luke?
>> I'm
>> planing on making many smaller scripts that each do only one spefic
>> thing (eg. install yosys, install all general software prereqs from apt,
>> etc.).
>
> that's a really good idea. i wonder... i wonder if ikiwiki objects to
> git submodules? it shouldn't....
>
> if the scripting repo can be dropped (as a separate repo) into the
> ikiwiki as a subdirectory, the scripts - and any documents - should
> appear there directly as pages on the wiki.
That would certainly be very cool!
>> These scripts can then be combined as needed for specific
>> purposes/set-ups. I will write the basic use cases as these
>> purpose-specific aggregations, specifically the entirety of the HDL
>> workflow setup.
>
> look forward to it, as we will have interns for coriolis2 and i'd like
> them to be able to get up and running with the exact same environment
> in as short a time as possible.
>
> l.
I'm aiming for the same goal, hopefully my first draft will be ready
around tuesday.
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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-29 23:15 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=271
--- Comment #4 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #3)
> what do you think of the idea of adding signals with the same name as
> the fields?
Haven't you already done this with power_fields/power_fieldsn?
--
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] PPC on Talos and Playstation 3
From: Lauri Kasanen @ 2020-03-30 6:56 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAF1D9AC-F167-4B48-AE93-BADA36932AE8@gatech.edu>
On Sun, 29 Mar 2020 20:17:49 +0000
"Immanuel, Yehowshua U" <yimmanuel3@gatech.edu> wrote:
> So I was wondering how to run unit tests for the PPC FPU. We can obviously do this on the Talos server, but also playstation 3.
>
> I have some old PPC Macs, but they are 32 bit not 64 bit.
>
> Sony’s playstation 3 however is ppc64. Also, Sony officially supported Linux on PS3 FAT models only which you can pick up on eBay for $50 - $70.
>
> So I think this is a good route to explore if anyone needs immediate/direct access to PPC64 for unit testing. I’m considering ordering one myself.
Remember that Sony blocked OtherOS in a specific firmware version, and
newer firmwares were required for running newer games. So finding a PS3
that can be used will be hard.
However, WiiUs are a viable option for recent-ish power hw for cheap.
- Lauri
_______________________________________________
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] PPC on Talos and Playstation 3
From: Jacob Lifshay @ 2020-03-30 7:12 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200330095605.53c15f0713bab37f5c7121e2@gmx.com>
On Sun, Mar 29, 2020, 23:55 Lauri Kasanen <cand@gmx.com> wrote:
> On Sun, 29 Mar 2020 20:17:49 +0000
> "Immanuel, Yehowshua U" <yimmanuel3@gatech.edu> wrote:
>
> > So I was wondering how to run unit tests for the PPC FPU. We can
> obviously do this on the Talos server, but also playstation 3.
> >
> > I have some old PPC Macs, but they are 32 bit not 64 bit.
> >
> > Sony’s playstation 3 however is ppc64. Also, Sony officially supported
> Linux on PS3 FAT models only which you can pick up on eBay for $50 - $70.
> >
> > So I think this is a good route to explore if anyone needs
> immediate/direct access to PPC64 for unit testing. I’m considering ordering
> one myself.
>
> Remember that Sony blocked OtherOS in a specific firmware version, and
> newer firmwares were required for running newer games. So finding a PS3
> that can be used will be hard.
>
> However, WiiUs are a viable option for recent-ish power hw for cheap.
>
The Wii U is a tri-core 32-bit PPC with 2GB of ddr3. Additionally, Nintendo
is not likely to support installing custom software.
I personally think Power Macs are probably the best option since they can
use standard PC hardware (eg. ram, sata disk, pci cards (maybe pcie?),
external display, usb, ethernet), they actually are designed to be able to
install your own OS, they have 1, 2, or 4 core 64-bit Power processors, and
they are relatively inexpensive -- I saw one for $100 last I checked.
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] PPC on Talos and Playstation 3
From: Lauri Kasanen @ 2020-03-30 7:32 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAC2bXD4DoabbWWc4vZCdrjEwOR7TG8DhrFMnU-0=uktSR23Q0A@mail.gmail.com>
On Mon, 30 Mar 2020 00:12:40 -0700
Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Sun, Mar 29, 2020, 23:55 Lauri Kasanen <cand@gmx.com> wrote:
> > Remember that Sony blocked OtherOS in a specific firmware version, and
> > newer firmwares were required for running newer games. So finding a PS3
> > that can be used will be hard.
> >
> > However, WiiUs are a viable option for recent-ish power hw for cheap.
>
> The Wii U is a tri-core 32-bit PPC with 2GB of ddr3. Additionally, Nintendo
> is not likely to support installing custom software.
>
> I personally think Power Macs are probably the best option since they can
> use standard PC hardware (eg. ram, sata disk, pci cards (maybe pcie?),
> external display, usb, ethernet), they actually are designed to be able to
> install your own OS, they have 1, 2, or 4 core 64-bit Power processors, and
> they are relatively inexpensive -- I saw one for $100 last I checked.
The specs quote 64-bit FPU, so it's not entirely 32-bit. Nintendo
doesn't need to, they have abandoned the console, and in its last state
it was still hackable, unlike the PS3. Therefore it's safe to buy any
(NTSC, I haven't checked PAL) WiiU if you intend to hack it, vs very
careful checking to find that rare low-firmware PS3.
PowerMacs are fine, though old and power-hogging.
- Lauri
_______________________________________________
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] PPC on Talos and Playstation 3
From: Jacob Lifshay @ 2020-03-30 7:52 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200330103226.4cc14532f22a48719e25ea8f@gmx.com>
On Mon, Mar 30, 2020, 00:31 Lauri Kasanen <cand@gmx.com> wrote:
> On Mon, 30 Mar 2020 00:12:40 -0700
> Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > On Sun, Mar 29, 2020, 23:55 Lauri Kasanen <cand@gmx.com> wrote:
> > > Remember that Sony blocked OtherOS in a specific firmware version, and
> > > newer firmwares were required for running newer games. So finding a PS3
> > > that can be used will be hard.
> > >
> > > However, WiiUs are a viable option for recent-ish power hw for cheap.
> >
> > The Wii U is a tri-core 32-bit PPC with 2GB of ddr3. Additionally,
> Nintendo
> > is not likely to support installing custom software.
> >
> > I personally think Power Macs are probably the best option since they can
> > use standard PC hardware (eg. ram, sata disk, pci cards (maybe pcie?),
> > external display, usb, ethernet), they actually are designed to be able
> to
> > install your own OS, they have 1, 2, or 4 core 64-bit Power processors,
> and
> > they are relatively inexpensive -- I saw one for $100 last I checked.
>
> The specs quote 64-bit FPU, so it's not entirely 32-bit.
Normally, the size of a pointer or general-purpose integer register is used
to determine 32 or 64-bit rather than the size of the FP unit since nearly
every processor more powerful than a microcontroller supports 64-bit FP.
even the 8086 (16-bit) supports 64-bit floating point (or even 80-bit) with
the 8087 math coprocessor. Also, recent intel processors support 512-bit FP
registers (the avx512 instruction set), but it's only a 64-bit processor.
Nintendo
> doesn't need to, they have abandoned the console, and in its last state
> it was still hackable, unlike the PS3. Therefore it's safe to buy any
> (NTSC, I haven't checked PAL) WiiU if you intend to hack it, vs very
> careful checking to find that rare low-firmware PS3.
>
From some searching I found a linux port for the WiiU, however, it only
supports booting 1 core.
https://gitlab.com/linux-wiiu/linux-wiiu#device-support
The main benefit of Power Macs is the software's highly likely to work,
whereas both the WiiU and PS3 are less likely to.
> PowerMacs are fine, though old and power-hogging.
>
yup. :)
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] PPC on Talos and Playstation 3
From: Lauri Kasanen @ 2020-03-30 8:05 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAC2bXD68ze_ZNsHm_gECzFzQXT-E8td=ART0gD1Rp28Vb-EiqQ@mail.gmail.com>
On Mon, 30 Mar 2020 00:52:31 -0700
Jacob Lifshay <programmerjake@gmail.com> wrote:
> Normally, the size of a pointer or general-purpose integer register is used
> to determine 32 or 64-bit rather than the size of the FP unit since nearly
> every processor more powerful than a microcontroller supports 64-bit FP.
> even the 8086 (16-bit) supports 64-bit floating point (or even 80-bit) with
> the 8087 math coprocessor. Also, recent intel processors support 512-bit FP
> registers (the avx512 instruction set), but it's only a 64-bit processor.
Aiye, but the context was running 64-bit fpu code, and with an embedded
cpu it's possible it would not have such.
- Lauri
_______________________________________________
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] Building Docker Containers
From: Luke Kenneth Casson Leighton @ 2020-03-30 8:59 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <53ED80C8-0F97-4B04-9892-3F0524038D80@getmailspring.com>
On Sunday, March 29, 2020, Cole Poirier <colepoirier@gmail.com> wrote:
>
> libre-soc access are not my own. Before I step into the git repo fully,
> I'd like to take this figurative milestone as an opprotunity to
> reinstall my setup, and send you my new public key sometime today or
> tomorrow. Is that alright luke?
yes... except bear in mind that you in no way need to do a "Windows".
1. git --global user.name blah
2. git --global user.email blah
3. sudo bash
4. mv /home/blah /home/blahblah
5. edit /etc/passwd /etc/shadow and /etc/group
that's it.
*especially* don't throw away ssh keys please, because it will be a
sysadmin burden for me to go replacing them all with new ones, on two
separate machines.
> I'm aiming for the same goal, hopefully my first draft will be ready
> around tuesday.
great.
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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-30 9:06 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=271
--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #4)
> (In reply to Luke Kenneth Casson Leighton from comment #3)
> > what do you think of the idea of adding signals with the same name as
> > the fields?
>
>
> Haven't you already done this with power_fields/power_fieldsn?
if you recall i mentioned this a month ago particularly when we did those
recursive expressions. the distinction between nmigen expressions and nmigen
signals is very important.
they are expressions rather than signals
which, if you recall, results in duplication of those expressions wherever they
are used (hence the massivr graphs ladt month despite the code only being a few
lines long)
if the expressions are used a hundred times then they are copied into the HDL a
hindred times because they are a nmigen AST tree fragment.
as signals, the *signal* would be copied and would show up in the yosys graphs.
--
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] microwatt tlb
From: Luke Kenneth Casson Leighton @ 2020-03-30 9:35 UTC (permalink / raw)
To: Paul Mackerras; +Cc: openpower-hdl-cores, Libre-RISCV General Development
In-Reply-To: <20200330033002.GB15134@blackberry>
On Monday, March 30, 2020, Paul Mackerras <paulus@ozlabs.org> wrote:
>
> Thanks for the comments and the pointers. We do already have stall
> signals in microwatt, but the way it works is pretty simple so far.
*great* :)
> The pipelined, in-order execution structure basically comes from
> Anton's initial work, so I don't think we'll be throwing that out.
> We will continue to make readability and understandability a focus,
> and I for one will try to add more code comments as I work on it to
> make it easier to follow.
it's pretty damn good already, paul. one suggestion, put spec version book
section and pagenum into the comments?
btw the parsing of 3.0B PDF integer, LDST and Logical ops went "ok",
codegenerator first syntax recognising simple lines (RT) <- X[56]*4
we will need at least 3 generators (64 bit c code for pearpc, python
simulator, and nmigen) so will make it modular, therefore creating VHDL and
Chisel generators that autocreate code fragments should be a two day job
each and would result in autogenerated HDL for 80% of the 3.0B spec (!)
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] [OpenPOWER-HDL-Cores] microwatt tlb
From: Paul Mackerras @ 2020-03-30 3:30 UTC (permalink / raw)
To: Luke Kenneth Casson Leighton
Cc: openpower-hdl-cores, Libre-RISCV General Development
In-Reply-To: <CAPweEDzGri9hXAk5JPhQnLhqNoKD_M3v1yhasNDEtO8=xpz7Cw@mail.gmail.com>
On Fri, Mar 27, 2020 at 02:15:03AM +0000, Luke Kenneth Casson Leighton wrote:
> hi this is for paul mackerras when you see it.
>
> great to know you're working on microwatt. been such a long time, and
> really good to encounter you over the virtual coffee chat earlier today.
>
> here's the link to the radix walk doc i was talking about:
> https://github.com/power-gem5/gem5/blob/gem5-experimental/src/arch/power/radix_walk_example.txt
>
> it is really good. implementations also exist in the same codebase, the
> easiest way to track them down is via the commit logs in the
> gem5-experimental branch.
>
> for libresoc we really really need clear HDL to "track" if you know what i
> mean, because some of these algorithms are very timeconsuming to implement
> from scratch.
>
> paul, continuing the (brief) discussion somewhat, in a related way, i
> really wanted to make you aware of the implications for microwatt of trying
> to make it multistage pipelined.
>
> if you look up jon dawson's IEE754 FPU code you find that it is entirely
> FSM based. as such it is superb for fitting in small FPGAs.
>
> over a 6 month period i morphed it from its humble beginnings into an
> absolute beast of a flexibly reprogrammable Object Orientated IEEE754 FP
> toolkit, capable of 16, 32 or 64 bit (and anything else you care to add),
> arbitrary pipeline depth *or* FSM style engines, SIMD capability, *dynamic*
> pipelines, the works. Jacob helped add a fantastic hybrid fpdiv, sqrt
> *and* rsqrt engine all in the same pipeline. it's now well north of 10,000
> lines of python code and takes a week to run all the unit tests.
>
> what i learned along the way was that the FSM based systems vs pipeline
> systems trade low gate count and simplicity and code readability for speed,
> much higher gate count, and, unless *and even* if OO design is used, turn
> into the most awful unreadable unmaintainable total trash.
>
> rocketchip unfortunately, for all the compactness and other advantages, is
> particularly bad, *because* of the OO (and total lack of code comments).
> the OO hierarchy makes it flat-out impossible for anyone but its original
> creators to work with. (something to alert the chiselwatt team on, there,
> although from what i have seen, the code comments in chiselwatt are damn
> good).
>
> and yet if you even remotely try anything like modern OO programming design
> strategies and tecuniques with these 1980s era languages (HDL, Verilog) you
> immediately also run into serious difficulties of a different kind, which i
> won't go into, right now.
>
> the bottom line is: adding extra pipeline stages to microwatt not only
> complicates it and makes it unreadable and unmaintainable, it increases the
> number of LUTs required to the pont where you will need to call it "watt"
> or "megawatt"
>
> :)
>
> regarding exceptions and traps: for in-order pipelined systems these are a
> damn nuisance.
>
> every solution to every problem in an inorder system is:
>
> stall.
>
> that's it.
>
> after learning about the CDC6600, which is a deeply impressive design that
> takes literally months to begin to comprehend, i dislike inorder systems
> intensely.
>
> the key thing that i learned from Mitch Alsup about how to handle
> exceptions is: you *must* prevent the ALU (or whatever) from "committing"
> its result until it is GUARANTEED known that the exception will not occur.
>
> that is the absolute core concept of exceptions (aka interrupts), you MUST
> achieve, in some fundamental way.
>
> this is done in an OoO design by marking and tracking the operation - all
> the way down the pipeline - with "cancellation masks" (a global ID which
> travels *with* the partial result data, down a given pipeline)
>
> this is known as "shadowing", and it is not only the operation that *might*
> be cancelled that has to be "shadowmarked", it is *all following
> instructions as well* (hence the term "shadow").
>
> shadowed operations are real easy to cancel: pull the "cancel" wire up, ane
> everything with the requisite mask ID gets a global signal "whoops we no
> longer need to pass this down the pipeline, drop it on the floor".
>
> with all "future" partial (and completed but noncommitted) results now
> killed, the PC can safely be redirected at the exception, interrupt, or the
> alternative branch, or whatever: these all use *exactly* the same shadowing
> technique.
>
> you start to see why the majority of inorder systems use "stall stall stall
> stall stall" as the be-all and end-all "onnne and only true solution",
> here? [ hallelujah, praise the stall... ] :)
>
> basically if i have discouraged you from pursuing the path of adding
> multiple pipeline stages to microwatt, then i have succeeded in what i set
> out to explain. because microwatt's value is not just its small code size,
> its readability and compactness makes it an ideal reference implementation
> *and*, furthermore, its complete lack of optimisation normally seen in
> "simple" pipelined designs actually saves on gates / FPGA resources.
>
> the moment you add extra stages, all that goes out the window.
>
> an associate and contributor on our list, Samuel Falvo, taught me some
> awesome tricks.
>
> his CPUs are incredible, designed in the most amazing elegant and unusual
> ways. he wrote his own PLA style "language" (written in lisp) which takes
> specifications (in lisp lists) for functionality and *generates* VHDL
> combinatorial blocks.
>
> he used this tool to create a 6502-like processor with virtually no
> manually written glue logic (even the decoder was written in this simple
> specification), that easily fits into an ultra low cost ICE40 yet has
> massive amounts of room to spare for peripherals.
>
> the key to the success of this approach was the heavy tradeoff of *not*
> using pipeline stages, but effectively doing a FSM style entire execution
> design. actually it wasn't even a FSM, i think he used the term "PLA". i
> am garbling it, it was a year ago, there are some keywords i have missed
> out, you get the idea though.
>
> what i am really saying is: please do seriously consider simply stalling on
> anything that could have an exception thrown. arrange for the entire
> pipeline to simply grind to a halt, *globally* freezing right the way back
> to the decode phase, only proceeding when it is guaranteed known, 100%,
> that the exception will NOT occur.
>
> this is, believe it or not, an industry-wide "acceptable" technique in ALL
> in-order designs.
>
> look up "minerva rv32" on github (it is very readable code) and grep its
> source for the word "stall".
>
> you will find a *combinatorial* global signal propagates throughout *every*
> pipeline stage, implementing this "stop the world i want to get off!"
> industry-wide "solution".
>
> literally every effort that i have seen that attempts *not* to follow that
> "solution" for inorder designs involves the word "but" and it goes downhill
> from there.
>
> surprising, ehn? :)
Thanks for the comments and the pointers. We do already have stall
signals in microwatt, but the way it works is pretty simple so far.
The pipelined, in-order execution structure basically comes from
Anton's initial work, so I don't think we'll be throwing that out.
We will continue to make readability and understandability a focus,
and I for one will try to add more code comments as I work on it to
make it easier to follow.
Thanks,
Paul.
_______________________________________________
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] Testing the simulator with qemu-5.0.0-rc0 and GDB
From: Tobias Platen @ 2020-03-30 9:44 UTC (permalink / raw)
To: libre-riscv-dev
I've upgraded my installed version of QEMU to the latest version because my old version (included in Debian Buster) does not support "-machine powernv9".
When running launch.sh I get these warnings:
qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-cfpc=workaround
qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-sbbc=workaround
qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-ibs=workaround
qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-ccf-assist=on
When I run "powerpc64-linux-gnu-gdb -x gdbscript", I get the following error message:
GNU gdb (GDB) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=powerpc64le-unknown-linux-gnu --target=powerpc64-buildroot-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
warning: No executable has been specified and target does not support
determining executable automatically. Try using the "file" command.
0x000000003001b288 in ?? ()
gdbscript:2: Error in sourced command file:
Undefined command: "layout". Try "help".
--
Tobias Platen <libre-soc[at]platen-software[dot]de>
_______________________________________________
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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-30 13:01 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=271
--- Comment #6 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #5)
> they are expressions rather than signals
> which, if you recall, results in duplication of those expressions wherever
> they are used (hence the massivr graphs ladt month despite the code only
> being a few lines long)
>
Ah, I see 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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-30 14:11 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=271
--- Comment #7 from Michael Nolan <mtnolan2640@gmail.com> ---
Ok, I've got it sort of working in df295b5. I removed TopPowerDecoder's
inheritance of DecodeFields and moved DecodeFields to a member. I then had
TopPowerDecoder go through each of the "common" fields in DecodeFields and copy
it to a signal. This works, but it doesn't take care of the form specific
fields (e.g. dec.FormXL.XO[9]), and I'm not sure what to do with those. I
suppose I could add in submodules for each of the forms and copy their signals
like I did with the common ones, would that work for you?
--
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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-30 15:09 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=271
--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #7)
> Ok, I've got it sort of working in df295b5. I removed TopPowerDecoder's
> inheritance of DecodeFields and moved DecodeFields to a member. I then had
> TopPowerDecoder go through each of the "common" fields in DecodeFields and
> copy it to a signal.
great.
> This works, but it doesn't take care of the form
> specific fields (e.g. dec.FormXL.XO[9]), and I'm not sure what to do with
> those. I suppose I could add in submodules for each of the forms and copy
> their signals like I did with the common ones, would that work for you?
submodules is unnecessary (and a bit overkill): an object that is a dummy class
would do (similar to the use of NamedTuple)
class Form:
pass
or, actually, just a NamedTuple again. hmm take a look see what you
think
commit 5374cb82b
_should_ be accessible as
comb += something.eq(decoder.FormX.RA)
which becomes important in the autogenerator code because each instruction
is listed as having a "Form", and we can drop the decoder.Form{something}
into its context, and the pseudo-code fragment will go "oh, i recognise
these variables RA, RT etc. as being from Form{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 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-03-30 15:16 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=269
--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
the basics of the parser now work.
this:
n <- 0
do while n < 64
if (RS)[63-n] = 0b1 then
leave
n <- n + 1
RA <- EXTZ64(n)
gets turned into this:
n = 0
while n < 64:
if RS[63 - n] == 1:
break
n = n + 1
RA = EXTZ64(n)
which is executable python code.
one little piece of syntax not currently supported is the regfile read.
(RS) means "look up in the GPR using the bits from the field named RS of
the opcode", not "change the bits in the opcode"
unfortunately, assignment to RT means "change the regfile".
it's a little more non-obvious than at first glance.
--
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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-30 16:56 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=271
--- Comment #9 from Michael Nolan <mtnolan2640@gmail.com> ---
Interesting, it looks like we're going to need to remove the [0:-1] from
anything that uses the fields 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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-30 17:05 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=271
--- Comment #10 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Michael Nolan from comment #9)
> Interesting, it looks like we're going to need to remove the [0:-1] from
> anything that uses the fields now.
Oh right, that removes the last value from the signal normally. Anyways, all
the tests pass 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 272] New: functions needed in POWER simulator which match 3.0B spec
From: bugzilla-daemon @ 2020-03-30 17:27 UTC (permalink / raw)
To: libre-riscv-dev
http://bugs.libre-riscv.org/show_bug.cgi?id=272
Bug ID: 272
Summary: functions needed in POWER simulator which match 3.0B
spec
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: PC
OS: Linux
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Source Code
Assignee: lkcl@lkcl.net
Reporter: lkcl@lkcl.net
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
we need some functions, named EXTS, EXTZ64 and so on, which
are in the spec, and need to be implemented. this is so that
the auto-generated code, which is taken directly *from* the spec
(pseudo-code fragments, converted to actual python code),
can call them.
michael can you take a look?
--
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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-30 18:03 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=271
--- Comment #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #9)
> Interesting, it looks like we're going to need to remove the [0:-1] from
> anything that uses the fields now.
it was a bad hack, i couldn't work out how to just refer to the field
without going through __getattr__.
now that everything goes *through* the equivalent of that, and is now
sub-signals (slices of the original opcode), yes that hack should not
be necessary... *as long* as we refer to those fields.
--
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