Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-26  5:54 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 #114 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
actually, i like what you wrote a whooole lot better, michael:
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/simulator/qemu.py;h=c9b1b573dd22d3da0adb0415a0a6b8bb005c99c6;hb=4b50a170c413f47e0527c843be49babc493c684b

the only modification i needed:

set architecture powerpc:common64
target remote localhost:1234
layout asm
b *0x20000000
c

and to use debian package "gdb-multilib" which *sigh* had to come from
debian/unstable.

building cross-compilers etc. from source has always stressed me out :)

if we do that, we need a proper documented reproducible process.

how did you get powerpc64-linux-gnu-gdb?

-- 
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 266] Allow read-only git clone over https
From: bugzilla-daemon @ 2020-03-26  7:42 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-266-13@http.bugs.libre-riscv.org/>

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

vklr@vkten.in <vklr@vkten.in> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vklr@vkten.in

--- Comment #2 from vklr@vkten.in <vklr@vkten.in> ---
Yes. git protocol is insecure over untrusted network as documented in official
git-scm.org site itself.

Please use new protocol for http/https protocol and not the old dumb protocol.

-- 
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] test failure when running nmutil tests on GitLab CI
From: Jacob Lifshay @ 2020-03-26  7:46 UTC (permalink / raw)
  To: Libre-RISCV General Development

getting lots of errors like:

Traceback (most recent call last):
   File "/builds/Kazan-team/nmutil/.eggs/nose-1.3.7-py3.7.egg/nose/case.py",
line 198, in runTest
     self.test(*self.arg)
   File "/builds/Kazan-team/nmutil/src/nmutil/test/test_buf_pipe.py",
line 1227, in test0
     vcd_name="test_maskchain0.vcd")
   File "/builds/Kazan-team/nmigen/nmigen/compat/sim/__init__.py",
line 22, in run_simulation
     fragment.domains += ClockDomain("sync")
 AttributeError: 'MaskCancellablePipe' object has no attribute 'domains'

See for details:
https://salsa.debian.org/Kazan-team/nmutil/-/jobs/630414

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] Git mirroring
From: Jacob Lifshay @ 2020-03-26  7:54 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxXyyLbAVcnQebULR2-9V_AUJ7m9LQO4DWmMz6G1+yd+A@mail.gmail.com>

On Wed, Mar 25, 2020 at 10:48 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Thu, Mar 26, 2020 at 4:37 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > Stupid gmail formatting.
>
> doh. whyy do we put up with it??
>
> > fixed:
> >
> > https://salsa.debian.org/Kazan-team/ieee754fpu
> > https://salsa.debian.org/Kazan-team/soc
> > https://salsa.debian.org/Kazan-team/nmutil
>
> this means manual checkout (and instructions) don't need an extra
> argument.  while we're at it, soclayout might as well be added to
> that?

added at https://salsa.debian.org/Kazan-team/soclayout

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] nmigen upstream repo moved
From: Jacob Lifshay @ 2020-03-26  8:19 UTC (permalink / raw)
  To: Libre-RISCV General Development

nmigen appears to have moved the upstream repo to
https://github.com/nmigen/nmigen instead of
https://github.com/m-labs/nmigen

The old one is still kept somewhat up-to-date.

Do you think we should switch to using the new repo? I can do the work
to update all the docs.

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] nmigen upstream repo moved
From: Luke Kenneth Casson Leighton @ 2020-03-26 10:07 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5JhkA-Y_E6_rizbBXh1GadHwj31m+51_0J9nfS2MN1Yw@mail.gmail.com>

On Thu, Mar 26, 2020 at 8:20 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> nmigen appears to have moved the upstream repo to
> https://github.com/nmigen/nmigen instead of

urr ok.

> Do you think we should switch to using the new repo? I can do the work
> to update all the docs.

yes please.

_______________________________________________
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 266] Allow read-only git clone over https
From: bugzilla-daemon @ 2020-03-26 10:09 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-266-13@http.bugs.libre-riscv.org/>

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

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
hmm really we should be doing git tag signing and/or git commit sign-off,
with gpg keys.  relying on HTTPS in particular for security just paints
a bullseye on the server.

-- 
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] test failure when running nmutil tests on GitLab CI
From: Luke Kenneth Casson Leighton @ 2020-03-26 10:13 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5_vzhS28s+eE06jAftGaJfv4J8nxrUW_zQaF_vC0YCRw@mail.gmail.com>

