Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 265] new server from raptorcs needs set up with build/test rnvironment
From: bugzilla-daemon @ 2020-03-22 23:36 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-265-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=265

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
veera would you be happy to log in and manage this server? if so please send me
an ssh pub key.

we have to agree not to do anything illegal with this server, we are guests on
raptor engineering's network.

it will need fail2ban configuring, i have it installed already.  whitelisting
of the VPN 10.6.0.0/16, changing ssh to recognise port 922, enabling ssh
fail2ban and also enanling recidive.

also i think installing ssmtpd so that it can at least send email out, use
10.6.0.1 as the SMTP relay.

the VPN also has access to libre-riscv.org, to the build server that jacob set
up, and to my laptop.  so we need to be careful.

-- 
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 264] ISA switch needs to be a privileged operation
From: bugzilla-daemon @ 2020-03-23  0:01 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-264-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=264

--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
What could work is to have new ELF flags to indicate which ABI variants a
particular executable, object (.o file), or dynamic library requires. The
dynamic linker and standard linker would make sure that the files are
compatible.

This is kinda similar to what RISC-V is doing:
see e_flags field in
https://github.com/riscv/riscv-elf-psabi-doc/blob/master/riscv-elf.md

Defining which ISAs can link together and if inlining can occur should be the
responsibility of the toolchain and dynamic linker, rather than relying on ISA
switching being a privileged operation.

What I think should happen is that the ABI requires functions to have the ISA
set to the proper value when calling a function, and if it isn't set properly,
then that's a bug in the calling function. Likewise for returning.

This is similar to how the thread pointer or stack pointer must be set properly
before calling a function. If it isn't set properly, than it's undefined
behavior and the code is allowed to do anything (though will probably crash).

I had been planning on the actual RISC-V/Power ISA switching operation happen
as part of switching between user and kernel modes, where all the RISC-V state
is accessible in either standard Power registers or SFRs.

For switching between standard Power and Power+SVPrefix, I was hoping that all
of SVPrefix would just fit in unallocated portions of the Power ISA.

For handling 16-bit instructions, would it work to instead define a pair of
16-bit instructions as a 32-bit instruction with the standard opcode field in
the correct position for decoding to allow mixing with arbitrary >= 32-bit
Power ISA operations?

For example, if there were the following two 16-bit instructions:

add 3, 3, 4
addi 3, 3, 12

They would both be packed into
a single 32-bit instruction (denoted using braces):

{
    add 3, 3, 4
    addi 3, 3, 12
}

We wouldn't need to support all instructions, just the most common ones, and
it's perfectly fine to not support particular pairs (such as if the second one
can trap and the first one can't just be run again -- allowing us to not need
to worry about what happens if we trap in the middle of a pair).

-- 
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] [Bug 184] new mailing lists proposal for libre-soc.org
From: Cole Poirier @ 2020-03-23  0:01 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: libre-riscv-dev
In-Reply-To: <bug-184-13-ZvOgwzSRqn@http.bugs.libre-riscv.org/>

On Mar 21 2020, at 4:24 pm, bugzilla-daemon@libre-riscv.org wrote:
> http://bugs.libre-riscv.org/show_bug.cgi?id=184
> --- Comment #6 from vklr@vkten.in <vklr@vkten.in> ---
> (In reply to Jacob Lifshay from comment #4)
>> (In reply to Luke Kenneth Casson Leighton from comment #0)
>> > These should be *new* lists on libre-soc.org (retire libre-riscv-dev)
>> > 
>> > 1) Libre-SOC-Dev, for hardware and software development (productive)
>> > discussion
>> > 2) Libre-SOC-Org, for discussion about related to the organization
>> > itself, such as funding, investing, finances, domain change, website
>> > design, members, ethics, business, administration, you get my point
>> > 3) Libre-SOC-Misc, for everything else (the non serious stuff that I
>> > can safely ignore unlike the first two which should have important
>> > stuff only)
>> > 4) Bugtracker separate list, readonly announce only, and replyto
>> set to
>> > bugzilla ready for when/if incoming bugzilla is ever set up
>> 
>> I think the above proposal is a good idea. When we finally shut-down
>> libre-riscv-dev, I think we should send out a single notification
>> email to
>> everyone who's subscribed even if they have mail delivery turned off. We
>> should also announce our name & domain change on crowdsupply.
>> 
>> Is everyone ok with the above plan?
> 
> I am also fine with it.

