* [libre-riscv-dev] [Bug 309] New: investigate OpenTITAN
From: bugzilla-daemon @ 2020-05-13 12:57 UTC (permalink / raw)
To: libre-riscv-dev
https://bugs.libre-soc.org/show_bug.cgi?id=309
Bug ID: 309
Summary: investigate OpenTITAN
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: PC
OS: Linux
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Source Code
Assignee: lkcl@lkcl.net
Reporter: lkcl@lkcl.net
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
http://opentitan.org
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] daily kan-ban update 13may2020
From: Luke Kenneth Casson Leighton @ 2020-05-13 10:28 UTC (permalink / raw)
To: Libre-RISCV General Development
yesterday i started on integrating the LDSTCompUnit into the
scoreboard and immediately ran into a brick wall in the form of the
address-request/release signalling. when go_addr is raised (in
response to req_addr), the LDSTCompUnit is supposed to drop req_addr
one cycle later: instead it stays high.
i also investigated microwatt to find out what the heck is going on
with the register-order-swapping. turns out that different classes of
operations (logical, rotate, arith) have different ordering. why? who
knows.
today i will continue working through the address-negotiation in LDSTCompUnit.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 238] POWER Compressed Formal Standard writeup
From: bugzilla-daemon @ 2020-05-13 9:38 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-238-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=238
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.libre-soc.org/
| |show_bug.cgi?id=308
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 308] POWER variable-length encoding scheme needed
From: bugzilla-daemon @ 2020-05-13 9:38 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-308-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=308
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.libre-soc.org/
| |show_bug.cgi?id=238
NLnet milestone|--- |NLNet.2019.10.Standards
--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
note, not to be confused with bug #238 which is *actual* compressed
(16-bit) instruction encodings.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 308] New: POWER variable-length encoding scheme needed
From: bugzilla-daemon @ 2020-05-13 9:37 UTC (permalink / raw)
To: libre-riscv-dev
https://bugs.libre-soc.org/show_bug.cgi?id=308
Bug ID: 308
Summary: POWER variable-length encoding scheme needed
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: PC
OS: Linux
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Specification
Assignee: lkcl@lkcl.net
Reporter: lkcl@lkcl.net
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
instruction stream order needs to be sorted out so that the proposed
Compressed/48/64/VBLOCK encoding will fit. currently, LE on POWER
is wholly unsuited to variable-length ISA encoding due to the opcode
being at the wrong end of a sequential instruction byte stream
https://libre-soc.org/openpower/
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-May/006553.html
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 291] HDL Workflow and Coriolis2 chroot automated setup scripts
From: bugzilla-daemon @ 2020-05-13 9:19 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=291
--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #7)
> (In reply to Luke Kenneth Casson Leighton from comment #6)
> > ok so there's nothing in there which says "picking a hard-coded git tag
> > number"
> > so i suspect that it's as simple as jean-paul made a commit recently which
> > broke something.
>
> Ah, I'm realizing now that I really should have been using a hard-coded git
> tag number.
ah - no, not exactly. keep it simple for now. the idea we came up with
is to have a new (single) repo with git submodules.
the git branch/tag info will be encoded into the submodules. this way,
the script remains the same.
> Can you share your known-working git tag number for coriolis2 so
> I can continue working on the script tomorrow?
wait for jean-paul to investigate:
https://gitlab.lip6.fr/vlsi-eda/coriolis/-/issues/13
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] [OpenPOWER-HDL-Cores] little-endian only power cores and spec compliance
From: Benjamin Herrenschmidt @ 2020-05-13 1:41 UTC (permalink / raw)
To: Hugh Blemings, Jacob Lifshay, openpower-hdl-cores
Cc: Libre-RISCV General Development
In-Reply-To: <ec667579-06e2-ff44-4604-b160149feaa3@blemings.org>
On Wed, 2020-05-13 at 11:22 +1000, Hugh Blemings wrote:
> Hi All,
> I'm barely qualified to add much more than $0.20 to this thread, but
> will give it a whirl...
> I've not had a chance to dig into the v3.1 spec as yet but can offer
> the observation that the intent (as demonstrated in the Microwatt
> implementation for example) was that the simpler/simplest
> implementations would be LE with BE optional. SIMD also optional in
> these as well.
The main difficulty is that in practice, a powerpc64le toolchain will
generate code with both FP and SIMD instructions. I don't think it's
possible to generate a fully soft-float one and even if you managed
with gcc, glibc somewhat assumes it too. At least from memory.
If OpenPower wants to go down a path more similar to RiscV here and
support small(er) implementations, it's necessary to stop having the
toolchain engineers push for only supporting the latest/greatest IBM
server CPUs :-)
The Microwatt core is now starting to boot Linux as well (not merged
yet) but at the moment this requires some kernel hacks to work around
the above, such as plumbing in FPU emulation, and I know Paul has
issues generating a usable userspace...
> So if the docs don't represent this we'll need to take a closer look
> :)
> We're getting more of the key folk from our member companies (mostly
> IBM) into the loop through this list but as Luke rightly pointed out
> over on libre-riscv-dev they're a busy crew at the moment with a new
> chip due out soon :)
> That said I imagine someone will chime in soon who -actually- knows
> this stuff!
> Cheers,
> Hugh
> (Speaking for myself only in this case, though I believe wearing my
> ED hat I'd be saying much the same :)
>
> On 12/5/20 5:24 pm, Jacob Lifshay 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
> >
> >
> > _______________________________________________
> > OpenPOWER-HDL-Cores mailing list
> > OpenPOWER-HDL-Cores@mailinglist.openpowerfoundation.org
> >
http://lists.mailinglist.openpowerfoundation.org/mailman/listinfo/openpower-hdl-cores
>
> _______________________________________________
> 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] [OpenPOWER-HDL-Cores] little-endian only power cores and spec compliance
From: Luke Kenneth Casson Leighton @ 2020-05-13 9:11 UTC (permalink / raw)
To: Benjamin Herrenschmidt
Cc: openpower-hdl-cores, Libre-RISCV General Development
In-Reply-To: <ba6dfcfcac4cb37dab95ba1669f68f57f01347d1.camel@ozlabs.org>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Wed, May 13, 2020 at 7:01 AM Benjamin Herrenschmidt <benh@ozlabs.org> wrote:
>
> On Wed, 2020-05-13 at 11:22 +1000, Hugh Blemings wrote:
> > Hi All,
> > I'm barely qualified to add much more than $0.20 to this thread, but
> > will give it a whirl...
> > I've not had a chance to dig into the v3.1 spec as yet but can offer
> > the observation that the intent (as demonstrated in the Microwatt
> > implementation for example) was that the simpler/simplest
> > implementations would be LE with BE optional.
yes. this was the take-away i got from reading it. the summaries
were as follows:
* AIX Platform - POWER9 and above
must support 64 and 32 bit
must support LE and BE
* UNIX Platform - (i call it UNIX because RTOSes and L4Ka are not
"Linux") - *also POWER9 and above*
must support 64 bit (32-bit probably optional, not explicity stated)
must support LE (BE explicity stated as optional)
* SFFS - basically this recognises and gives space to the NXP QuorlQ
series (which is V2.07B(?) compliant)
must support 32-bit (64-bit optional, explicitly stated)
must support BE (LE explicity stated as optional)
* SFS - basically this recognises and gives space to the NXP MC5xxx
32-bit embedded series
must support 32-bit (64-bit optional, explicitly stated)
must support BE (LE explicity stated as optional)
note that *only POWER9* meets the requirements of the AIX and UNIX
platforms. microwatt, by being a LE-only and non-VMX/VSX processor,
does not fall into *any* Compliance Category.
this puts microwatt firmly into "custom-built distro" territory. our
design likewise - even though it will have 3D and VPU Vector
capability - will *still* be in "custom distro" territory, which is a
massive burden on customers and end-users.
with the product intended for mass-production, that means it'll end up
with "Rasbian" community-driven distros being created. (Rasbian was -
and is - a damn nuisance. the original Broadcom processor used in the
Pi v1 was neither armel nor armv7: consequently it had to have its own
complete and total recompiled Debian distro, annoying the hell out of
the Debian Community due to the mis-filed bugreports and
miscategorised - unpaid - end-user support requests)
now, for Android-based products and Chromebook-based products *this is
not a problem*. Android and chromebook products always
custom-recompile the entire binaries from source anyway.
but for distros? debian? fedora? as things stand, we're excluded -
and so is microwatt. microwatt as it stands cannot run *either* the
ppc32 debian distro *or* ppc64le distro binaries.
that exclusion - being unable to run standard debian or fedora distros
- in turn makes community grass-roots development almost impossible to
kick-start a thriving community and knowledgeable user-base.
> > SIMD also optional in these as well.
unfortunately that was left out: only the SFFS and SFS subsets
(intended primarily to be 32-bit BE) are permitted to have SIMD (VMX
and VSX) optional.
it means that we (and microwatt, and any other new processor designer)
have a whopping 600 additional instructions to add (in addition to the
appx-380), with a full Vector Engine if they (we) would like their
product to take advantage of the time and effort saved by availability
of distro pre-compiled binaries (Fedora, Debian).
this is a very high threshold, which, working through the
implications, would simply have quite a significant number of
otherwise interested parties in POWER from pursuing other options.
the extra register file (Vector Regfile is separate) alone will be
enough to make them think twice.
if you already *have* VSX and VMX implemented, it is perfectly
reasonable to have it on the AIX and UNIX Platforms. however for a
new entrant?
> The main difficulty is that in practice, a powerpc64le toolchain will
> generate code with both FP and SIMD instructions. I don't think it's
> possible to generate a fully soft-float one and even if you managed
> with gcc, glibc somewhat assumes it too. At least from memory.
a solution exists (it involves modifications to gcc, binutils and glibc).
the RISC-V Foundation members have been working on support for
multiple-compilations of functions - the exact same function -
compiled multiple times and the resultant assembly code inserted under
the *same function name* into the object file, with sufficient
metadata to be able to discern it from "functions-with-the-same-name".
(this i specifically mention because it is not a new form of c++
name-mangling being deployed, here)
what then happens at dynamic link time is this:
* the capabilities of the processor are detected
* the existence of two (or more) versions of the same dynamic-linked
function is noted
* the *CORRECT AND REQUIRED* version of that function according to the
*hardware* capabilities is selected *dynamically*.
this includes defining *new ABIs* suitable for each type of "hardware
capability". so for example for RISC-V Vectors, they are defining a
new glibc6 ABI for vectors...
... *and compiling functions twice - once to conform to the Vector ABI
and once to conform to the standard scalar ABI*.
thus when it comes to "who must win" this is now entirely moot:
everyone can be happy.
Questions:
1) does the executable size increase? yes of course.
2) is it the same as multilib? honestly i am not sure that it is.
or, if it is, it's the mechanism *behind* multilib.
> If OpenPower wants to go down a path more similar to RiscV here and
> support small(er) implementations, it's necessary to stop having the
> toolchain engineers push for only supporting the latest/greatest IBM
> server CPUs :-)
i can understand why they would want to advocate that :)
unfortunately, as you point out, it excludes "simpler" entrants, and,
worse, excludes entrants to markets that *POWER9 is never going to be
able to enter anyway* due to its massive size and huge power
requirements.
however with the above scheme, recently introduced somewhere in... the
past 18+ months(?) it is no longer necessary to fight over the space.
of course, JIT-compilation by using LLVM-IR *also* solves this problem
nicely. however, LLVM is not the default, de-facto and sole exclusive
compiler used in the world.
> The Microwatt core is now starting to boot Linux as well (not merged
> yet)
we saw the ppcdev patches. nice work :)
> but at the moment this requires some kernel hacks to work around
> the above, such as plumbing in FPU emulation, and I know Paul has
> issues generating a usable userspace...
the powerpc gem5 experiment already has one pre-compiled (an
initramfs) with a "hello world" buildroot of some kind (busybox). and
associated modifications to skiboot?
https://github.com/power-gem5/gem5
[branch "gem5-experimental"]
and the other support repos are at
https://github.com/power-gem5/
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] more compatible alternative to BE instructions on LE processor
From: Luke Kenneth Casson Leighton @ 2020-05-13 8:17 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4xp7+4qWk1Frg4mW+ukuLPBs0=2wCB=ZCz4=pWeV46Gw@mail.gmail.com>
On Wed, May 13, 2020 at 3:57 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
> PC value -> memory address
> 0x1000 -> 0x1003
> 0x1001 -> 0x1002
> 0x1002 -> 0x1001
> 0x1003 -> 0x1000
NNxx -> NN(3-xx)
> Since all currently existing Power instructions are a multiple of 32 bits,
> this wouldn't change how they are decoded or executed, however, would
> change how new 16 or 48-bit instructions are laid out.
>
> If the processor is switched to BE mode (for both instructions and data),
> this address reordering would be disabled, since BE mode already has the
> opcode byte as the first byte anyway.
>
> (PDP endian resurrected -- sort of)
:)
ok it's effectively "BE instruction order" as separate from "BE data
order". it's reordering the instruction memory area in a fixed
(non-dynamic) way.
i have a sneaking suspicion jacob that SVP-48 and C (16) will not
interact well with that. it'll need thinking through, what happens
when there are:
* two C (16) instructions in sequence starting on a 32-bit boundary
* one C (16) instruction followed by a SVP-48, the C (16-bit) starting
on a 32-bit boundary
* a SVP-48 (starting on a 32-bit boundary) followed by a C (16-bit)
* two SVP-48 instructions (starting on a 32-bit boundary)
also necessary to consider how to ensure that "padding" back to 32-bit
boundaries is not misinterpreted as garbage instructions, usually this
by having a 16-bit "NOP" (C) encoding
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] more compatible alternative to BE instructions on LE processor
From: Luke Kenneth Casson Leighton @ 2020-05-13 8:09 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200513092953.f9475239874f2b1ff1f29fd3@gmx.com>
On Wed, May 13, 2020 at 7:29 AM Lauri Kasanen <cand@gmx.com> wrote:
> The PowerISA 3.1 doc adds a 32-bit prefix (page 46 of the pdf (reader),
> page 22 of the official naming). I didn't go into details, but for such
> plans it'd be good to take into account.
ok that entire section covers a new (extended, 64-bit) instruction
format, including new extended immediates, vector-masks and so on.
it uses major opcode 0b0000001 to do so.
however unlike what we propose (and, crucially, propose to put behind
a mode-switch bit):
* the scheme critically depends on the instructions being chunked into
32-bit sections
* 48-bit and 16-bit instruction encodings are impossible
* we need far more bits (11 bits for C, 11 bits for SVP P48 and 27
bits for SVP P64) than can fit after *one* major opcode.
16 (prefix) minus 6 (major opcode) is 10. that is not enough to fit
11 bits of SVP P48.
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] more compatible alternative to BE instructions on LE processor
From: Lauri Kasanen @ 2020-05-13 6:29 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAC2bXD4xp7+4qWk1Frg4mW+ukuLPBs0=2wCB=ZCz4=pWeV46Gw@mail.gmail.com>
On Tue, 12 May 2020 19:56:45 -0700
Jacob Lifshay <programmerjake@gmail.com> wrote:
> Since having the instruction stream be BE is not directly compatible with
> existing LE instructions since calling between them requires a mode switch
> to switch endian, I propose a different solution that doesn't require any
> mode switch, is compatible with LE instructions, and allows supporting
> instructions that are any size, though will probably be limited to
> multiples of 16 bits.
The PowerISA 3.1 doc adds a 32-bit prefix (page 46 of the pdf (reader),
page 22 of the official naming). I didn't go into details, but for such
plans it'd be good to take into account.
- 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
* [libre-riscv-dev] more compatible alternative to BE instructions on LE processor
From: Jacob Lifshay @ 2020-05-13 2:56 UTC (permalink / raw)
To: Libre-RISCV General Development
Since having the instruction stream be BE is not directly compatible with
existing LE instructions since calling between them requires a mode switch
to switch endian, I propose a different solution that doesn't require any
mode switch, is compatible with LE instructions, and allows supporting
instructions that are any size, though will probably be limited to
multiples of 16 bits.
My idea is to switch the logical order that instructions are decoded such
that decoding 32-bit LE words starts with the most-significant byte which
contains the opcode, instead of the least-significant byte.
PC would effectively be split into two fields, where the top N-2 bits are
the address like usual, but the bottom 2 bits instead address memory in
reversed order:
PC value -> memory address
0x1000 -> 0x1003
0x1001 -> 0x1002
0x1002 -> 0x1001
0x1003 -> 0x1000
0x1004 -> 0x1007
0x1005 -> 0x1006
0x1006 -> 0x1005
0x1007 -> 0x1004
0x1008 -> 0x100B
0x1009 -> 0x100A
0x100A -> 0x1009
0x100B -> 0x1008
0x100C -> 0x100F
0x100D -> 0x100E
0x100E -> 0x100D
0x100F -> 0x100C
0x1010 -> 0x1013
Since all currently existing Power instructions are a multiple of 32 bits,
this wouldn't change how they are decoded or executed, however, would
change how new 16 or 48-bit instructions are laid out.
If the processor is switched to BE mode (for both instructions and data),
this address reordering would be disabled, since BE mode already has the
opcode byte as the first byte anyway.
(PDP endian resurrected -- sort of)
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-13 2:27 UTC (permalink / raw)
To: openpower-hdl-cores; +Cc: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6LVtrMh7RT=11ZVypujcJRaMokG7XuBwF87veBiMMDLQ@mail.gmail.com>
On Tue, May 12, 2020, 00:24 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:
>
It turns out that I spoke too soon about what exactly Libre-SOC's CPU will
support, I apologise.
With that said, I still think it would be useful for OpenPower to support
LE-only processors without the additional requirements imposed by the Linux
and AIX compatibility 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
* [libre-riscv-dev] [Bug 291] HDL Workflow and Coriolis2 chroot automated setup scripts
From: bugzilla-daemon @ 2020-05-13 2:00 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=291
--- Comment #7 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #6)
> ok so there's nothing in there which says "picking a hard-coded git tag
> number"
> so i suspect that it's as simple as jean-paul made a commit recently which
> broke something.
Ah, I'm realizing now that I really should have been using a hard-coded git tag
number. Can you share your known-working git tag number for coriolis2 so I can
continue working on the script tomorrow?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] [OpenPOWER-HDL-Cores] little-endian only power cores and spec compliance
From: Hugh Blemings @ 2020-05-13 1:22 UTC (permalink / raw)
To: Jacob Lifshay, openpower-hdl-cores; +Cc: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6LVtrMh7RT=11ZVypujcJRaMokG7XuBwF87veBiMMDLQ@mail.gmail.com>
Hi All,
I'm barely qualified to add much more than $0.20 to this thread, but
will give it a whirl...
I've not had a chance to dig into the v3.1 spec as yet but can offer the
observation that the intent (as demonstrated in the Microwatt
implementation for example) was that the simpler/simplest
implementations would be LE with BE optional. SIMD also optional in
these as well.
So if the docs don't represent this we'll need to take a closer look :)
We're getting more of the key folk from our member companies (mostly
IBM) into the loop through this list but as Luke rightly pointed out
over on libre-riscv-dev they're a busy crew at the moment with a new
chip due out soon :)
That said I imagine someone will chime in soon who -actually- knows this
stuff!
Cheers,
Hugh
(Speaking for myself only in this case, though I believe wearing my ED
hat I'd be saying much the same :)
On 12/5/20 5:24 pm, Jacob Lifshay 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
>
> _______________________________________________
> 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
* [libre-riscv-dev] [Bug 291] HDL Workflow and Coriolis2 chroot automated setup scripts
From: bugzilla-daemon @ 2020-05-13 1:19 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=291
--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ok so there's nothing in there which says "picking a hard-coded git tag number"
so i suspect that it's as simple as jean-paul made a commit recently which
broke something.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-13 1:05 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #49 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ok. i think we need to look more closely at decoder2.py compared to
decode2.vhdl
https://github.com/antonblanchard/microwatt/blob/master/decode2.vhdl
i'm not seeing any reason though why the operands should need "swapping over":
why RC is needing to go into a.
the alignment should definitively be:
* reg3_data into c
* reg2_data (or imm) into b
* reg1_data into a
ah hang on...
https://github.com/antonblanchard/microwatt/blob/master/execute1.vhdl
see lines 183-184:
logical_0: entity work.logical
port map (
rs => c_in,
rb => b_in,
and here, lines 166-169:
rotator_0: entity work.rotator
port map (
rs => c_in,
ra => a_in,
that's it. that's what's going on. the different pipelines have *different*
register map/alignment, *depending on function-group*.
the *adder* takes A as A, and B as B. rotator crosses over, logical crosses
over.
what a mess.
ok what i suggest, then, here is: split out Logical ALU operations as well.
the ADD ALU will deal with OP_ADD and OP_CMP. i don't yet know if we should
allow the ADD ALU to change the PC (handle OP_TRAP), i'm inclined to suggest
that that one be handled in the Branch Computation Unit.
by splitting out:
* ADD/CMP into one pipeline
* Logical into another
* Rotator into another
basically on the face of it we need to use the FunctionOp to determine the
re-routing of the operands.
but... it looks like you've discovered a correlation, where if reg_data3 is
available it can go *first* (into out.a), otherwise if reg_data1 is available,
*that* goes first (into out.a)
however B i think definitely goes into out.b, or the immediate definitely
goes into out.b, and i think we'll find that there is no "immediate" form
with a register B.
fields.txt
RB (16:20)
Field used to specify a GPR to be used as a
source.
Formats: A, M, MDS, VA, X, XO
ok so strictly speaking MDS-Form has immediates in it, however if you look
at what anton's done, in minor-opcode table 30:
https://libre-soc.org/openpower/isatables/
he's marked rdlcr as *not* reading the immediate (bit 21, mb/me) as an
immediate, but instead operand2 is marked as "RB". which explains why
we have to decode insn to get at dec2.mb and dec2.me.
so i think we're good to go with reg2_data (or imm_data) always going into
out.b
and perhaps to have an assert that checks, for these 2-operand pipelines,
that reg3_ok and reg1_ok can never be set simultaneously, and to always put
reg3_data or reg1_data into out.a. perhaps even as an OR rather than a Mux.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 291] HDL Workflow and Coriolis2 chroot automated setup scripts
From: bugzilla-daemon @ 2020-05-13 0:16 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=291
--- Comment #5 from Cole Poirier <colepoirier@gmail.com> ---
Note, theres a very high probability that I am making very silly bash scripting
mistakes because I'm new to this. So any help and corrections are greatly
appreciated :)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 291] HDL Workflow and Coriolis2 chroot automated setup scripts
From: bugzilla-daemon @ 2020-05-13 0:15 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=291
--- Comment #4 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #3)
> (In reply to Cole Poirier from comment #2)
> ok so this "per se" is of no help as without knowing "which script"
> there is no way to know what it is doing. until we know where that
> script is, and can examine it (and run it) there's not a lot that can
> be done.
Oops, sorry, I forgot to link the script's git repo. This error occurs when
running the script 'coriolis2-chroot' after running the script
'install-apt-reqs' from this repo
https://git.libre-soc.org/?p=dev-env-setup.git;a=summary.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 291] HDL Workflow and Coriolis2 chroot automated setup scripts
From: bugzilla-daemon @ 2020-05-13 0:09 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-291-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=291
--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #2)
> Luke, I was able to get the script to work to the point of correctly
> installing and configuring the coriolis chroot such that it would open the
> coriolis window diplaying the chicken, which when clicked on a few times
> displayed the coriolis layout window as on the HDL workflow wiki.
> Unfortunately my script no longer reaches this point of successful
> completion, and I am now consistently getting stuck at this error:
ok so this "per se" is of no help as without knowing "which script"
there is no way to know what it is doing. until we know where that
script is, and can examine it (and run it) there's not a lot that can
be done.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-05-12 22:03 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=307
--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://bugs.libre-soc.org/rest.cgi
works (and is returning a "readthedocs" comment)
however https://bugs.libre-soc.org/rest/{anything}
is not working.
this indicates some sort of error with the nginx location-redirect section
in sites-available/bugzilla
location /rest {
rewrite ^/rest/(.*)$ rest.cgi/$1 last;
}
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-12 22:02 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #48 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #47)
> ok let's put the forms side-by-side, from fields.txt
>
> #1.6.4 D-FORM
> | OPCD | RT | RA| D |
>
> # V3.0B 1.6.6 DX-FORM
> | OPCD| RT| d1| d0| XO|d2
>
> # 1.6.16 XO-FORM
> | OPCD | RT| RA| RB |OE | XO |Rc |
>
>
> and the shift ones are:
>
> # 1.6.18 M-FORM
> | OPCD | RS | RA | RB | MB | ME |Rc|
>
> # 1.6.19 MD-FORM
> | OPCD | RS | RA | sh | mb |XO|sh|Rc|
>
> # 1.6.7 X-FORM
> | OPCD | RT | RA | /// | XO | / |
>
>
> so... well... i'm not actually seeing any 3-operand-input forms, there.
> they're all 2-operand or 1-operand-plus-immediate.
>
> note: 3-operand *input* not 3-operand *total including output operand*.
>
> so i'm now wondering what on earth is going on, because we shouldn't need
> to be reading reg3 at all.
>
> any clues?
We only need two register operands and an immediate for all ALU instructions.
The only ones with 3 register operands are store indexed instructions
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-05-12 21:58 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=307
--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
done, alain. however it's not something you enable, it's always there
(rest.cgi)
https://bugzilla.readthedocs.io/en/latest/installing/nginx.html
this config is *different* from the one in /etc/nginx/sites-enabled/bugzilla
i think it might be that the script is always forced to be index.cgi
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-12 21:33 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=305
--- Comment #47 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ok let's put the forms side-by-side, from fields.txt
#1.6.4 D-FORM
| OPCD | RT | RA| D |
# V3.0B 1.6.6 DX-FORM
| OPCD| RT| d1| d0| XO|d2
# 1.6.16 XO-FORM
| OPCD | RT| RA| RB |OE | XO |Rc |
and the shift ones are:
# 1.6.18 M-FORM
| OPCD | RS | RA | RB | MB | ME |Rc|
# 1.6.19 MD-FORM
| OPCD | RS | RA | sh | mb |XO|sh|Rc|
# 1.6.7 X-FORM
| OPCD | RT | RA | /// | XO | / |
so... well... i'm not actually seeing any 3-operand-input forms, there.
they're all 2-operand or 1-operand-plus-immediate.
note: 3-operand *input* not 3-operand *total including output operand*.
so i'm now wondering what on earth is going on, because we shouldn't need
to be reading reg3 at all.
any clues?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-05-12 20:56 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=307
--- Comment #3 from Alain D D Williams <addw@phcomp.co.uk> ---
For this to work bugzilla needs to have the REST API option enabled.
Please can you, Luke, enable this or give me appropriate admin rights so that I
can do this.
Thanks
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
page: next prev latest
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git