On Thu, Mar 26, 2020 at 7:46 AM Jacob Lifshay <programmerjake@gmail.com> wrote:

>      fragment.domains += ClockDomain("sync")
>  AttributeError: 'MaskCancellablePipe' object has no attribute 'domains'

ah frickin 'ell.  you'll need to use a less up-to-date

there are dozens of simulations that need "conversion".

my feeling is: screw that, we write our own function which emulates
the old behaviour of run_simulation(), of 6 months ago.

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] test failure when running nmutil tests on GitLab CI
From: Tobias Platen @ 2020-03-26 10:51 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDxBx__2mud1uRddWjqci-wZXiK1hMYARbL0qyyF8z4Suw@mail.gmail.com>

I had a similar error when I ugraded nmigen some months ago. I still don't remember how I solved that.

t.

On Thu, 26 Mar 2020 10:13:05 +0000
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

> On Thu, Mar 26, 2020 at 7:46 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
> 
> >      fragment.domains += ClockDomain("sync")
> >  AttributeError: 'MaskCancellablePipe' object has no attribute 'domains'
> 
> ah frickin 'ell.  you'll need to use a less up-to-date
> 
> there are dozens of simulations that need "conversion".
> 
> my feeling is: screw that, we write our own function which emulates
> the old behaviour of run_simulation(), of 6 months ago.
> 
> l.
> 
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev




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

^ permalink raw reply

* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-26 11:02 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 #115 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
i enabled export PYTHONTRACEMALLOC=25
https://docs.python.org/3/using/cmdline.html#envvar-PYTHONTRACEMALLOC

/usr/lib/python3.7/subprocess.py:858: ResourceWarning: subprocess 1551551 is
still running
  ResourceWarning, source=self)
Object allocated at (most recent call last):
  File "simulator/test_sim.py", lineno 106
    unittest.main()
  File "/usr/lib/python3.7/unittest/main.py", lineno 101
    self.runTests()
  File "/usr/lib/python3.7/unittest/main.py", lineno 271
    self.result = testRunner.run(self.test)
  File "/usr/lib/python3.7/unittest/runner.py", lineno 176
    test(result)
  File "/usr/lib/python3.7/unittest/suite.py", lineno 84
    return self.run(*args, **kwds)
  File "/usr/lib/python3.7/unittest/suite.py", lineno 122
    test(result)
  File "/usr/lib/python3.7/unittest/suite.py", lineno 84
    return self.run(*args, **kwds)
  File "/usr/lib/python3.7/unittest/suite.py", lineno 122
    test(result)
  File "/usr/lib/python3.7/unittest/case.py", lineno 663
    return self.run(*args, **kwds)
  File "/usr/lib/python3.7/unittest/case.py", lineno 615
    testMethod()
  File "simulator/test_sim.py", lineno 58
    self.run_test_program(program, [1, 2, 3, 4])
  File "simulator/test_sim.py", lineno 95
    with run_program(prog) as q:
  File "/home/lkcl/src/libreriscv/soc/src/soc/simulator/qemu.py", lineno 54
    q = QemuController(program.binfile.name)
  File "/home/lkcl/src/libreriscv/soc/src/soc/simulator/qemu.py", lineno 16
    stdin=subprocess.PIPE)
simulator/test_sim.py:58: ResourceWarning: unclosed file <_io.BufferedWriter
name=4>
  self.run_test_program(program, [1, 2, 3, 4])


this gets rid of it:

        self.qemu_popen.stdout.close()
        self.qemu_popen.stdin.close()

except one of the qemus is still running, thissays you have
to call qemu_popen.communicate():
https://docs.python.org/3/library/subprocess.html

fixed with a quick commit.

-- 
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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-26 11:10 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 #116 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
i've also added pygdbmi to the dependencies in setup.py and added a way
to get hold of and compile up powerpc64 gdb.  michael (and anyone else)
could you take a look?
https://git.libre-riscv.org/?p=soc.git;a=blob;f=README.md;hb=HEAD

-- 
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] test failure when running nmutil tests on GitLab CI
From: Luke Kenneth Casson Leighton @ 2020-03-26 11:12 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <20200326115158.221499f9f35dab24f9a47db3@platen-software.de>

On Thu, Mar 26, 2020 at 10:52 AM Tobias Platen
<libre-soc@platen-software.de> wrote:
>
> I had a similar error when I ugraded nmigen some months ago. I still don't remember how I solved that.