I endorse this plan.

Cole

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 265] new server from raptorcs needs set up with build/test environment
From: bugzilla-daemon @ 2020-03-23  0:07 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-265-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=265

--- Comment #2 from Jacob Lifshay <programmerjake@gmail.com> ---
updated comment #0 to actual core count (18 cores * 4 threads/core == 72
threads)

-- 
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 264] ISA switch needs to be a privileged operation
From: bugzilla-daemon @ 2020-03-23  0:26 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-264-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=264

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #1)

i'll mention the elf flags idea. it may help at some point if you could explain
it to Tim of RaptorCS.


> For switching between standard Power and Power+SVPrefix, I was hoping that
> all of SVPrefix would just fit in unallocated portions of the Power ISA.

just. barely, yes. by using up 2 major opcodes per prefix.  2 for 48, 2 for 64
bit.

> 
> For handling 16-bit instructions, would it work to instead define a pair of
> 16-bit instructions as a 32-bit instruction with the standard opcode field
> in the correct position for decoding to allow mixing with arbitrary >=
> 32-bit Power ISA operations?

only on BE systems because only then does the decoder see the major opcode in
the 1st byte.

ok ok if we wanted to make ourselves feel like jamming our fingers down our
throat and hurling, we could go:

"ok mr 32 bit LE system, we have reserved 2 major opcodes for C, and in byte 3
we have a C instruction.  however there are 2 bytes left, 0 and 1, which is now
the SECOND C instruction, to be executed AFTER the one in bytes 2 and 3".

if those 2 bytes are all zero that is a C NOP

so this would mean running instructions in a weird 2 steps forward, 1 step back
fashion, but would at least be LE compatible.

blech.

SVPrefix32 (C with a SVP added) is also doable btw.  that just takes up 32
bits, straight.

> 
> For example, if there were the following two 16-bit instructions:
> 
> add 3, 3, 4
> addi 3, 3, 12
> 
> They would both be packed into
> a single 32-bit instruction (denoted using braces):
> 
> {
>     add 3, 3, 4
>     addi 3, 3, 12
> }
> 
> We wouldn't need to support all instructions, just the most common ones, 

yes agreed.  i'd like to ask rogier bruisse to help design it, he is extremely
good.



>and
> it's perfectly fine to not support particular pairs (such as if the second
> one can trap and the first one can't just be run again -- allowing us to not
> need to worry about what happens if we trap in the middle of a pair).

hmm... we might have to. or, another way (indicating the extent of the
awfulness), a bit in a SPR which is contextswitched tells us which of the 2 C
instructions are being executed.

or... *shudder* we have the PC advance first by 4 bytes, then jump BACK 2
bytes, then jump forward to... no, my brain just melted thinking about that
one.

-- 
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 264] ISA switch needs to be a privileged operation
From: bugzilla-daemon @ 2020-03-23  1:12 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-264-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=264

--- Comment #3 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #2)
> (In reply to Jacob Lifshay from comment #1)
> > it's perfectly fine to not support particular pairs (such as if the second
> > one can trap and the first one can't just be run again -- allowing us to not
> > need to worry about what happens if we trap in the middle of a pair).
> 
> hmm... we might have to. or, another way (indicating the extent of the
> awfulness), a bit in a SPR which is contextswitched tells us which of the 2
> C instructions are being executed.

That could work, but it will require additional modification to Linux as well
as userspace for things like changing the on-stack structures for asynchronous
signals.

> 
> or... *shudder* we have the PC advance first by 4 bytes, then jump BACK 2
> bytes, then jump forward to...

That would be very messy and won't work if any instructions don't start on a
4-byte boundary (can happen with 48-bit instructions), since that would be
ambiguous between a misaligned 4-byte instruction and the second half of a
compressed instruction pair.

> ... no, my brain just melted thinking about that
> one.

