* [libre-riscv-dev] nmigen weekly monday meeting starting NOW.
From: Luke Kenneth Casson Leighton @ 2020-07-27 18:04 UTC (permalink / raw)
To: Libre-RISCV General Development
hi folks,
those bi-weekly nmigen meetings changed to weekly, i didn't realise.
consequently, that's right now (UTC 1800). logs will be at
https://freenode.irclog.whitequark.org/nmigen/2020-07-27 if anyone
misses it.
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] daily kan-ban update 29jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-27 12:39 UTC (permalink / raw)
To: Libre-RISCV General Development
task list:
* https://bugs.libre-soc.org/showdependencytree.cgi?id=383&
maxdepth=1&hide_resolved=1
yesterday:
* sorted yet another LDST Comp Unit bug
* reorganised pipeline tests
* made a start on XICS interrupt controller
today:
* reviewed (and finished?) trap proof.
rest of day:
* other half of XICS then do some unit tests for it
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] system call (sc) LEV "reserved field"
From: Luke Kenneth Casson Leighton @ 2020-07-27 9:43 UTC (permalink / raw)
To: Libre-RISCV General Development
Cc: Benjamin Herrenschmidt, openpower-hdl-cores
In-Reply-To: <a1c69311-9b7d-a6db-68f9-d987eeea64f2@blemings.org>
On Mon, Jul 27, 2020 at 10:08 AM Hugh Blemings <hugh@blemings.org> wrote:
>
> Hiya,
>
> Apologies for the top post but I can offer a historical perspective on
> at least part of this I think.
appreciated.
> Before I do though a disclaimer - these are my opinions and
> recollections only, certainly not policy! :)
always important to know where things are coming from.
> While it may change over time, the focus for OpenPOWER in the embedded
> space with the Open ISA has been firmly in the mid to high end and
> therefore mostly 64 bit space.
you may be interested to know that Andes Technology (a company in
Taiwan that has traditionally done DSPs focussing on audio processing:
think e.g. "C-Media" USB Audio devices: massive volume) has become the
de-facto creator and maintainer of RV32 Linux.
this because whilst everyone else is abandoning 32-bit because
640k^H^H^H^H 4GB should be enough for everyone, turns out this isn't
true any more thanks mostly to web browser memory consumption, Andes
Technology recognises that, in the huge market their customers *need*
the space and power saving that comes with a 32 bit ISA.
and it's enormous.
the jump in power consumption suffered by ARM when they went from the
32-bit Cortex A7 (which has a 48-bit address space) to the 64-bit
Cortex A53 was a whopping 10 to *15* percent for the same level of
DMIPS and actual real-world performance.
this because the increase in instruction length that inherently goes
with a 64 bit ISA required vendors using the Cortex A53 to lay down an
extra 50% larger L1 I-Cache. with L1 caches being a major part of
power consumption, real-world performance/watt figures took a
nose-dive.
> So to borrow some of the terminology/examples below, a SoC for a
> Raspberry Pi style device based on OpenPOWER ? Sure, definitely an area
> of interest.
cool.
> Getting down into smaller devices - really resource constrained and/or
> native 32 bit only - "truly embedded" - that's an area well served by
> RISC-V and not, I think somewhere we're going to see focus for OpenPOWER
> at present.
the advantage that they had was not being constrained by what is,
slightly unfairly / inaccurately, termed "mistakes of the past". they
had a clean sheet, basically.
could OpenPOWER follow that? with careful planning, and given the
care that's already been taken (as Paul mentioned), quite probably
yes.
*should* the OpenPOWER Foundation Members get together and work on
that? mmm... there would have to be clear benefits and a chance of
market success and adoption that warranted the effort. and, i think,
here, given that as you say, RISC-V already serves this area well,
it's not clear that it would be worthwhile doing.
i.e. unless it's something that was invested in (multi-year) by
something Foundation-like and University-collaboration-like (with
associated large DARPA/other Grants to back it up, as happened with
RISC-V) you'd need a well-funded OPF stakeholder that was actively
interested in pursuing it, and given the resources involved they'd
more than likely evaluate RISC-V as the better cost-benefit option.
> Not to say it can't in the future, but I think there is a bias towards
> working in areas the ecosystem as it currently stands knows well -
> playing to current strengths. :)
yeh absolutely. incremental steps, with consensus.
> That said I may still do an OpenPOWER based NTP enabled 7-segment
> display bedside clock one day, but that will be born of stubbornness,
> not because I actually need a 64 bit CPU to do it ;)
:) with added realistic and annoying analog buzzer alarm (a la
Groundhog Day), to boot.
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] [OpenPOWER-HDL-Cores] system call (sc) LEV "reserved field"
From: Hugh Blemings @ 2020-07-27 9:07 UTC (permalink / raw)
To: Luke Kenneth Casson Leighton, Benjamin Herrenschmidt
Cc: openpower-hdl-cores, Libre-RISCV General Development
In-Reply-To: <CAPweEDz+=H1FQ24uFyveuC3-BoaQeYLPY7phUsc1Zm1WpazvBA@mail.gmail.com>
Hiya,
Apologies for the top post but I can offer a historical perspective on
at least part of this I think.
Before I do though a disclaimer - these are my opinions and
recollections only, certainly not policy! :)
While it may change over time, the focus for OpenPOWER in the embedded
space with the Open ISA has been firmly in the mid to high end and
therefore mostly 64 bit space.
So to borrow some of the terminology/examples below, a SoC for a
Raspberry Pi style device based on OpenPOWER ? Sure, definitely an area
of interest.
Getting down into smaller devices - really resource constrained and/or
native 32 bit only - "truly embedded" - that's an area well served by
RISC-V and not, I think somewhere we're going to see focus for OpenPOWER
at present.
Not to say it can't in the future, but I think there is a bias towards
working in areas the ecosystem as it currently stands knows well -
playing to current strengths. :)
That said I may still do an OpenPOWER based NTP enabled 7-segment
display bedside clock one day, but that will be born of stubbornness,
not because I actually need a 64 bit CPU to do it ;)
Cheers,
Hugh
On 27/7/20 6:00 pm, Luke Kenneth Casson Leighton wrote:
> ---
> crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
>
> On Mon, Jul 27, 2020 at 5:30 AM Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
>
>>> although i have to ask why, for Embedded, they did not just recompile
>>> the source code, customised for that enduser application.
>> Because the distinction between "embedded" and "unix" is very blurry
> benjamin: this is not good! specifications should *never* be blurry!
> i believe you may mean something different, here, which warrants
> investigation. i think i know why, given that the typical markets for
> embedded PowerISA cores are specialist areas (aerospace and so on).
> Quorl for example is marketed at routers and definitely crosses over,
> yet is still termed "embedded".
>
>> and in many areas obsolete.
> ok let's look at the v3.1B document, page viii "Compliancy Subsets".
>
> nowhere in there - even in the scalar fixed-point section - am i
> seeing mention of what would be expected for "really resource
> constrained i.e. *truly* embedded" markets: being able to drop the
> (very expensive, gate-wise) logic decoding for catching illegal
> instructions, illegal SPR access, and so on.
>
> in SFS the drop in gate count from not needing a FPU is massive: an
> FPU typically dwarfs the size of the main core. once the FPU is
> dropped then relatively speaking further savings such as cutting those
> needed for illegal instructions becomes signficant (5% saving, 10%
> saving) and in mass-volume markets that's absolutely massive.
>
> let us therefore define "resource-constrained embedded markets" as
> "truly" embedded, rather than the blurry definition inspired by the
> meme that goes by the moniker "IoT", which now includes 8+ watt
> raspberry pi 4 devices that run so hot they need fan cooling.
>
> whilst it comes with the "burden" of needing to snapshot and maintain
> the full toolchain (which for customisation and custom extensions is a
> hard requirement anyway), one of the key areas in which RISC-V has
> been successful is the mass-volume *truly* embedded market.
>
> the canonical example is Western Digital, who up until RISC-V had
> their own "truly" embedded custom ISA which has been hyper-efficient
> for them, for use in SSDs, HDDs and USB Flash devices. the reason
> they wanted to go with RISC-v is to save on maintenance of their own
> custom toolchain (bear in mind that with a custom ISA you need not
> only a custom toolchain, you need a custom OS and custom applications
> as well! the cost to them of maintaining this would be enormous!)
>
> here, if the binary size is large, this cuts into the usage allocation
> of the on-board NAND and on-board RAM (because they don't have
> separate NAND from the customer-allocated area, or separate RAM for
> the cacheing of customer's data).
>
> if the NAND and RAM allocation are reduced, that has a very real
> detrimental impact on their sales and profitability, especially in
> such a highly competitive market!
>
> remember that for WD we are talking sales of billions of units, here.
> "a few gates" multiplied by a billion sales can make the difference
> between profit and loss.
>
> so they found when converting to RISC-V from their own internal ISA
> that binary size increased by (iirc) 20%. they absolutely had to do
> something about this and so set about analysing static instruction
> allocation and (i am projecting here as this was 2016) they would by
> now likely have used that research to create custom instruction
> modifications similar to the VLE Book, except targetted specifically
> at their use-case.
>
> none of these custom ISA modifications which result in code-size
> reduction that is important to their profitability in a very real way
> afaik are made public (i have not checked or heard any news so this
> could be wrong).
>
> this was all based on the initial base of *not* having to have the
> gates for illegal instruction catching etc., they had to go "custom
> firmware, custom toolchain" anyway, and the RISC-V initiative provided
> them with a huge cost saving on the toolchain and much more.
>
> so they got to have their cake and eat it:
>
> * cost savings on toolchain, kernel, os and bootloader maintenance (by
> being able to ride off the back of RISC-V "official")
> * cost savings from the "Embedded RISC-V Platform" already having made
> decisions that significantly reduced gate count
> * cost savings from further reductions by adding custom instructions
> and customising the toolchain to match them.
>
> *this* is *truly* embedded.
>
>
>
>> One can compile a single image that is meant to run on a wide variety
>> of system and even the "embedded" world wants that capability.
> if we are talking about the existing (core) OpenPOWER Foundation
> members subset embedded markets, served by their current product
> offerings: yes.
>
> if we are talking about the *full* (world-wide) definition of
> "embedded" which includes "truly" embedded: absolutely not.
>
> and i have to point out that if OpenPOWER's direction only takes into
> consideration the former, it is *guaranteed* that Power will never
> extend or see wide adoption into the latter. the cost-benefit
> analysis comes up so short that no mass-volume product manufacturer
> will consider it, and quite rightly so, as things stand.
>
> this then is the challenge for OpenPOWER if it wishes to have a wider
> reach: to adapt to beyond the needs of the current members, whilst
> also - very importantly - respecting the long-standing relationship,
> contribution and needs *of* those current members at the same time.
>
> it's a delicate balance to achieve.
>
>
>> Either
>> because they end up running some kind of "upstream" OS image, or
>> because they don't want to maintain completely different SW images for
>> all their products, etc...
> indeed. and this is perfectly reasonable, for what we've colloquially
> termed the "blurry" embedded markets. the cost savings of not having
> to recompile or maintain custom packages etc. - these are enormous
> savings, absolutely worthwhile pursuing.
>
> unfortunately, if that expectation then propagates throughout the
> entire OpenPOWER community as a "hard expectation" (even to the SFS
> Compliancy subset), it *automatically and inherently* excludes any
> possibility for "truly" embedded vendors to consider using POWER,
> because they are *prohibited* by the Compliancy Requirements from
> dropping the gates that would make the product profitable!
>
>
>>> however this also actually illustrates precisely why i mentioned that
>>> for best results, a spec has to have different platform behaviour for
>>> Embedded as completely separate and distinct from UNIX.
>> This is not really true anymore.
> thanks to the meme "IoT" and so on the word "embedded" when in general
> circulation has become meaningless, yes. i am not using the term
> "Embedded" in the meaningless sense, i am using it in the original
> sense used to describe 8 and 16 bit processor markets (when uprated to
> 32 and sometimes 64 bit).
>
> Embedded in the sense of Arduino PICs, ATMEL ATSAM3 series, ST Micro
> STM32F series, and so on. ARM Cortex M0, M3 style and such.
>
> not the "take the latest 64 bit high performance 2.5 ghz quad-core 8+
> watt processor, slap it into a SBC form-factor and call it quotes
> embedded quotes" definition of Embedded.
>
>> For example, do you consider your cell
>> phone or your TV "embedded" or "unix" ?
> UNIX, without a shadow of doubt. Android is a UNIX Platform. the
> Android kernel *is* the linux kernel, and, if end-users are prepared
> to put in some effort, all devices running Android - if there isn't
> Treacherous DRM built-in to the boot sequence - can have their OS
> entirely replaced by any GNU/Linux distro that's compatible with the
> processor.
>
> so no - those are *definitely* UNIX platform devices.
>
>>> this on the basis that Embedded Markets are typically one-off
>>> deployment, where the toolchain and all build source is "snapshotted"
>>> at product release time, used internally and the source code and
>>> toolchain almost never see the light of day. mainline upgrades are
>>> exceptionally rare.
>> There are quite a few counter examples even in the "embedded" market.
>> Especially when it comes to storage appliances. Some of these things
>> can even run CentOS.
> cool!
>
> however, again: are we referring to "general morphed (blurry)"
> definition of Embedded, or "truly" embedded?
>
>>> so in that context, i am slightly confused to hear that for Freescale
>>> *Embedded* processors that there is even a binary incompatibility
>>> problem with lwsync *at all*.
>>>
>>> if you have time i'd love to hear more, what's the story there?
>> I forgot the details, but a specific core variant from FSL screwed up
>> the decode table and would trap on lwsync instead of ignoring the bit.
> and, given the expectation to have binary interoperability even across
> "general" (aka colloquially blurry) Embedded, that would matter (a
> lot).
>
>>> indeed... in this very special case that we have established, by it
>>> effectively being a "hint", falls completely outside of what i am
>>> concerned about
>> In *most* cases trap + emulation leads to unusable performances though.
> this is another sub-topic entirely. the question one needs to ask is:
> *why* is performance unusable? *why* is the cost so high?
>
> RISC-V (again. there are many good bits to RISC-V) provides
> hardware-level partial-decode of instruction sub-fields. RA, RB, RS,
> RT (or, RISC-V equivalents) and other sub-fields, these are all
> available via individual SPRs (CSRs in RISC-V terminology) in the
> "illegal instruction" trap, saving huge numbers of mask/shift
> operations that make trap-and-emulate much faster and require far less
> instructions.
>
> without such hardware-level assistance yes i can see that trap and
> emulate would be considered completely unacceptable.
>
> we've diverged quite a lot from the original topic :) but also i
> believe provided some insights into the very different needs of
> different markets, which pull in completely polar opposite directions
> on the same ISA.
>
> the summary is: the Power Spec is a valued and valuable reflection of
> the needs of its community. the question becomes: does that community
> want to see OpenPOWER extend further? if so, it needs to learn from
> the analysis done by the RISC-V founders, who analysed *30 years* of
> RISC processor architectures and amalgamated the best bits that they
> thought would make a modern ISA *and eco-system* supporting a hugely
> diverse range of markets, from tiny ("truly") embedded all the way up
> to supercomputers.
>
> l.
> _______________________________________________
> OpenPOWER-HDL-Cores mailing list
> OpenPOWER-HDL-Cores@mailinglist.openpowerfoundation.org
> http://lists.mailinglist.openpowerfoundation.org/mailman/listinfo/openpower-hdl-cores
>
_______________________________________________
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] system call (sc) LEV "reserved field"
From: Luke Kenneth Casson Leighton @ 2020-07-27 8:00 UTC (permalink / raw)
To: Benjamin Herrenschmidt
Cc: openpower-hdl-cores, Libre-RISCV General Development
In-Reply-To: <16afa487019146baacfc26f50db637f6c2c9576a.camel@kernel.crashing.org>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Mon, Jul 27, 2020 at 5:30 AM Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
> > although i have to ask why, for Embedded, they did not just recompile
> > the source code, customised for that enduser application.
>
> Because the distinction between "embedded" and "unix" is very blurry
benjamin: this is not good! specifications should *never* be blurry!
i believe you may mean something different, here, which warrants
investigation. i think i know why, given that the typical markets for
embedded PowerISA cores are specialist areas (aerospace and so on).
Quorl for example is marketed at routers and definitely crosses over,
yet is still termed "embedded".
> and in many areas obsolete.
ok let's look at the v3.1B document, page viii "Compliancy Subsets".
nowhere in there - even in the scalar fixed-point section - am i
seeing mention of what would be expected for "really resource
constrained i.e. *truly* embedded" markets: being able to drop the
(very expensive, gate-wise) logic decoding for catching illegal
instructions, illegal SPR access, and so on.
in SFS the drop in gate count from not needing a FPU is massive: an
FPU typically dwarfs the size of the main core. once the FPU is
dropped then relatively speaking further savings such as cutting those
needed for illegal instructions becomes signficant (5% saving, 10%
saving) and in mass-volume markets that's absolutely massive.
let us therefore define "resource-constrained embedded markets" as
"truly" embedded, rather than the blurry definition inspired by the
meme that goes by the moniker "IoT", which now includes 8+ watt
raspberry pi 4 devices that run so hot they need fan cooling.
whilst it comes with the "burden" of needing to snapshot and maintain
the full toolchain (which for customisation and custom extensions is a
hard requirement anyway), one of the key areas in which RISC-V has
been successful is the mass-volume *truly* embedded market.
the canonical example is Western Digital, who up until RISC-V had
their own "truly" embedded custom ISA which has been hyper-efficient
for them, for use in SSDs, HDDs and USB Flash devices. the reason
they wanted to go with RISC-v is to save on maintenance of their own
custom toolchain (bear in mind that with a custom ISA you need not
only a custom toolchain, you need a custom OS and custom applications
as well! the cost to them of maintaining this would be enormous!)
here, if the binary size is large, this cuts into the usage allocation
of the on-board NAND and on-board RAM (because they don't have
separate NAND from the customer-allocated area, or separate RAM for
the cacheing of customer's data).
if the NAND and RAM allocation are reduced, that has a very real
detrimental impact on their sales and profitability, especially in
such a highly competitive market!
remember that for WD we are talking sales of billions of units, here.
"a few gates" multiplied by a billion sales can make the difference
between profit and loss.
so they found when converting to RISC-V from their own internal ISA
that binary size increased by (iirc) 20%. they absolutely had to do
something about this and so set about analysing static instruction
allocation and (i am projecting here as this was 2016) they would by
now likely have used that research to create custom instruction
modifications similar to the VLE Book, except targetted specifically
at their use-case.
none of these custom ISA modifications which result in code-size
reduction that is important to their profitability in a very real way
afaik are made public (i have not checked or heard any news so this
could be wrong).
this was all based on the initial base of *not* having to have the
gates for illegal instruction catching etc., they had to go "custom
firmware, custom toolchain" anyway, and the RISC-V initiative provided
them with a huge cost saving on the toolchain and much more.
so they got to have their cake and eat it:
* cost savings on toolchain, kernel, os and bootloader maintenance (by
being able to ride off the back of RISC-V "official")
* cost savings from the "Embedded RISC-V Platform" already having made
decisions that significantly reduced gate count
* cost savings from further reductions by adding custom instructions
and customising the toolchain to match them.
*this* is *truly* embedded.
> One can compile a single image that is meant to run on a wide variety
> of system and even the "embedded" world wants that capability.
if we are talking about the existing (core) OpenPOWER Foundation
members subset embedded markets, served by their current product
offerings: yes.
if we are talking about the *full* (world-wide) definition of
"embedded" which includes "truly" embedded: absolutely not.
and i have to point out that if OpenPOWER's direction only takes into
consideration the former, it is *guaranteed* that Power will never
extend or see wide adoption into the latter. the cost-benefit
analysis comes up so short that no mass-volume product manufacturer
will consider it, and quite rightly so, as things stand.
this then is the challenge for OpenPOWER if it wishes to have a wider
reach: to adapt to beyond the needs of the current members, whilst
also - very importantly - respecting the long-standing relationship,
contribution and needs *of* those current members at the same time.
it's a delicate balance to achieve.
> Either
> because they end up running some kind of "upstream" OS image, or
> because they don't want to maintain completely different SW images for
> all their products, etc...
indeed. and this is perfectly reasonable, for what we've colloquially
termed the "blurry" embedded markets. the cost savings of not having
to recompile or maintain custom packages etc. - these are enormous
savings, absolutely worthwhile pursuing.
unfortunately, if that expectation then propagates throughout the
entire OpenPOWER community as a "hard expectation" (even to the SFS
Compliancy subset), it *automatically and inherently* excludes any
possibility for "truly" embedded vendors to consider using POWER,
because they are *prohibited* by the Compliancy Requirements from
dropping the gates that would make the product profitable!
> > however this also actually illustrates precisely why i mentioned that
> > for best results, a spec has to have different platform behaviour for
> > Embedded as completely separate and distinct from UNIX.
>
> This is not really true anymore.
thanks to the meme "IoT" and so on the word "embedded" when in general
circulation has become meaningless, yes. i am not using the term
"Embedded" in the meaningless sense, i am using it in the original
sense used to describe 8 and 16 bit processor markets (when uprated to
32 and sometimes 64 bit).
Embedded in the sense of Arduino PICs, ATMEL ATSAM3 series, ST Micro
STM32F series, and so on. ARM Cortex M0, M3 style and such.
not the "take the latest 64 bit high performance 2.5 ghz quad-core 8+
watt processor, slap it into a SBC form-factor and call it quotes
embedded quotes" definition of Embedded.
> For example, do you consider your cell
> phone or your TV "embedded" or "unix" ?
UNIX, without a shadow of doubt. Android is a UNIX Platform. the
Android kernel *is* the linux kernel, and, if end-users are prepared
to put in some effort, all devices running Android - if there isn't
Treacherous DRM built-in to the boot sequence - can have their OS
entirely replaced by any GNU/Linux distro that's compatible with the
processor.
so no - those are *definitely* UNIX platform devices.
> > this on the basis that Embedded Markets are typically one-off
> > deployment, where the toolchain and all build source is "snapshotted"
> > at product release time, used internally and the source code and
> > toolchain almost never see the light of day. mainline upgrades are
> > exceptionally rare.
>
> There are quite a few counter examples even in the "embedded" market.
> Especially when it comes to storage appliances. Some of these things
> can even run CentOS.
cool!
however, again: are we referring to "general morphed (blurry)"
definition of Embedded, or "truly" embedded?
> > so in that context, i am slightly confused to hear that for Freescale
> > *Embedded* processors that there is even a binary incompatibility
> > problem with lwsync *at all*.
> >
> > if you have time i'd love to hear more, what's the story there?
>
> I forgot the details, but a specific core variant from FSL screwed up
> the decode table and would trap on lwsync instead of ignoring the bit.
and, given the expectation to have binary interoperability even across
"general" (aka colloquially blurry) Embedded, that would matter (a
lot).
> > indeed... in this very special case that we have established, by it
> > effectively being a "hint", falls completely outside of what i am
> > concerned about
>
> In *most* cases trap + emulation leads to unusable performances though.
this is another sub-topic entirely. the question one needs to ask is:
*why* is performance unusable? *why* is the cost so high?
RISC-V (again. there are many good bits to RISC-V) provides
hardware-level partial-decode of instruction sub-fields. RA, RB, RS,
RT (or, RISC-V equivalents) and other sub-fields, these are all
available via individual SPRs (CSRs in RISC-V terminology) in the
"illegal instruction" trap, saving huge numbers of mask/shift
operations that make trap-and-emulate much faster and require far less
instructions.
without such hardware-level assistance yes i can see that trap and
emulate would be considered completely unacceptable.
we've diverged quite a lot from the original topic :) but also i
believe provided some insights into the very different needs of
different markets, which pull in completely polar opposite directions
on the same ISA.
the summary is: the Power Spec is a valued and valuable reflection of
the needs of its community. the question becomes: does that community
want to see OpenPOWER extend further? if so, it needs to learn from
the analysis done by the RISC-V founders, who analysed *30 years* of
RISC processor architectures and amalgamated the best bits that they
thought would make a modern ISA *and eco-system* supporting a hugely
diverse range of markets, from tiny ("truly") embedded all the way up
to supercomputers.
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] Fwd: [LPC] XDC2020 - Your proposal has been accepted
From: Jacob Lifshay @ 2020-07-26 16:37 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwzWMadsDQGcJnXDmrwN9963geyxoi-Z7MkSXLGhc1ffw@mail.gmail.com>
On Sun, Jul 26, 2020, 01:25 lkcl <luke.leighton@gmail.com> wrote:
> ok so that's been accepted
>
Yay!
link to publicly accessible version:
https://xdc2020.x.org/event/9/contributions/607/
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] daily kan-ban update 26jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-26 14:17 UTC (permalink / raw)
To: Libre-RISCV General Development
task list:
*
https://bugs.libre-soc.org/showdependencytree.cgi?id=383&maxdepth=1&hide_resolved=1
yesterday:
* went over trap and div
* found long-standing bug in decode fields (OE)
today:
* created TestAccumulatorBase class
* discovered and fixed another bug in LDSTCompUnit
* added nop unit test (actually, ori 0,0,0)
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] simulator get time API
From: Luke Kenneth Casson Leighton @ 2020-07-26 8:30 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5qyQr3Xz5Qq=aT7BmYtg2SKWT8oH+ay62ES-bHU7KAjQ@mail.gmail.com>
On Sun, Jul 26, 2020 at 6:13 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
> # TODO: raise bugreport with whitequark
> # requesting a public API to access this "officially"
> # XXX print("time:", sim._state.timeline.now)
>
> Feature request already submitted:
> https://github.com/nmigen/nmigen/issues/443
fantastic.
_______________________________________________
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] Fwd: [LPC] XDC2020 - Your proposal has been accepted
From: lkcl @ 2020-07-26 8:25 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <159574530246.1457.14701379022617557855@linuxplumbersconf.org>
ok so that's been accepted
---------- Forwarded message ---------
From: <noreply@lwn.net>
Date: Sun, Jul 26, 2020 at 7:35 AM
Subject: [LPC] XDC2020 - Your proposal has been accepted
To: <luke.leighton@gmail.com>
Dear Luke Leighton,
We are pleased to announce that your abstract "The Libre-SOC Project"
has been accepted!
In case you are in a different timezone than Europe, please include
the hours you are available to give your presentation. We will try to
define the final schedule taking your preferences into account. The
conference schedule is expected to be between 9:30 and 17:15 UTC+2
every day, pending to confirm once we get all the talks confirmed.
See below a summary of your submitted abstract:
Conference: X.Org Developers Conference 2020
Submitted by: Luke Leighton
Title: The Libre-SOC Project
Presentation type:
For more details please visit the page of your abstract:
https://xdc2020.x.org/event/9/abstracts/657/.
Kind regards,
The XDC 2020 Program Committee
--
Indico :: Call for Abstracts
https://xdc2020.x.org/event/9/
_______________________________________________
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] simulator get time API
From: Jacob Lifshay @ 2020-07-26 5:13 UTC (permalink / raw)
To: Libre-RISCV General Development
# XXX sim._state is an internal variable
# and timeline does not exist
# AttributeError: '_SimulatorState' object
# has no attribute 'timeline'
# TODO: raise bugreport with whitequark
# requesting a public API to access this "officially"
# XXX print("time:", sim._state.timeline.now)
Feature request already submitted:
https://github.com/nmigen/nmigen/issues/443
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] daily kan-ban update 25jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-25 20:57 UTC (permalink / raw)
To: Libre-RISCV General Development
tasks:
* https://bugs.libre-soc.org/showdependencytree.cgi?maxdepth=1&id=383&hide_resolved=1
yesterday:
* went over DIV tests a bit. reorganised.
* likewise Trap
* generally bitched about maturin and was amazed and impressed when
they listened (cool!)
today:
* added some "names" to records that will help with the coriolis2 layout
* tracked down a MAJOR bug where the OE field was being set to the Rc field
* put div pia back in place
i can't quite believe it's taken this long, with all the unit tests in
place, to track down that bug in decoder_fields.py, from a
"convenience" dictionary that had been manually written. it set the
decode.OE field from the *Rc* field (msb0 bit 31) rather than msb0 bit
21.
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] microwatt IEE754FP
From: Luke Kenneth Casson Leighton @ 2020-07-25 19:52 UTC (permalink / raw)
To: Paul Mackerras, openpower-hdl-cores; +Cc: Libre-RISCV General Development
paul, hi,
thought i'd give a glimpse into the testing behind IEEE754
this is what jon dawson did:
https://github.com/dawsonjon/fpu/blob/master/adder/run_test.py
note that that test is expected to produce hundreds of thousands of test
vectors.
*this is perfectly normal* when testing IEEE754(!)
if you look at the test.cpp file it is a native operation that uses the c
library. therefore running it on x86 will only be testing *against x86
IEEE754*, not POWER9!
compiled on *POWER9* it would obviously produce QNaNs etc etc for POWER9
compatibility.
this of course assumes you *have* access to native hardware.
our first exploration therefore took us via john hauser's excellent
softfloat-3 (with python bindings, sfpy):
https://github.com/ucb-bar/berkeley-softfloat-3
this allows full crossplatform emulation of the various different subtle
variations in IEEE754 FP rounding, NaNs and so on.
intel's NaN is different from ARM's NaN is different from RISCV blah blah
and so you simply must use an emulation library.
12 months later we had IEEE754 pipelines for the major operations,
including SQRT RSQRT and so on, and are looking to add sin, cos, log1p,
atan2 etc. next year.
our equivalent to jon dawson's unit tests we have libraries such as these:
https://git.libre-soc.org/?p=ieee754fpu.git;a=blob;f=src/ieee754/fpcommon/test/unit_test_double.py;h=6dee89d26fa98f821435848c9f92ec17cff2d9da;hb=dc9082559f7fba8555c2f76a6de95a6d84a6d087
there you can see it creates test vectors with zero, minus zero, inf, minus
inf and so on all making sure to get good coverage that would simply stand
no chance of being hit with pure random uniform distribution of values.
conversion from FP64 to FP32 or int etc had to be a little different
because again if you try to test the full range of FP64 converted to UINT16
almost all of those will be out of range (result in 0xffff in nearly 100%
of all uniformly random test cases).
one thing missing from the FP unit tests that i must add is exponentially
weighted random input for the non-normal numbers (less than 2^-126 for
FP32).
these are the values where the exponent is the absolute lowest possible
value and the mantissa then no longer has the implicit 1. in this range it
is no good trying to use a uniform distribution of mantissas, you need an
*exponentially weighted* distribution of mantissas:
x = random(0, 23) # 23 is length of FP32 mantissa
mant_test = random((1<<(x-1))-1, (1<<x)-1)
basically what i am trying to say is that the effort for *testing* any
given IEEE754 FP implementation far exceeds the effort needed for the RTL
implementation itself by literally an order of magnitude, to do in any kind
of meaningful way that will give users confidence in the implementation.
about the only IEEE754 spec that could potentially be full coverage tested
is FP16 and even there that is 4 billion unit tests needed for 2-operand
tests (only 2^16 for 1 operand tests). however POWER9 does not have FP16.
the primary reason why i mention this is because for proper OpenPOWER
Compliance such a comprehensive IEEE754 FP test suite is still *nowhere
near enough*, and the only sure-fire way to get 100% confidence is with a
Formal Correctness Proof. and that is a *big* project.
remember the Intel Pentium FPDIV bug.
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] zulip chat
From: Luke Kenneth Casson Leighton @ 2020-07-24 20:53 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7eJE=nC575xetF=TOzDDvcB3+Gp2xL6LKPh1REwYsDqw@mail.gmail.com>
On Friday, July 24, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
>
> I think we should try using Zulip https://zulipchat.com/ -- it's an
> open-source chat web app that Rust is using with great success. It's
> written in Python. It can interface with all of IRC, email, Matrix, git,
> gitlab, and many more.
oooOOoo :)
https://github.com/zulip/zulip-desktop
i think it's like pidgin used to be, except it seems like it crosses
different channels as well.
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] zulip chat
From: Jacob Lifshay @ 2020-07-24 20:30 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <bug-417-11-z2HgsCPVSg@https.bugs.libre-soc.org/>
On Fri, Jul 24, 2020, 07:18 <bugzilla-daemon@libre-soc.org> wrote:
> https://bugs.libre-soc.org/show_bug.cgi?id=417
>
> --- Comment #26 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> (In reply to Cesar Strauss from comment #25)
> > I joined the channel as "cesar".
>
> we really should run our own irc channel
>
I think we should try using Zulip https://zulipchat.com/ -- it's an
open-source chat web app that Rust is using with great success. It's
written in Python. It can interface with all of IRC, email, Matrix, git,
gitlab, and many more.
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] system call (sc) LEV "reserved field"
From: Luke Kenneth Casson Leighton @ 2020-07-24 16:53 UTC (permalink / raw)
To: Benjamin Herrenschmidt
Cc: openpower-hdl-cores, Libre-RISCV General Development
In-Reply-To: <b3a6d1be404b96594d69d9b59701c574957c8d2a.camel@kernel.crashing.org>
On Thursday, July 23, 2020, Benjamin Herrenschmidt <benh@kernel.crashing.org>
wrote:
> On Thu, 2020-07-23 at 05:16 +0100, Luke Kenneth Casson Leighton wrote:
> >
> > what i have observed (again this is from RISCV), for instructions
> > that can be "safely ignored" are of a "hint" type.
>
> See what Paul said... the idea is that any change to an existing
> instruction that makes use of formerly reserved bits needs to be done
> in such a way that the ignoring the bits is a correct implementation.
this works well if extremely carefully managed, and planned well in advance.
at no time can the new functionality step *up* or otherwise be anything
other than an optimisation.
In practice that often means the new bits are indeed hints,
this is an accidental discovery! i had not meant them to be considered
"hints" however now that you mention it, it makes a lot of sense.
lwsync would fall into this category.
but not
> always, see Paul example about mfocrf.
indeed. although it makes me nervous, that 2/2 cases quoted have known
issue where they did not go as planned.
i am guessing that mtmsr L=0/1 may also have been extended at some point?
that in an earlier version of the spec it was only L=0?
> > i.e. old sync is a "superset" of lwsync?
>
> sync is a memory barrier. lwsync is a lighter weight version of it, so
> yes, sync is a superset of lwsync.
ok, good. so it is an optimisation. as a "hint" type it would be "safe"
hints are only safe to add precisely because they are declared in advance -
long before anyone even implements the very first implementation of the
very first core - to have no change in functionality, merely an opportunity
for performance optimisation.
> > bit did not matter, the trap would call the alternative sync
> > instruction, and return from the trap.
>
> The performance impact of this would make it entirely unusable however.
in that example, yes. most unfortunate.
>
> > i do not know the full story about what FSL is: without knowing the
> > details i suspect that a trap *could* have sorted things out, there,
> > *if* the older processor was required to raise "illegal instruction"
>
> FSL is Freescale.
ahh ok.
>
>
Some variants of their embedded cores did trap, which
> forced the kernel to do some nasty dynamic patching at runtime to get
> rid of lwsync's on these.
a low-grade version of JIT translation, which is one solution. expensive,
but a solution.
although i have to ask why, for Embedded, they did not just recompile the
source code, customised for that enduser application.
however this also actually illustrates precisely why i mentioned that for
best results, a spec has to have different platform behaviour for Embedded
as completely separate and distinct from UNIX.
the rules for Embedded in RISCV state that traps are *not* needed for
illegal instructions (it is up to an implementor to decide if they wish to
add them). the Conformance Test Suite does *not* test for illegal
instructions.
this on the basis that Embedded Markets are typically one-off deployment,
where the toolchain and all build source is "snapshotted" at product
release time, used internally and the source code and toolchain almost
never see the light of day. mainline upgrades are exceptionally rare.
examples include Trinamic Stepper ASICs, which actually hit the shelves
even before RISCV Standardisation was ratified.
the binaries are in ROM. whatever trap spec incompatibility with "Latest
and Greatest" are utterly irrelevant for them and their customers.
so in that context, i am slightly confused to hear that for Freescale
*Embedded* processors that there is even a binary incompatibility problem
with lwsync *at all*.
if you have time i'd love to hear more, what's the story there?
> > but because the bit is ignored, there is no way that can be done.
>
> But that's fine because "sync" is a strict superset so ignoring the bit
> works just fine.
in this case, yes.
>
> > so whilst on the face of it, lwsync *sounds* like a counterexample,
> > instead (caveat, i do not know what FSL is), it seems more to support
> > the case *for* use of reserved bits raising illegal instructions [on
> > UNIX platforms]
>
> I fail to follow your logic. The trap case is a complete non-starter
> for an instruction meant to be a lightweight memory barrier.
ok given that it is a "hint" type and not quite suited to "reserved" we are
now at cross purposes.
and, also, it is a special case that happens to gave, as one of its
requirements, to be "lightweight" in order to be useful.
The
> transparent "fallback" to a full memory barrier on the contrary works
> fine. There is never any case where "trapping an emulating" is the
> desired behaviour.
indeed... in this very special case that we have established, by it
effectively being a "hint", falls completely outside of what i am concerned
about
>
> >
> > > > if however reserved bits being set cause an exception, the "old"
> > > > processor stands a chance of emulating the new behaviour (in
> > > > software, even if that's slow), giving it a chance of keeping out
> > > of
> > > > landfill for slightly longer.
> > >
> > > Which is why powerpc tends not to "add bits" to instructions unless
> > > ignoring them is a safe fallback.
> >
> > as we can see above, the example that was given shows that this is a
> > problematic approach.
>
> I fail to understand the "problem" in your example, maybe you can
> rephrase it ?
we've identified that lwsync is a "hint" so can discount it.
i'll need to take some more time to think about it. also, it requires
explaining the context.
OpenPOWER is, under the auspices of the Foundation, i gather aiming for
much wider adoption whilst also retaining the reputation for performance
and stability, *and* allowing for extensions and customisation under the
stewardship of the Foundation.
with so few members using POWER up to this point, there has been little in
the way of conflict because there is no "pulling in different directions"
and, as Paul pointed out, a lot of care and thought has gone into any
upgrades.
looking for comparisons - examples from the past - is therefore actually
going to be difficult.
> > i have not spelled it out explicitly, seeking instead to use logical
> > reasoning rather than make categorical statements, but this is
> > actually a really serious problem.
>
> Again, experience seems to indicate this is not as long as the
> definition of the architecture is careful in how the reserved bits get
> allocated in the future.
if they are genuinely synonymous with (effectively) a "hint" then there is
absolutely no problem at all... *as long as* the entire area has been
declared fully and well in advance that it is of type "hint".
for example mtmsr L=1 (which i am assuming perhaps incorrectly was added
long after L=0, is that correct? if not let us assume hypothetically that
it was) absolutely in no way falls into the "safe" category because it
damages bits of MSR unexpectedly. or only updates some of them.
in this (hypothetical?) case, modern software running on an older UNIX
Platform processor that only supported L=1 could *only* sort things out
*if* a trap was taken.
and yet the spec explicitly says, "don't bother", which is *guaranteed* to
cause problems.
SC having LEV > 1 in the future is also a special case because it is
*already* raising a trap. no extra cost, there. things can be sorted
out.... in the trap.
> > in other words the approach of ignoring reserved bits has only worked
> > (for the past 20 years?) because IBM, realistically, is the only
> > (non-Embedded) implementor of UNIX Platform processors.
>
> That wasn't always true and still didn't become a problem.
>
> Again, I really fail to see the smoking gun you seem to be implying
> there is.
no gun.
it is that things have changed, now.
where before the specification could be managed by a few vendors, for a few
vendors (managed extremely well) the intention as i understand it is to
expand the reach of OpenPOWER, and allow dozens if not hundreds of
implementors to participate in its ongoing evolution, just as is done with
RISCV.
under such changed circumstance it is well known and well established that
it is *not safe* to have reserved bits *not* throw exceptions on the UNIX
Platform.
bear in mind that we established that lwsync is a "hint", and that hints
*are* safe to add (as long as the available range is reserved fully, in
advance) and do not and should not raise exceptions because they are
performance optimisations.
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] daily kan-ban update 23jul2020
From: Cole Poirier @ 2020-07-23 20:41 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyGD-jX-kwU3uDLyg+H-qga3F1+LZbOKBKx_jeOC8S+XA@mail.gmail.com>
On Thu, Jul 23, 2020 at 1:37 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> you're good.
Thanks, works.
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 23jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-23 20:36 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAEg7hukasSLnGq+mbR+4G1sKWuLJ=4MNOWEWXjOeb-7SUnGiHA@mail.gmail.com>
On Thursday, July 23, 2020, Cole Poirier <colepoirier@gmail.com> wrote:
> On Thu, Jul 23, 2020 at 12:19 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > that should be gitolite3 not gitolote3
doh
>
> ```
> colepoirier@cherrytree:~$ ssh gitolite3@git.libre-soc.org
>
> R W libreriscv
you're good.
--
---
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] openpower virtual coffee
From: Luke Kenneth Casson Leighton @ 2020-07-23 20:03 UTC (permalink / raw)
To: Libre-RISCV General Development, Linux on small ARM machines
https://openpowerfoundation.org/openpower-virtual-coffee-calls/
in 2 hours. conference call dial-in numbers at the above web page
(which do not involve running non-free proprietary software to attend)
these are an open informal chat, not recorded, no "agenda". topics
have been thoroughly eclectic and enjoyable.
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] daily kan-ban update 23jul2020
From: Cole Poirier @ 2020-07-23 19:26 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4pXM4EkT+MZ1EqQ4HM_bQjCVVD-REvGRiQ4XKU5=7KTQ@mail.gmail.com>
On Thu, Jul 23, 2020 at 12:19 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> that should be gitolite3 not gitolote3
```
colepoirier@cherrytree:~$ ssh gitolite3@git.libre-soc.org
PTY allocation request failed on channel 0
hello colepoirier, this is gitolite3@libre-soc running gitolite3
3.6.6-1 (Debian) on git 2.11.0
R W crowdsupply
R W dev-env-setup
R freedom-sifive
R gitolite-admin
R ieee754fpu
R kazan
R W libreriscv
R W litex
R llvm
R W nmigen-soc
R nmutil
R pinmux
R riscv-isa-sim
R riscv-tests
R rv32
R sfpy
R shakti-core
R shakti-iclass
R shakti-mclass
R shakti-peripherals
R sifive-blocks
R W soc
R soclayout
R sv2nmigen
R W testing
Connection to git.libre-soc.org closed.
```
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 23jul2020
From: Jacob Lifshay @ 2020-07-23 19:18 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAEg7hunRf3jUJeD=1Csse5YFU_VuWdCgxxgR-kyVrHtcKM+j4w@mail.gmail.com>
On Thu, Jul 23, 2020, 12:14 Cole Poirier <colepoirier@gmail.com> wrote:
> On Thu, Jul 23, 2020 at 11:47 AM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
> > what does ssh gitolote3@git.libre-soc.org come back with?
>
that should be gitolite3 not gitolote3
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] daily kan-ban update 23jul2020
From: Cole Poirier @ 2020-07-23 19:14 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwn0P283KkhfaemdrUysc20+do3eSBDJ38A3W7P=qQt9A@mail.gmail.com>
On Thu, Jul 23, 2020 at 11:47 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
> what does ssh gitolote3@git.libre-soc.org come back with?
```
colepoirier@cherrytree:~$ ssh gitolote3@git.libre-soc.org
gitolote3@git.libre-soc.org's password:
```
Not sure what this implies...
> (done btw)
Thanks
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 23jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-23 18:47 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAEg7huki8XE_=HGGGkpgHPemTyd+xqGg8P0nm7vqbHwcMEYFUQ@mail.gmail.com>
On Thursday, July 23, 2020, Cole Poirier <colepoirier@gmail.com> wrote:
>
> I can't push my commit to the libreriscv repo,
what does ssh gitolote3@git.libre-soc.org come back with?
(done btw)
--
---
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] daily kan-ban update 23jul2020
From: Cole Poirier @ 2020-07-23 18:26 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzfkzt8XG5G43PiWOtqJELjLNeBc8ums-Suio+K9NJLYg@mail.gmail.com>
Yesterday:
* Finished updating the wiki libreriscv/HDL_workflow/coriolis2
documentation to sync it with the coriolis-chroot setup script
I can't push my commit to the libreriscv repo, can you please grant me
access Luke?
Today:
* Script and document soclayout workflow, will coordinate via "Bug 291
- HDL Workflow and Coriolis2 chroot automated setup scripts"
<https://bugs.libre-soc.org/show_bug.cgi?id=291>
* Investigate how to "Add post-receive git hooks to git.libre-soc.org
that mirror repos to debian salsa." per comment #16 from
<https://bugs.libre-soc.org/show_bug.cgi?id=190#c16> on "Bug 190 -
Setup Gitlab CI Runner for Kazan on a computer", will coordinate via
this bug report
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, 22jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-23 17:11 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD61pYs-vZzduaZq0j-xovmgH+Xv188HTV6r1rUJB5TtpQ@mail.gmail.com>
On Thursday, July 23, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> for soc, we can copy the test case generation logic from DivPipeCore's
> tests in ieee754fpu since that covers waaay more cases (nicely
> exponentially distributed too) but is also deterministic. it covers the
> cases:
> for all 0 <= a < 2^8 and 0 <= b < 64:
> the case a << b if b < 64 - 8
> and the case ~(a << b) if b < 64 - 8
> and the case (1 << b) - 1
> and the case ~((1 << b) - 1)
ohh yeh i remember now.
> It might use a different value than 8 -- icr.
>
> this covers all the corner cases I can think of, which random testing has a
> very small chance of ever hitting
yehyeh this is why the ieee754fp tests have to have special cornercase
handling, zero, inf, nan etc.
(small enough that you'd need every
> person on the planet to all run the test on the order of a billion times
> each to hit the case once).
:)
we need a way to express these, cross language, so that they can be run in
multiple scenarios.
qemu, pia, ISACaller, HDL.
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] daily kan-ban update, 22jul2020
From: Jacob Lifshay @ 2020-07-23 17:06 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzsho_Jemrm03UG1UmwxtjnGx5+G47JBbGSVgH4DLc3TQ@mail.gmail.com>
On Thu, Jul 23, 2020, 09:42 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Thursday, July 23, 2020, Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > On Thu, Jul 23, 2020, 02:40 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> > wrote:
> >
> > > On Thursday, July 23, 2020, Luke Kenneth Casson Leighton <
> lkcl@lkcl.net>
> > > wrote:
> > >
> > > >
> > > >
> > > > On Thursday, July 23, 2020, Jacob Lifshay <programmerjake@gmail.com>
> > > > wrote:
> > > >
> > > >>
> > > >> SimOnly, I discovered that for test_divwuo_regression_1 (0xc4e32b68
> /
> > > >> 0x32867d69), the pipeline (SimOnly) is giving the correct results
> > > >> (rt=0x3), it's the ISA simulator code that's messed up
> > > >> (rt=0xFFFFFFFF).
> > > >
> > > >
> > > > please raise a bugreport for it.
> > > >
> > >
> > > saw it, thank you for doing that.
> > >
> > > these look great btw
> > >
> > >
> > >
> > > https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=
> > 78096b62db0345846cca70ab2f75f9c3519006c4
> >
> >
> > Thanks! I used the same list of test values as in
> > power-instruction-analyzer.
>
>
> i wondered if, like in the ieee754fp tests, if some random values could be
> added, too.
>
I specifically want the test cases to be reproducible for
power-instruction-analyzer, since the test results generated on a POWER9
cpu are checked into the repo for those who don't have a POWER9.
for soc, we can copy the test case generation logic from DivPipeCore's
tests in ieee754fpu since that covers waaay more cases (nicely
exponentially distributed too) but is also deterministic. it covers the
cases:
for all 0 <= a < 2^8 and 0 <= b < 64:
the case a << b if b < 64 - 8
and the case ~(a << b) if b < 64 - 8
and the case (1 << b) - 1
and the case ~((1 << b) - 1)
It might use a different value than 8 -- icr.
this covers all the corner cases I can think of, which random testing has a
very small chance of ever hitting (small enough that you'd need every
person on the planet to all run the test on the order of a billion times
each to hit the case once).
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
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