index c6a89e3..42f6fd6 100644
--- a/nmigen/compat/sim/__init__.py
+++ b/nmigen/compat/sim/__init__.py
@@ -19,7 +19,7 @@ def run_simulation(fragment_or_module, generators,
clocks={"sync": 10}, vcd_name

     if not isinstance(generators, dict):
         generators = {"sync": generators}
-        fragment.domains += ClockDomain("sync")
+        #fragment.domains += ClockDomain("sync")

     sim = Simulator(fragment)
     for domain, period in clocks.items():


except that now won't work on the very latest nmigen.

this however is fine:

commit 57d95b7f95dd37e2527db7b04be9ac8f324133e2 (HEAD -> master,
origin/master, origin/HEAD)
Merge: 7245b1e dfcf793
Author: Sebastien Bourdeauducq <sb@m-labs.hk>
Date:   Thu Feb 6 01:06:27 2020 +0800

    Merge branch 'master' of https://github.com/nmigen/nmigen

_______________________________________________
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] [OP-CD] OpenPOWER Foundation "Virtual Coffee" Calls
From: Luke Kenneth Casson Leighton @ 2020-03-26 11:23 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwjpLn9TpF2Fj1ZXtQNWsZ5f04iGwd3c2KvkTo=igingw@mail.gmail.com>

On Thu, Mar 26, 2020 at 4:10 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
>
>
> On Tuesday, March 24, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>>
>> Maybe we should participate.
>
>
> i'll be on both.

late... :)  i'll juuust rest my eyes for a bit... ho hum.

the next one is at 22:00 UTC.  if you use this link:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=3&day=26&hour=22&min=0&sec=0&p1=136
or this
https://www.timeanddate.com/worldclock/meetingtime.html?iso=20200326&p1=136

you can "add more cities" - keep London (it's UTC for now) and use its
time at Thu 22:00 to cross-check your own call-in time.

dial-in numbers (actual telephone) you can find at the link, remember
to press # twice after entering the meeting ID.
https://openpowerfoundation.org/openpower-virtual-coffee-calls/

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] cache SRAM organisation
From: Staf Verhaegen @ 2020-03-26 12:18 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDxiyTEsneXN65Kq0HsEsdL3wdY=NYayq2tz5egXJNCVfg@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 3436 bytes --]

Luke Kenneth Casson Leighton schreef op wo 25-03-2020 om 15:53 [+0000]:
> On Wed, Mar 25, 2020 at 1:46 PM Staf Verhaegen <staf@fibraservi.eu> wrote:
> 
> > > this because it turns out that asynchronous SRAM can act, when used in aRegister File, as if it was a (separate) Register Bypass / ForwardingPort.  with the Out-of-Order Engine being a huge cyclic feedback loopbetween ALUs and RegFile, clock delays are an impediment, and havingcompletely separate (extra) Regfile Bypass ports dramatically increases thenumber of wires and Multiplexers.
> > 
> > Could detail more on how the adress, data and output signals of this asynchronous block would be used and switched between synchronous and asynchronous functioning. To me it seems that it would just place of the multiplexers, not the amount.
> 
> ok i will try to outine it, there is quite a lot of detail, i apologise.
> it's basically the "pass-through" system used in nmigen FIFOs, and the"synchronous" mode of nmigen Memory.  the requirements are: what iswritten has to be available *combinatorially* - i.e. on the same clockcycle - if simultaneously read via another port.
> now, yes i took note that this is not supposed to be permitted: you'renot normally permitted to be able to read *and* write to an SRAM cellat the same time.  however, that's exactly what we need.

You seem to mixing up two different concepts, e.g. synchronicity and write-through. Synchronous means signals are synced with an edge of a (clock) signal. SRAM write-through means that after a write operation you also get on the Q output the data you have just written. These two concepts are orthogonal to each other.
The current synchronous SRAM being developed will most likely have write-through behavior; will be confirmed before May test chip tape-out. It will cause delay on the signal though. I need to check if it has changed but in the OpenRAM 0.35um test tape-out I did the address and data input was latched on rising edge and the Q output was updated on falling edge of the clock. So the delay on the Q output is half a clock cycle plus the internal delay on the output latch enable signal.
So if timing of the write-through is critical it is still best to still include MUXs as said in Jacob's reply to allow the bypass ofsignal. I have seen SRAM that did include a AWT (asynchronous write through) but this just moved the MUXs inside the SRAM block and also adds them if you don't need this AWT. So I would like to keep these MUX be added added externally is needed.
In theory on a single port SRAM
> a workaround (fallback position) is, we use DFF latches.  i created a"bypass latch" function which creates DFF latches with such acombinatorial bypass: we actually use them quite a lot (includingbetween pipeline stages so that we can programmatically cut the numberof pipeline stages in half at the flick of a switch).
> however for the Register File we would not "switch" betweensynchronous / asynchronous mode.  the reason why we need thesynchronous mode is because some Function Units will be sitting idle,waiting for their input operands, which have to come from otherFunction Units as "results".