Let's all join the melted brain club!!! :P

-- 
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 258] Finish implementing support for Power in simple-soft-float
From: bugzilla-daemon @ 2020-03-23  1:24 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-258-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=258

--- Comment #2 from Jacob Lifshay <programmerjake@gmail.com> ---
Finished updating for latest version of PyO3 and algebraics

-- 
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 265] new server from raptorcs needs set up with build/test environment
From: bugzilla-daemon @ 2020-03-23  1:53 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-265-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=265

--- Comment #3 from vklr@vkten.in <vklr@vkten.in> ---
(In reply to Luke Kenneth Casson Leighton from comment #1)
> veera would you be happy to log in and manage this server? if so please send
> me an ssh pub key.
> 
> we have to agree not to do anything illegal with this server, we are guests
> on raptor engineering's network.
> 
> it will need fail2ban configuring, i have it installed already. 
> whitelisting of the VPN 10.6.0.0/16, changing ssh to recognise port 922,
> enabling ssh fail2ban and also enabling recidive.
> 
> also i think installing ssmtpd so that it can at least send email out, use
> 10.6.0.1 as the SMTP relay.
> 
> the VPN also has access to libre-riscv.org, to the build server that jacob
> set up, and to my laptop.  so we need to be careful.

Luke, I will try. How quickly it has to be done? How much time I would have to
spend? I am sending you my ssh pub key by mail.

-- 
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 264] ISA switch needs to be a privileged operation
From: bugzilla-daemon @ 2020-03-23  7:54 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-264-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=264

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
so, um... it's just easier to use BE instruction format and "cheat" a little,
because the MSBs of the 32-bit instruction, containing the major opcode,
end up in the 1st byte:

byte 0:
31 30 29 28 27 26 25 24
| major opcode  | rest-of-32-bit-instruction...

byte 1:
23 22 21 20 19 18 17 16
more of 32-bit-instruction

see https://libre-riscv.org/openpower/:

if we take over 2 opcodes for each of C, SVP P48, SVP P64 and VBLOCK
then we have a workaround.  SVP P32 can potentially be "paged".

it's a bit of a pain that there's so few bits, due to the way that POWER
was never designed for this type of thing originally.

the way VLE works is, you actually have an entire new memory page which
is allocated a "format".  that means that mixing 16-bit VLE and 32-bit
VLE is basically impossible, and you have to jump between two completely
different memory pages repeatedly just to get access to regular
instructions which are not available in VLE 16-bit.

-- 
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 265] new server from raptorcs needs set up with build/test environment
From: bugzilla-daemon @ 2020-03-23  8:14 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-265-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=265

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to vklr@vkten.in from comment #3)

> > the VPN also has access to libre-riscv.org, to the build server that jacob
> > set up, and to my laptop.  so we need to be careful.
> 
> Luke, I will try. 

appreciated.

> How quickly it has to be done? How much time I would have
> to
> spend? 

it's not a major blocker at the moment.

> I am sending you my ssh pub key by mail.

appreciated.  got it.  what's your preferred username?

-- 
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 264] ISA switch needs to be a privileged operation
From: bugzilla-daemon @ 2020-03-23  8:30 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-264-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=264

--- Comment #5 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #4)
> so, um... it's just easier to use BE instruction format and "cheat" a
> little, because the MSBs of the 32-bit instruction, containing the major
> opcode,
> end up in the 1st byte:
> 
> byte 0:
> 31 30 29 28 27 26 25 24
> | major opcode  | rest-of-32-bit-instruction...
> 
> byte 1:
> 23 22 21 20 19 18 17 16
> more of 32-bit-instruction
> 
> see https://libre-riscv.org/openpower/:
> 
> if we take over 2 opcodes for each of C, SVP P48, SVP P64 and VBLOCK
> then we have a workaround.

If we use the same 2 C opcodes for compressed pairs, then we can end up with
13.5 bits available per instruction, rather than just 11, which allows us to
define about 5.656 (!) times as many compressed instructions.

13.5 = (32 - 6 + 1) / 2
11 = 16 - 6 + 1
5.656... = 2 ^ (13.5 - 11)

