* Re: [libre-riscv-dev] ppc-dev linux patch support for microwatt!
From: Luke Kenneth Casson Leighton @ 2020-05-11 22:34 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <D96DDBD2-461A-4CB9-B536-CC7434B97CA3@gatech.edu>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Mon, May 11, 2020 at 11:27 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
>
>
> > On May 11, 2020, at 6:23 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> >
> > https://github.com/paulusmack/microwatt/blob/mmu/mmu.vhdl <https://github.com/paulusmack/microwatt/blob/mmu/mmu.vhdl>
> Oh - its a fork. Haha
yes, paul mackerras is working on the RADIX MMU implementation, and
has got a linux kernel booting. that's really significant. i can do
a brain-dead conversion of his mmu.vhdl and associated data structures
in a couple of hours: i'm not so good at writing unit tests etc. that
takes longer: if we work together we should have a linux-capable MMU
in a few days.
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] ppc-dev linux patch support for microwatt!
From: Luke Kenneth Casson Leighton @ 2020-05-11 22:53 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDx7Ou_0panOQEW+58RgdqSq7_dKhXQvV3D-aGCghEgm9w@mail.gmail.com>
dcache:
https://github.com/paulusmack/microwatt/blob/mmu/dcache.vhdl
icache:
https://github.com/paulusmack/microwatt/blob/mmu/icache.vhdl
_______________________________________________
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-dev linux patch support for microwatt!
From: Yehowshua @ 2020-05-11 23:02 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDz-35t6vK=-NX2QtQqZ3bJjP3f=5bmdick_45X2K0bF4A@mail.gmail.com>
> dcache:
> https://github.com/paulusmack/microwatt/blob/mmu/dcache.vhdl <https://github.com/paulusmack/microwatt/blob/mmu/dcache.vhdl>
>
> icache:
> https://github.com/paulusmack/microwatt/blob/mmu/icache.vhdl <https://github.com/paulusmack/microwatt/blob/mmu/icache.vhdl>
I was actually talking to Michael about that the other day.
If you have an instruction that does a store to a location in the icache, I guess you need some coherency to make that work.
Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] ppc-dev linux patch support for microwatt!
From: Luke Kenneth Casson Leighton @ 2020-05-12 0:53 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <3079D5F2-F773-47BE-AD3E-DEE1377FED17@gatech.edu>
On Tuesday, May 12, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:
> > dcache:
> > https://github.com/paulusmack/microwatt/blob/mmu/dcache.vhdl <
> https://github.com/paulusmack/microwatt/blob/mmu/dcache.vhdl>
> >
> > icache:
> > https://github.com/paulusmack/microwatt/blob/mmu/icache.vhdl <
> https://github.com/paulusmack/microwatt/blob/mmu/icache.vhdl>
>
>
> I was actually talking to Michael about that the other day.
>
> If you have an instruction that does a store to a location in the icache,
that is prohibited by design.
I guess you need some coherency to make that work.
single core and separate read only instruction area from readwrite data
area, no you don't.
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] ppc-dev linux patch support for microwatt!
From: Yehowshua @ 2020-05-12 0:56 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxHxc4ZWuQtEnY1EQqdRHuXAqgVXpLxqWRewXJdrPpcwA@mail.gmail.com>
> On May 11, 2020, at 8:53 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> that is prohibited by design.
Are you saying that the POWER ISA itself dis-allows writes to instruction memory?
Does such a behavior get trapped or something?
I know that Linux on RISCV for example will set page r/w/ex bits that are part of the RISCV ISA. Then, an attempt to store into instruction memory becomes prohibited.
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] ppc-dev linux patch support for microwatt!
From: Luke Kenneth Casson Leighton @ 2020-05-12 1:25 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <FEBBCA29-9C37-45EF-818F-E8705F2EEEC6@gatech.edu>
On Tuesday, May 12, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:
>
>
> > On May 11, 2020, at 8:53 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
> >
> > that is prohibited by design.
>
> Are you saying that the POWER ISA itself dis-allows writes to instruction
> memory?
we'll have to check the spec closely, or ask on one if the lists, or just
trust paul's expertise. he's been working with powerpc since 1996.
Does such a behavior get trapped or something?
hard exception, yes.
> I know that Linux on RISCV for example will set page r/w/ex bits that are
> part of the RISCV ISA. Then, an attempt to store into instruction memory
> becomes prohibited.
exactly.
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] Power memory fences and icache handling
From: Jacob Lifshay @ 2020-05-12 1:42 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxHxc4ZWuQtEnY1EQqdRHuXAqgVXpLxqWRewXJdrPpcwA@mail.gmail.com>
On Mon, May 11, 2020, 17:54 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Tuesday, May 12, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> > > dcache:
> > > https://github.com/paulusmack/microwatt/blob/mmu/dcache.vhdl <
> > https://github.com/paulusmack/microwatt/blob/mmu/dcache.vhdl>
> > >
> > > icache:
> > > https://github.com/paulusmack/microwatt/blob/mmu/icache.vhdl <
> > https://github.com/paulusmack/microwatt/blob/mmu/icache.vhdl>
> >
> >
> > I was actually talking to Michael about that the other day.
> >
> > If you have an instruction that does a store to a location in the icache,
>
>
> that is prohibited by design.
>
If you're trying to run a standard Linux OS, writing to memory that could
be in the icache is required, that's how the dynamic linker works.
Additionally, loading code from disk (e.g. the exec() call) or JIT
compilation also requires writing to memory then executing it. In all of
those cases one or more icache invalidate and then an isync instruction (or
other context synchronizing instruction) are run before running the
modified code.
Note: it turns out that isync doesn't do any icache flushing without
additional icache invalidate instructions, so it's not quite as expensive
as I had originally thought for Power atomics, however, it still restarts
fetching and decoding instructions, so is still more expensive than
necessary for just using it as an atomic fence.
It's standard practice for JITs to map a section of memory with all of R/W
and execute permissions simultaneously, then, once a section of code is
written/modified, it will run the required icache invalidate and isync
instructions (RISC-V just uses a single fence.i instruction that must be
run on all harts using a syscall) before trying to execute the changed code.
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] Power memory fences and icache handling
From: Luke Kenneth Casson Leighton @ 2020-05-12 3:29 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6gWCr9GK7m==YP+riR_8J=aEMGXocMKk7nCzXPSFQifQ@mail.gmail.com>
On Tuesday, May 12, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Mon, May 11, 2020, 17:54 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
> > On Tuesday, May 12, 2020, Yehowshua <yimmanuel3@gatech.edu> wrote:
> >
> > > > dcache:
> > > > https://github.com/paulusmack/microwatt/blob/mmu/dcache.vhdl <
> > > https://github.com/paulusmack/microwatt/blob/mmu/dcache.vhdl>
> > > >
> > > > icache:
> > > > https://github.com/paulusmack/microwatt/blob/mmu/icache.vhdl <
> > > https://github.com/paulusmack/microwatt/blob/mmu/icache.vhdl>
> > >
> > >
> > > I was actually talking to Michael about that the other day.
> > >
> > > If you have an instruction that does a store to a location in the
> icache,
> >
> >
> > that is prohibited by design.
> >
>
> If you're trying to run a standard Linux OS, writing to memory that could
> be in the icache is required, that's how the dynamic linker works.
my understabding of this is that writing to memory as a data page, then
flushing it and reloading it into the icache, is a workaround.
> Additionally, loading code from disk (e.g. the exec() call) or JIT
> compilation also requires writing to memory then executing it. In all of
> those cases one or more icache invalidate and then an isync instruction (or
> other context synchronizing instruction) are run before running the
> modified code.
that would... ok if the icache is entirely invalidated following a write
through the dcache, it would load the modified executable
>
> Note: it turns out that isync doesn't do any icache flushing without
> additional icache invalidate instructions, so it's not quite as expensive
> as I had originally thought for Power atomics, however, it still restarts
> fetching and decoding instructions, so is still more expensive than
> necessary for just using it as an atomic fence.
hmmm
--
---
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] learning from a failed business
From: Jacob Lifshay @ 2020-05-12 4:15 UTC (permalink / raw)
To: Libre-RISCV General Development
Found this quite interesting video about how one of Louis Rossmann's
businesses failed due to mistakes he made and what he learned from it:
https://youtu.be/w3c2dOw6Frg
Louis Rossmann runs a Apple computer repair shop in New York and a YouTube
channel where he shows repairs, talks about his business, and fights for
right-to-repair.
We could probably use some of his ideas, such as having a clear mission
statement, choosing correctly who you are selling to, choosing correctly
when to decline investment and what terms & stuff you would need to accept
investment.
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] PowerISA 3.1 (Power10) spec released
From: Lauri Kasanen @ 2020-05-12 6:01 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <20200511203421.5d834abb14dbc2b7c979c6f7@gmx.com>
Hi,
The thing that stood out to me in the levels was BE/LE. An int or float
compatible Power processor must support BE, LE is optional at those
levels. A Linux level processor must support LE, BE is optional at that
level. However the Linux level requires SIMD.
So this means that our int+float processor must support BE.
- 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] PowerISA 3.1 (Power10) spec released
From: Jacob Lifshay @ 2020-05-12 6:27 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200512090144.8fe5608fc7b63c8b6b33367a@gmx.com>
On Mon, May 11, 2020, 23:01 Lauri Kasanen <cand@gmx.com> wrote:
> Hi,
>
> The thing that stood out to me in the levels was BE/LE. An int or float
> compatible Power processor must support BE, LE is optional at those
> levels. A Linux level processor must support LE, BE is optional at that
> level. However the Linux level requires SIMD.
>
> So this means that our int+float processor must support BE.
not necessarily, it defines 4 compatibility levels, notice that all
features included in higher levels are not forbidden in lower levels, so we
could claim to be 100% compatible with the lowest level and we could still
implement nearly everything from higher levels, we just couldn't claim to
implement the named int+fp level. We could still claim to implement fp
instructions (assuming we actually do) and to be totally compatible with
LE-only int+fp (which we should probably ask OpenPower to add as a
supported level).
Note that the levels aren't strictly subsets of each other, so they're more
like named feature sets rather than levels.
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] PowerISA 3.1 (Power10) spec released
From: Lauri Kasanen @ 2020-05-12 6:44 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAC2bXD68V1G5Rd5U0xBYHduNHJsZECMU_EiGbQpjnWQT9Y1ncQ@mail.gmail.com>
On Mon, 11 May 2020 23:27:38 -0700
Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Mon, May 11, 2020, 23:01 Lauri Kasanen <cand@gmx.com> wrote:
>
> > Hi,
> >
> > The thing that stood out to me in the levels was BE/LE. An int or float
> > compatible Power processor must support BE, LE is optional at those
> > levels. A Linux level processor must support LE, BE is optional at that
> > level. However the Linux level requires SIMD.
> >
> > So this means that our int+float processor must support BE.
>
> not necessarily, it defines 4 compatibility levels, notice that all
> features included in higher levels are not forbidden in lower levels, so we
> could claim to be 100% compatible with the lowest level
No, we couldn't. The lowest level, int only, has the same BE
requirement.
- 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] PowerISA 3.1 (Power10) spec released
From: Jacob Lifshay @ 2020-05-12 7:06 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200512094413.fba058b3ca1d04be1bae3aa8@gmx.com>
On Mon, May 11, 2020, 23:43 Lauri Kasanen <cand@gmx.com> wrote:
> On Mon, 11 May 2020 23:27:38 -0700
> Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > On Mon, May 11, 2020, 23:01 Lauri Kasanen <cand@gmx.com> wrote:
> >
> > > Hi,
> > >
> > > The thing that stood out to me in the levels was BE/LE. An int or float
> > > compatible Power processor must support BE, LE is optional at those
> > > levels. A Linux level processor must support LE, BE is optional at that
> > > level. However the Linux level requires SIMD.
> > >
> > > So this means that our int+float processor must support BE.
> >
> > not necessarily, it defines 4 compatibility levels, notice that all
> > features included in higher levels are not forbidden in lower levels, so
> we
> > could claim to be 100% compatible with the lowest level
>
> No, we couldn't. The lowest level, int only, has the same BE
> requirement.
>
Ok, sounds like we definitely need to talk to OpenPower about this.
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] little-endian only power cores and spec compliance
From: Jacob Lifshay @ 2020-05-12 7:24 UTC (permalink / raw)
To: openpower-hdl-cores; +Cc: Libre-RISCV General Development
Over on Libre-SOC's mailing list (CCed), we've been having a conversation
about the newly-released spec v3.1 and the compliance levels:
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-May/006502.html
we are building a cpu that is intended to be Linux capable, however doesn't
support Power's SIMD instructions and is LE only. We've been running into
an issue with the spec's compliance levels:
the linux compliance level requires SIMD and BE is optional but the lower
compliance levels require BE but SIMD is optional.
Would it be possible to get a LE version of the int and int+float
compliance levels added to the spec?
Other ideas also welcome
Jacob Lifshay
_______________________________________________
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] little-endian only power cores and spec compliance
From: Luke Kenneth Casson Leighton @ 2020-05-12 7:31 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6LVtrMh7RT=11ZVypujcJRaMokG7XuBwF87veBiMMDLQ@mail.gmail.com>
(removing opencores-hdl cc)
we need BE because without BE it is not possible to support VBLOCK,
Compressed or SVPrefix.
with BE, the opcode is presented in the first 2 bytes of any
instruction stream, regardless of whether it is 32-bit, VB, C or SVP,
and consequently the major opcodes that we plan to overload will
always be in the first 2 bytes and can reliably be used to detect the
mode.
without BE, this is flat-out impossible to do.
it would have been good to wait until we had agreed what to say on
that list because it is populated by extremely busy people whom we now
need to inform (implicitly or explicitly) that we've not discussed
properly and now their extremely precious time has to be taken up with
a correction.
can i suggest that we set some interaction guidelines for opencores-hdl?
l.
On Tue, May 12, 2020 at 8:24 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> Over on Libre-SOC's mailing list (CCed), we've been having a conversation
> about the newly-released spec v3.1 and the compliance levels:
> http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-May/006502.html
>
> we are building a cpu that is intended to be Linux capable, however doesn't
> support Power's SIMD instructions and is LE only. We've been running into
> an issue with the spec's compliance levels:
> the linux compliance level requires SIMD and BE is optional but the lower
> compliance levels require BE but SIMD is optional.
>
> Would it be possible to get a LE version of the int and int+float
> compliance levels added to the spec?
>
> Other ideas also welcome
>
> Jacob Lifshay
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
From: Luke Kenneth Casson Leighton @ 2020-05-12 7:36 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200512090144.8fe5608fc7b63c8b6b33367a@gmx.com>
On Tue, May 12, 2020 at 7:00 AM Lauri Kasanen <cand@gmx.com> wrote:
>
> Hi,
>
> The thing that stood out to me in the levels was BE/LE. An int or float
> compatible Power processor must support BE, LE is optional at those
> levels. A Linux level processor must support LE, BE is optional at that
> level. However the Linux level requires SIMD.
>
> So this means that our int+float processor must support BE.
michael and i have added BE byte-flipping into the instruction decode,
which is code used by both the simulator and the hardware.
we need BE because without it we cannot detect Compressed, VBLOCK or
SVPrefix modes in the same instruction stream as 32-bit operations,
because only in BE mode will the opcode be in the front 2 bytes in the
sequential bytes read from the instruction stream.
see https://libre-soc.org/openpower/
where it is mentioned that we will need to take 8 major opcodes to do
this: 2 bits per "mode".
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] little-endian only power cores and spec compliance
From: Jacob Lifshay @ 2020-05-12 7:40 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyUuFwL1yjyHESQEAVxQ3bLqN1VWcUS1enXTv6UN_3t8g@mail.gmail.com>
On Tue, May 12, 2020, 00:32 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
>
> without BE, this is flat-out impossible to do.
>
Oops, forgot about 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] little-endian only power cores and spec compliance
From: Jacob Lifshay @ 2020-05-12 7:46 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5SkgmjEi7TgqNMDc1gtkxzJFpNJn3ZfkFYsvAYgBzbcA@mail.gmail.com>
On Tue, May 12, 2020, 00:40 Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Tue, May 12, 2020, 00:32 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
>>
>> without BE, this is flat-out impossible to do.
>>
>
> Oops, forgot about that.
>
Never mind, now that I take more than 15s to think about it, we need BE for
the instruction stream but LE for data access (since that's effectively
industry standard), so it's still effectively a LE-only architecture since
everything but the instruction decoder is LE, but the instruction decoder
can be switched to BE mode.
Having our architecture require BE for all memory accesses just because we
want to support 16-bit instructions is a non-starter in my opinion
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] PowerISA 3.1 (Power10) spec released
From: Luke Kenneth Casson Leighton @ 2020-05-12 7:50 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200512090144.8fe5608fc7b63c8b6b33367a@gmx.com>
On Tue, May 12, 2020 at 7:00 AM Lauri Kasanen <cand@gmx.com> wrote:
> level. However the Linux level requires SIMD.
this is more serious. the implementation burden of POWER SIMD
compliance is absolutely massive. a quick count from figure 91 i
estimate 600 instructions dedicated to INT and FP SIMD.
the scalar instruction set is much more manageable: there's 378
opcodes from microwatt CSV files, then there's 20 FP LD/ST, and
estimated 70 or so FP arithmetic and 8 or so status registers.
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] PowerISA 3.1 (Power10) spec released
From: Luke Kenneth Casson Leighton @ 2020-05-12 7:56 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6KG8=aoJNoZvzZrBz=t+GZyct9JqQ0J=DjSgv7+TYNgQ@mail.gmail.com>
On Tue, May 12, 2020 at 8:07 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
> > No, we couldn't. The lowest level, int only, has the same BE
> > requirement.
> >
>
> Ok, sounds like we definitely need to talk to OpenPower about this.
we need to talk to them, however it would be good to review and agree
what we talk about, before contacting them, because the people on the
openpower-hdl-cores low-traffic list are extremely busy.
they're sufficiently busy that the core engineers (the ones in IBM,
responsible for the POWER architecture) have not yet responded -
publicly - to our ISAMUX/NS letter
(https://libre-riscv.org/isa_conflict_resolution/isamux_isans/), and
ISAMUX/NS is an extremely important part (absolutely mission-critical)
of what we need to do.
hugh has been working hard to encourage them to engage on the list: i
believe it'll be the first time that they've ever publicly interacted
with a libre/open community.
so we therefore need to treat them as a critical strategic resource
and plan our responses very carefully.
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] little-endian only power cores and spec compliance
From: Luke Kenneth Casson Leighton @ 2020-05-12 8:07 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4ko6A1P9omroZSMq0YjYzyShAr5D05csQw1aDh3-eNOw@mail.gmail.com>
On Tue, May 12, 2020 at 8:46 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Tue, May 12, 2020, 00:40 Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > On Tue, May 12, 2020, 00:32 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> > wrote:
> >
> >>
> >> without BE, this is flat-out impossible to do.
> >>
> >
> > Oops, forgot about that.
> >
>
> Never mind, now that I take more than 15s to think about it, we need BE for
> the instruction stream but LE for data access (since that's effectively
> industry standard),
(this is a myth: only in the West is it the industry standard - see below)
> so it's still effectively a LE-only architecture since
> everything but the instruction decoder is LE, but the instruction decoder
> can be switched to BE mode.
yes. it's.... odd.
> Having our architecture require BE for all memory accesses just because we
> want to support 16-bit instructions is a non-starter in my opinion
it's a different feature / capability. i believe it's possible to
select any combination: BE/LE for instructions, BE/LE for data.
i can kinda see where they would want full BE support because there
still exists OSes compiled up - and maintained - to run on it. not
supporting BE sends a clear (blunt) message to those users, "you don't
matter any more", and IBM really can't do that.
additionally, with pretty much the entirety of the Asia Industrial
complex (Japan in particular, India as well) still using BE hardware
and thus having a massive software codebase where BE is hard-coded
into control peripheral drivers, we would be cutting ourselves off
from that market by not having full BE compatibility.
the Shakti Group showed me VME Bus systems that they had to be
compatible with. these are 40+ year old systems *still in service*,
for which radical rewrites of the software are absolutely out of the
question.
so that's a definite "decision" that we need to take seriously, rather
than dismiss lightly.
the largest (by far) downloaders of the debian ppc (not ppc64le)
distribution is Japan.
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] learning from a failed business
From: Luke Kenneth Casson Leighton @ 2020-05-12 8:11 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7J5oVQuXrJ6WDrbD_PiHwt1ODPTa3K-RHgPwJbWEmXfg@mail.gmail.com>
On Tue, May 12, 2020 at 5:16 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
> We could probably use some of his ideas, such as having a clear mission
> statement, choosing correctly who you are selling to, choosing correctly
> when to decline investment and what terms & stuff you would need to accept
> investment.
interestingly i've engaged again with my long-standing friend sarah
for this kind of advice and insight. she talks often about clarity of
message.
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] PowerISA 3.1 (Power10) spec released
From: Lauri Kasanen @ 2020-05-12 8:23 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDw4siZsTwHd136CB8xZuiNeoA1X80fgdAv9NVj1N-nB=w@mail.gmail.com>
On Tue, 12 May 2020 08:50:09 +0100
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Tue, May 12, 2020 at 7:00 AM Lauri Kasanen <cand@gmx.com> wrote:
>
> > level. However the Linux level requires SIMD.
>
> this is more serious. the implementation burden of POWER SIMD
> compliance is absolutely massive. a quick count from figure 91 i
> estimate 600 instructions dedicated to INT and FP SIMD.
>
> the scalar instruction set is much more manageable: there's 378
> opcodes from microwatt CSV files, then there's 20 FP LD/ST, and
> estimated 70 or so FP arithmetic and 8 or so status registers.
It's just a name though, even the doc says you can run Linux on the
lower levels. It's fine for libresoc to be at the int+fp level, and
include optional features from above that are useful. I just wanted to
point out the BE/LE requirement as it surprised me at least.
BE for instructions is not full BE, as data changes too.
- 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] little-endian only power cores and spec compliance
From: Luke Kenneth Casson Leighton @ 2020-05-12 8:23 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDx2w25Wx0_quaJyNz87nXPVwDs3RyQh-aiOkk0LHcSMkg@mail.gmail.com>
so, jacob: under the libre-soc charter, there's a part that says
"mistakes and merit belong to those who make it". this means that
it's your responsibility to write to opencores-hdl-discuss to correct
the mistaken impression about BE/LE.
can i recommend:
* doing it very soon (so that they don't spend needless precious time)
* keeping it short, and
* also letting them know that we're still discussing and will get back
to them with a carefully-considered consensus response?
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] PowerISA 3.1 (Power10) spec released
From: Luke Kenneth Casson Leighton @ 2020-05-12 8:33 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200512112314.1e2bb6d08199e725106fe98a@gmx.com>
On Tue, May 12, 2020 at 9:22 AM Lauri Kasanen <cand@gmx.com> wrote:
> It's just a name though, even the doc says you can run Linux on the
> lower levels.
yes... you can.... however note the phrase "Linux Compliancy". this
means that they have plans for actual Compliance Test Suites. this in
turn will mean that
one option therefore is to have a software-driven emulator mode for
SIMD. this would be our responsibility to write and maintain.
> It's fine for libresoc to be at the int+fp level, and
> include optional features from above that are useful. I just wanted to
> point out the BE/LE requirement as it surprised me at least.
yeh - in the West it is just not known that the majority of S.E.Asia
industry runs on BE hardware that is often 40 years old (VME Bus).
> BE for instructions is not full BE, as data changes too.
i recall (and could be wrong about) seeing that there's different
bits, one covering instructions, one covering data. would need to
read them more closely. are you saying that the BE-for-instructions
bit will flip *data* order as well?
See Section 1.10 of Book I and its first two subsections. Also see
the description
of the ILE field of the LPCR in Section 2.2 of Book III and the
description of the
LE bit of the MSR in Section 4.2.1 of Book III.
p1122:
Interrupt Little-Endian (ILE)
The contents of the ILE bit are copied into
MSRLE by interrupts that set MSRHV to 0 (see
p1146:
63 Little-Endian Mode (LE)
0 The thread is in Big-Endian mode.
1 The thread is in Little-Endian mode.
if we are to flip the instruction stream to BE mode (to support the
SVP/C/VBLOCK capability) we definitely don't want data to flip as
well.
bottom line: if there *isn't* a separate bit for instructions-BE/LE
and data-BE/LE, we definitely need 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
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