I can understand you do this to implement functional units with configurable pipeline length but I would strongly discourage to pipeline register files after each other . If the latter is excluded would you still need an asynchronous RAM block ?

greets,
Staf.



[-- Attachment #2: Type: text/plain, Size: 177 bytes --]

_______________________________________________
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] cache SRAM organisation
From: Staf Verhaegen @ 2020-03-26 12:27 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDxiyTEsneXN65Kq0HsEsdL3wdY=NYayq2tz5egXJNCVfg@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 985 bytes --]

Luke Kenneth Casson Leighton schreef op wo 25-03-2020 om 15:53 [+0000]:
> On Wed, Mar 25, 2020 at 1:46 PM Staf Verhaegen <staf@fibraservi.eu> wrote:
> a workaround (fallback position) is, we use DFF latches.  i created a"bypass latch" function which creates DFF latches with such acombinatorial bypass: we actually use them quite a lot (includingbetween pipeline stages so that we can programmatically cut the numberof pipeline stages in half at the flick of a switch).

Would like to make separate side remark here. In ASICs MUXes are relative expensive gates with respect to delay and power. So if this principle is generally applied over the whole design it will make it difficult to make a chip that is competitive in power/performance compared to ARM/x86 CPUs.
In general if you are trying to optimize power/performance of your chip the KISS (keep it simple stupid) is your friend. In that respect your complex dual ISA decoder will have a power cost.

greets,
Staf.



[-- Attachment #2: Type: text/plain, Size: 177 bytes --]

_______________________________________________
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] cache SRAM organisation
From: Staf Verhaegen @ 2020-03-26 12:31 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <db557324bcb76a999d8f66c75b9319974a1a1e08.camel@fibraservi.eu>

[-- Attachment #1.1: Type: text/plain, Size: 352 bytes --]

(Sorry send to early)


> .In theory on a single port SRAM

In theory on a single port SRAM the write data input and the Q data output could be on opposite sides of the block but I will make sure that these pins are on the same side of the block and close together so you don't need much wire to connect a pass-through MUX.

greets,
Staf.



[-- Attachment #2: Type: text/plain, Size: 177 bytes --]

_______________________________________________
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 186] Create decoder for SOC: Power ISA and RISC-V
From: Luke Kenneth Casson Leighton @ 2020-03-26 12:59 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <bug-186-13-jh3pGIikod@http.bugs.libre-riscv.org/>

On Wednesday, March 25, 2020, <bugzilla-daemon@libre-riscv.org> wrote:

> http://bugs.libre-riscv.org/show_bug.cgi?id=186
>
> --- Comment #110 from Michael Nolan <mtnolan2640@gmail.com> ---
> I've got a rudimentary qemu-gdb interface working in qemu.py:
> https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/
> simulator/qemu.py;h=70e29b0d76b65227a06d3ba3bd95315cf5af37e8;hb=
> 3f7e6c771c7f8df65e67e6dc350964a54aee8066
>
> It's able to load a kernel into qemu, set up a breakpoint at the start of
> it,
> single step it, and dump the register contents.


coooool.

confirmed able to duplicate that, here.

i did encounter KeyError, register-values not present but it is spurious
and unreliably occurring.

i added an assert to investigate and, sigh, was no longer seeing failures
even after running 20 times.

the other really useful addition would be memory-dump / memory location
reading.

btw change of topic, i noticed, just like in the original RegSim, OP_ADD is
not joined by OP_SUB because Anton chose to do "add1 to op1" as well as
"invert op1" in the InternalOp csv.

therefore we need to pass the whole of the decode row to the
execute_alu_sim function, rather than just the enum InternalOp value.




-- 
---
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] cache SRAM organisation
From: Luke Kenneth Casson Leighton @ 2020-03-26 13:05 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <e430ea6587d292166fd58460adf4dfebfad20c6d.camel@fibraservi.eu>