>  SVP P32 can potentially be "paged".
> 
> it's a bit of a pain that there's so few bits, due to the way that POWER
> was never designed for this type of thing originally.
> 
> the way VLE works is, you actually have an entire new memory page which
> is allocated a "format".  that means that mixing 16-bit VLE and 32-bit
> VLE is basically impossible, and you have to jump between two completely
> different memory pages repeatedly just to get access to regular
> instructions which are not available in VLE 16-bit.

VLE requiring separate pages seems like a total mess that we should not
emulate.

-- 
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 264] ISA switch needs to be a privileged operation
From: bugzilla-daemon @ 2020-03-23  8:37 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-264-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=264

--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #5)

> If we use the same 2 C opcodes for compressed pairs, then we can end up with
> 13.5 bits available per instruction, rather than just 11, which allows us to
> define about 5.656 (!) times as many compressed instructions.
> 
> 13.5 = (32 - 6 + 1) / 2
> 11 = 16 - 6 + 1
> 5.656... = 2 ^ (13.5 - 11)

other ideas along this theme include saying, in that initial 32-bit space, is
to specify how many of the next instructions are to be encoded as C.

i'd recommend to reserve the option to do this, as it involves storing state
(the countdown timer) whereas just having 2 C opcodes as pairs is dead simple,
as long as you accept that the PC encodes the state information about the fact
that if the PC is on a 2-byte boundary you're in the middle of the pair.

this allows the PC to store the state if there is a trap.

> VLE requiring separate pages seems like a total mess that we should not
> emulate.

i only looked at it briefly so we can't write it off entirely, however... yeah
:)

-- 
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 264] ISA switch needs to be a privileged operation
From: bugzilla-daemon @ 2020-03-23  8:47 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-264-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=264

cand@gmx.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cand@gmx.com

--- Comment #7 from cand@gmx.com ---
Storing state sounds dangerous, consider someone jumping into the middle of
compressed instrs.

-- 
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 264] ISA switch needs to be a privileged operation
From: bugzilla-daemon @ 2020-03-23  8:54 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-264-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=264

--- Comment #8 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #6)
> (In reply to Jacob Lifshay from comment #5)
> 
> > If we use the same 2 C opcodes for compressed pairs, then we can end up with
> > 13.5 bits available per instruction, rather than just 11, which allows us to
> > define about 5.656 (!) times as many compressed instructions.
> > 
> > 13.5 = (32 - 6 + 1) / 2
> > 11 = 16 - 6 + 1
> > 5.656... = 2 ^ (13.5 - 11)
> 
> other ideas along this theme include saying, in that initial 32-bit space,
> is to specify how many of the next instructions are to be encoded as C.
> 
> i'd recommend to reserve the option to do this, as it involves storing state
> (the countdown timer) whereas just having 2 C opcodes as pairs is dead
> simple, as long as you accept that the PC encodes the state information
> about the fact that if the PC is on a 2-byte boundary you're in the middle
> of the pair.
> 
> this allows the PC to store the state if there is a trap.

Except, like I mentioned before, using the PC to store that info makes it
ambiguous between executing the second instruction in a pair and executing a
non-paired instruction that happens to start at a 2-byte boundary because there
was a preceding 48-bit instruction. So, we'll either have to not have any
48-bit instructions, not trap in the middle of a pair, or not have paired
instructions.

Switching instruction memory to always be in BE mode is not a good solution
since that is not compatible with standard Power code that doesn't know about
the endian switch.

-- 
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 264] ISA switch needs to be a privileged operation
From: bugzilla-daemon @ 2020-03-23  8:57 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-264-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=264

--- Comment #9 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to cand from comment #7)
> Storing state sounds dangerous, consider someone jumping into the middle of
> compressed instrs.

Just as dangerous as someone jumping into the middle of an x86 instruction.

It's not at all a problem for compilers, since they can arrange for all branch
targets to not be in the middle of compressed 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 265] new server from raptorcs needs set up with build/test environment
From: bugzilla-daemon @ 2020-03-23  9:12 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-265-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=265

Tobias Platen <hacks2019@platen-software.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hacks2019@platen-software.d
                   |                            |e