On Thursday, March 26, 2020, Staf Verhaegen <staf@fibraservi.eu> wrote:

>
> Would like to make separate side remark here. In ASICs MUXes are relative
> expensive gates with respect to delay and power. So if this principle is
> generally applied over the whole design it will make it difficult to make a
> chip that is competitive in power/performance compared to ARM/x86 CPUs.


just the ALU pipeline registers.  we felt that the advantage of being able
to drop to say 500mhz and halve the number of pipeline stages to say 5, and
also be able to ramp up to 1.6ghz and double bavk up to 10 stages, was
worth considering.


> In general if you are trying to optimize power/performance of your chip
> the KISS (keep it simple stupid) is your friend. In that respect your
> complex dual ISA decoder will have a power cost.


sigh yes i know.  however i do not know if you've seen the POWER ISA
decoder, it is *five* levels deep in some places, decoding different field
ranges in a dependent cascade!

adding RV would be trivial by comparison!

 but yes we are generally getting the message from various sources that
dual ISA isn't a good idea.

l.



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-26 14:13 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 #117 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #115)

> 
> except one of the qemus is still running, thissays you have
> to call qemu_popen.communicate():
> https://docs.python.org/3/library/subprocess.html
> 
> fixed with a quick commit.

Oh, thank you! I was struggling to figure out where this was coming from.

-- 
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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-26 14:14 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 #118 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #116)
> i've also added pygdbmi to the dependencies in setup.py and added a way
> to get hold of and compile up powerpc64 gdb.  michael (and anyone else)
> could you take a look?
> https://git.libre-riscv.org/?p=soc.git;a=blob;f=README.md;hb=HEAD

Yep, that looks right

-- 
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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-26 14:19 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 #119 from Michael Nolan <mtnolan2640@gmail.com> ---
>coooool.
>
>confirmed able to duplicate that, here.
>
>i did encounter KeyError, register-values not present but it is spurious
>and unreliably occurring.

Huh. It sounds like that's from the register read code, where it reaches in to
a largeish dict to grab the register values. I'll have to see if I can
replicate it on my end.

>
>i added an assert to investigate and, sigh, was no longer seeing failures
>even after running 20 times.
>
>the other really useful addition would be memory-dump / memory location
>reading.

That shouldn't be too hard to add. Similar to the register comparison code,
it'll need to only do it to specific locations as comparing all of memory would
not only take too long, but disagree because qemu loads the kernel and some
other stuff into memory and the simulator does not. 

>btw change of topic, i noticed, just like in the original RegSim, OP_ADD is
>not joined by OP_SUB because Anton chose to do "add1 to op1" as well as
>"invert op1" in the InternalOp csv.
>
>therefore we need to pass the whole of the decode row to the
>execute_alu_sim function, rather than just the enum InternalOp value.

Ah ok.

-- 
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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-26 14:43 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 #120 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #118)
> (In reply to Luke Kenneth Casson Leighton from comment #116)

> >the other really useful addition would be memory-dump / memory location
> >reading.
> 
> That shouldn't be too hard to add. Similar to the register comparison code,

yes just the right voodoo gdb incantation.  i think it allows byte word dword
selection.

> it'll need to only do it to specific locations as comparing all of memory
> would not only take too long, but disagree because qemu loads the kernel and
> some other stuff into memory and the simulator does not. 

urk :)

> 
> >btw change of topic, i noticed, just like in the original RegSim, OP_ADD is
> >not joined by OP_SUB because Anton chose to do "add1 to op1" as well as
> >"invert op1" in the InternalOp csv.
> >
> >therefore we need to pass the whole of the decode row to the
> >execute_alu_sim function, rather than just the enum InternalOp value.
> 
> Ah ok.

yeh :)

should be very straightforward (you want to do it?) a separate if elif elif,
"if op1.value == Op1.ONE op1 += 1"

can skip carry for now, add as TODO.

then also if row['op1neg'] op1 ^= 0xffffffffffffffff

something like that.

or op1 = (~op1) & 0xffffffffffffffff

that _should_ be sufficient to get sub, subi and neg all working, with not a
lot of effort.

-- 
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 186] Create decoder for SOC: Power ISA and RISC-V
From: bugzilla-daemon @ 2020-03-26 14:56 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 #121 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #120)