--- Comment #5 from Tobias Platen <hacks2019@platen-software.de> ---
I have a Talos II at home and I got coriolis2 running there. coriolis2 still
assumes that the architecture is i386 on POWER9 systems.

-- 
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 258] Finish implementing support for Power in simple-soft-float
From: bugzilla-daemon @ 2020-03-23  9:22 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-258-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=258

--- Comment #3 from Jacob Lifshay <programmerjake@gmail.com> ---
So you know, simple-soft-float's StatusFlags is getting lots of new flags and
some of the existing flags will become aliases for groups of flags, where
writing will write to all flags in the group and reading will get the logical
OR of all flags in the group.

Some of the new flags won't be persistent -- they will be overwritten by every
operation -- unlike the standard flags which all stay at 1 (unless explicitly
cleared).

-- 
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 258] Finish implementing support for Power in simple-soft-float
From: bugzilla-daemon @ 2020-03-23 10:00 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-258-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=258

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lkcl@lkcl.net

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #3)
> So you know, simple-soft-float's StatusFlags is getting lots of new flags
> and some of the existing flags will become aliases for groups of flags,
> where writing will write to all flags in the group and reading will get the
> logical OR of all flags in the group.
> 
> Some of the new flags won't be persistent -- they will be overwritten by
> every operation -- unlike the standard flags which all stay at 1 (unless
> explicitly cleared).

ok appreciated.  the next step will be writing as close a drop-in replacement
for sfpy as we can get.  once sfpy is replaced as a dependency we can add new
flags etc.  if those are in one place (a test helper routine / class) that
minimises disruption and makes it easy to add features to ssf.

-- 
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-03-23 10:21 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=216

--- Comment #14 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ok i have a pair of classes now:

* LDSTSplitter - this is designed to connect directly to LDSTCompUnit
* TwinPartialAddrBitmap - designed to be connected to LDSTSplitter

the idea is:

* misaligned LDs/STs that cross cache-line boundaries get "split" into
  a *pair* of LD/ST addresses plus corresponding "byte-map".

* these "byte-maps" are based on the bottom LSBs of the address *and*
  the length (byte-LD = len=1 ==> 0b1, halfword-LD = len=2 ==> 0b11
  which is then *SHIFTED UP* by the bottom LSBs

* any byte-map that goes over a cache line results in the SECOND
  of the two addresses "activating" from the LDSTSplitter

* key thing to note: the bytemaps *already encode* the position in the
  L1 cache, and can be used directly as "byte read/write-enable" lines on
  the underlying Memory.  no further shifting or offsetting is required
  at the Cache: the bytemaps can be wired *directly* into nmigen Memory
  as byte-enables.

* TwinPartialAddrBitmap takes *pairs* of addresses (plus length bytemaps)
  and identifies which addresses are clashing.  there are extra addresses
  included (actually, excluded) because only the LSBs are checked: this
  is fine.


important to note: LDSTSplitter has clock-synchronous signalling with
combinatorial bypass on it.  in other words, if the downstream LDs/STs
signal that they are ready immediately, LDSTSplitter will *also* respond
immediately (in that same clock cycle).  however if one of the LDs/STs
is not ready yet (cache miss for example) then LDSTSplitter will take
note of that and wait until the downstream sources set their "valid"
flag(s).

errors are simply merged.  this is still TODO properly.

-- 
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 264] ISA switch needs to be a privileged operation
From: bugzilla-daemon @ 2020-03-23 10:24 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-264-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=264

--- Comment #10 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to cand from comment #7)
> Storing state sounds dangerous, consider someone jumping into the middle of
> compressed instrs.

this is precisely what a context-switch has to be able to do, because a trap
may occur in the middle of a pair of C instrs.

i very carefully designed VBLOCK around precisely this principle, involving
state information that is required to be context-switched.

and yes, if an end-user writes code that jumps into the middle of a block
without respecting the specification, they're on their own.

-- 
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 264] ISA switch needs to be a privileged operation
From: bugzilla-daemon @ 2020-03-23 10:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-264-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=264