> 
> should be very straightforward (you want to do it?) a separate if elif elif,
> "if op1.value == Op1.ONE op1 += 1"
> 
> can skip carry for now, add as TODO.
> 
> then also if row['op1neg'] op1 ^= 0xffffffffffffffff
> 
> something like that.
> 
> or op1 = (~op1) & 0xffffffffffffffff
> 
> that _should_ be sufficient to get sub, subi and neg all working, with not a
> lot of effort.

Working now. Need to sort out setting the carry and overflow flags at some
point though, that'll be more fun...

-- 
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] cache SRAM organisation
From: Luke Kenneth Casson Leighton @ 2020-03-26 15:15 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <db557324bcb76a999d8f66c75b9319974a1a1e08.camel@fibraservi.eu>

On Thursday, March 26, 2020, Staf Verhaegen <staf@fibraservi.eu> wrote:
>
>
> You seem to mixing up two different concepts, e.g. synchronicity and
> write-through.


ah ok.  i didn't realise that SRAMs would have these as separate concepts.
perhaps i would get it immediately if i saw a gate level schematic.


> Synchronous means signals are synced with an edge of a (clock) signal.
> SRAM write-through means that after a write operation you also get on the Q
> output the data you have just written. These two concepts are orthogonal to
> each other.
> The current synchronous SRAM being developed will most likely have
> write-through behavior;


ah good


> will be confirmed before May test chip tape-out.


ah May not March.


>
>  It will cause delay on the signal though. I need to check if it has
> changed but in the OpenRAM 0.35um test tape-out I did the address and data
> input was latched on rising edge and the Q output was updated on falling
> edge of the clock. So the delay on the Q output is half a clock cycle plus
> the internal delay on the output latch enable signal.


fascinating.  that's pretty much exactly what the CDC6600 did on its
register file.


> So if timing of the write-through is critical it is still best to still
> include MUXs as said in Jacob's reply to allow the bypass ofsignal. I have
> seen SRAM that did include a AWT (asynchronous write through) but this just
> moved the MUXs inside the SRAM block and also adds them if you don't need
> this AWT. So I would like to keep these MUX be added added externally is
> needed.


ok

> > mode.  the reason why we need the synchronous mode is because some
> > Function Units will be sitting idle,waiting for their input operands,
which have to come from
> > otherFunction Units as "results".


> I can understand you do this to implement functional units with
> configurable pipeline length but I would strongly discourage to pipeline
> register files after each other .


"pipeline register files after each other"? apologies i am not clear what
you mean, here.  do you mean "don't do write-thru on the Regfile"?

this design is not like an InOrder system where it is very risky to change
pipeline lengths or do any kind of fancy work.

the (parallel) OoO design has all data dependencies sorted out, all units
*know exactly* which units they are waiting for, they can be arbitrary
completion time, they can be FSMs, and the Dependency Matrices just don't
care because they record completion *not* completion *time*.

therefore the only thing stopping them from proceeding is how fast they can
get a result, so that other FUs can get at it as an input operand as quick
as possible.

that means either: a Register Forwarding Bus, or it means a write to the
Regfile followed by a read.

therefore anything we can do to reduce the number of clock cycles between
that regfile write and subsequent read is a good thing.

if write-thru is available, we can use it to reduce delay by one cycle.
however yes i note that because it is on the falling edge we might not be
able to take full advantage of it.



If the latter is excluded would you still need an asynchronous RAM block ?


i can't tell, yet, apologies.  i believe the answer is no.

Staf it would help enormously i think if you could let us know, in terms of
what options to nmigen Memory module, are permitted.  i am assuming that
nmigen Memory actually supports the options correctly!

we can then "wrap" the Memory module (or hook it) and throw asserts if we
ever use options that are not supported.

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] cache SRAM organisation
From: Luke Kenneth Casson Leighton @ 2020-03-26 15:15 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <350514fc6cf0b578804b85775beb8c0e039cab1e.camel@fibraservi.eu>

On Thursday, March 26, 2020, Staf Verhaegen <staf@fibraservi.eu> wrote:

> (Sorry send to early)
>
>
> > .In theory on a single port SRAM
>
> In theory on a single port SRAM the write data input and the Q data output
> could be on opposite sides of the block but I will make sure that these
> pins are on the same side of the block and close together so you don't need
> much wire to connect a pass-through MUX.


ah fantastic, really appreciated.

that will help keep it small.

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

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