--- Comment #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #8)
> (In reply to Luke Kenneth Casson Leighton from comment #6)
> > (In reply to Jacob Lifshay from comment #5)
> > 
> > > If we use the same 2 C opcodes for compressed pairs, then we can end up with
> > > 13.5 bits available per instruction, rather than just 11, which allows us to
> > > define about 5.656 (!) times as many compressed instructions.
> > > 
> > > 13.5 = (32 - 6 + 1) / 2
> > > 11 = 16 - 6 + 1
> > > 5.656... = 2 ^ (13.5 - 11)
> > 
> > other ideas along this theme include saying, in that initial 32-bit space,
> > is to specify how many of the next instructions are to be encoded as C.
> > 
> > i'd recommend to reserve the option to do this, as it involves storing state
> > (the countdown timer) whereas just having 2 C opcodes as pairs is dead
> > simple, as long as you accept that the PC encodes the state information
> > about the fact that if the PC is on a 2-byte boundary you're in the middle
> > of the pair.
> > 
> > this allows the PC to store the state if there is a trap.
> 
> Except, like I mentioned before, using the PC to store that info makes it
> ambiguous between executing the second instruction in a pair and executing a
> non-paired instruction that happens to start at a 2-byte boundary because
> there was a preceding 48-bit instruction.

*click* yes got it now.  ok so a bit (a "length of number of C instructions to
be decoded" where that length happens to be 1, is a solution there.

> So, we'll either have to not have
> any 48-bit instructions, not trap in the middle of a pair, or not have
> paired instructions.

storing an extra bit (or bits) in a SPR - particularly one that already has to
be saved - isn't so onerous.

> Switching instruction memory to always be in BE mode is not a good solution
> since that is not compatible with standard Power code that doesn't know
> about the endian switch.

well, luckily, if we accept the C-pair idea has to have at least a length of "1
bit" and that is stored in a context-switched SPR, it's ok.

later the length can be extended to say 3 or 4 bits.  or, heck, we might as
well just allow 3-4 bits anyway.

-- 
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 265] new server from raptorcs needs set up with build/test environment
From: bugzilla-daemon @ 2020-03-23 12:31 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-265-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=265

--- Comment #6 from vklr@vkten.in <vklr@vkten.in> ---
(In reply to Luke Kenneth Casson Leighton from comment #4)
> (In reply to vklr@vkten.in from comment #3)
> 
> 
> it's not a major blocker at the moment.
> 
> > I am sending you my ssh pub key by mail.
> 
> appreciated.  got it.  what's your preferred username?

username: vklr

-- 
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 265] new server from raptorcs needs set up with build/test environment
From: bugzilla-daemon @ 2020-03-23 12:50 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-265-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=265

--- Comment #7 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to vklr@vkten.in from comment #6)

> username: vklr

ok sorted, you should now be able to ssh -p922 vklr@23.155.224.75

-- 
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] write-up and diagrams for components in the 6600 scoreboard engine
From: Luke Kenneth Casson Leighton @ 2020-03-23 16:21 UTC (permalink / raw)
  To: Libre-RISCV General Development

i discovered that last year i'd written up this page:
https://libre-riscv.org/3d_gpu/architecture/6600scoreboard/

i've updated it to include the LDSTCompUnit and others.

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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-23 20:12 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-186-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=186

--- Comment #96 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #95)

> yes.  however adding a power frontend on it as we found ain't so bad.  can
> use the same code.
> 
> if you look here you can see how basic the test simulator is
> https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/experiment/score6600.
> py;h=babce2439233f84c262c08795b873a6167197ec9;hb=HEAD#l859
> 
> adjusting that so it uses InternalOp is... er... not hard? :)

Luke, looks like you and I are doing different things...? It looks to me like
score6600 is actual hardware, not a simulator. I have basic simulator I'm
working on here
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/simulator/internalop_sim.py;h=813dd19c40e21283d000fd597074a2cb38595a8a;hb=e95b4372c5163bb6f753c92d8445d4af7f117457
- I took some of the elements from score6600 (like the register and memory
file) and modified them to get a basic simulator, which I'm testing along side
a real power machine. Were you going for something different...?

-- 
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:   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