[libre-riscv-dev] daily kan-ban update 20may2020

[libre-riscv-dev] daily kan-ban update 20may2020

[Luke Kenneth Casson Leighton]

yesterday:
* more pipeline stuff with michael and cole and jacob.  researched
TRAP ops in particular
* identified that MUL and DIV have similar register allocation to
SHIFT and LOGICAL
* moved MUL and DIV ops to their own respective Function Unit
(power_enums.py, csv files)
* talked with Marketnext about the resource requirements for the May
30 Hackathon.
* worked out from this image that we need to do pretty much the same thing: give
  each FunctionUnit a "consistent uniform interface" of its register
port allocation.
  https://libre-soc.org/3d_gpu/6600_scoreboard_fu_regs.png

this morning:
* created nmutil exts helper function and used it everywhere (OP_EXTS
and other places)
* helped Jean-Paul to understand the requirements for regular
coriolis2 layout of the Dep Matrices

today:

* send an agenda to Hugh, Tim, Yehowshua for the bi-weekly OpenPOWER conf call
* received a message from these guys, they would like to do a review
https://radicallyopensecurity.com/
* start putting an "API / Spec" system together for Function Units, to
be able to connect Regfiles to ports.
* do the "Record" conversion of CompALU (part of the API/Spec for FUs)

l.

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

Re: [libre-riscv-dev] daily kan-ban update 20may2020

[Cole Poirier]

On May 20 2020, at 7:14 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> yesterday:
> * more pipeline stuff with michael and cole and jacob.  researched
> TRAP ops in particular

Yesterday I learned another valuable lesson on the merits of the KISS
philosophy. Today I plan on integrating the Bpermd module into the
logical pipeline, with tests.

> * talked with Marketnext about the resource requirements for the May
> 30 Hackathon.

Is there a document about this on the wiki? If not would you mind
briefly explaining what the parameters and the objectives of the
hackathon are?

> * received a message from these guys, they would like to do a review
> https://radicallyopensecurity.com/

Just took a quick perusal of their website, they look like they share
our philosophy about digital rights, as well as having a
'social-benefit-esque' organizational model. I think their doing a
review of our processor's security would be welcome help. Your thoughts?

Cole


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

Re: [libre-riscv-dev] daily kan-ban update 20may2020

[Luke Kenneth Casson Leighton]

On Wed, May 20, 2020 at 3:51 PM Cole Poirier <colepoirier@gmail.com> wrote:

> Yesterday I learned another valuable lesson on the merits of the KISS
> philosophy.

funny man :)

> Today I plan on integrating the Bpermd module into the
> logical pipeline, with tests.

fooocuuuus :)  adding the module to Logical main_stage.py should be
around... maximum 10 lines of code.  really.  not.  difficult.  link
the inputs.  link the outputs.  err... that's it.

btw as a third (incremental) step, after integrating it and putting in
the unit test into soc.fu.logical.test/test_pipe_caller.py, you should
actually be able to integrate the formal proof into the Logical
pipeline as well.

> > * talked with Marketnext about the resource requirements for the May
> > 30 Hackathon.
>
> Is there a document about this on the wiki?

there isn't.  there should be.  however it is up to Marketnext.  the
issue is that i am not sure if they understand quite how high the
resource requirements are, and consequently how long it will take
people in India (and other places across the world) to install the
development environment.

> If not would you mind
> briefly explaining what the parameters and the objectives of the
> hackathon are?

to introduce over 15 different groups / teams / individuals to
Libre-SOC development.

> > * received a message from these guys, they would like to do a review
> > https://radicallyopensecurity.com/
>
> Just took a quick perusal of their website, they look like they share
> our philosophy about digital rights, as well as having a
> 'social-benefit-esque' organizational model. I think their doing a
> review of our processor's security would be welcome help. Your thoughts?

their review is a mandatory requirement as part of the NLNet funding.
i did point out to them that asking to have a private conversation
about their role is not exactly very transparent :)

l.

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

Re: [libre-riscv-dev] daily kan-ban update 20may2020

[Michael Nolan]

It looks like I'm working formal proofs today! I started out by making 
sure the alu's 32 bit carry was working correctly and kinda branched out 
from there... After lunch I think I'll work on the overflow and 
overflow32 ports for alu and checking the outputs of the CR pipeline.

--Michael



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

Re: [libre-riscv-dev] daily kan-ban update 20may2020

[Luke Kenneth Casson Leighton]

On Wed, May 20, 2020 at 4:50 PM Michael Nolan <mtnolan2640@gmail.com> wrote:
>
> It looks like I'm working formal proofs today! I started out by making
> sure the alu's 32 bit carry was working correctly and kinda branched out
> from there... After lunch I think I'll work on the overflow and
> overflow32 ports for alu and checking the outputs of the CR pipeline.

nice.  can you raise the associated bugreports (like i just did here
https://bugs.libre-soc.org/show_bug.cgi?id=331)

i'll help fill them in.

l.

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

Re: [libre-riscv-dev] daily kan-ban update 20may2020

[Cole Poirier]

On May 20 2020, at 8:14 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Wed, May 20, 2020 at 3:51 PM Cole Poirier <colepoirier@gmail.com> wrote:
> 
>> Yesterday I learned another valuable lesson on the merits of the KISS
>> philosophy.
> 
> funny man :)
> 
>> Today I plan on integrating the Bpermd module into the
>> logical pipeline, with tests.
> 
> fooocuuuus :)  adding the module to Logical main_stage.py should be
> around... maximum 10 lines of code.  really.  not.  difficult.  link
> the inputs.  link the outputs.  err... that's it.
> 
> btw as a third (incremental) step, after integrating it and putting in
> the unit test into soc.fu.logical.test/test_pipe_caller.py, you should
> actually be able to integrate the formal proof into the Logical
> pipeline as well.

Will copy this to and comment on it at https://bugs.libre-soc.org/show_bug.cgi?id=316.

>> > * talked with Marketnext about the resource requirements for the May
>> > 30 Hackathon.
>> 
>> Is there a document about this on the wiki?
> 
> there isn't.  there should be.  however it is up to Marketnext.  the
> issue is that i am not sure if they understand quite how high the
> resource requirements are, and consequently how long it will take
> people in India (and other places across the world) to install the
> development environment.

Ah that's an interesting constraint. Would it be possible (or even
desirable) to provide them with a compressed archive of all the
necessary repos, tools, etc in a frozen state?

>> If not would you mind
>> briefly explaining what the parameters and the objectives of the
>> hackathon are?
> 
> to introduce over 15 different groups / teams / individuals to
> Libre-SOC development.

That's pretty darn cool!

>> > * received a message from these guys, they would like to do a review
>> > https://radicallyopensecurity.com/
>> 
>> Just took a quick perusal of their website, they look like they share
>> our philosophy about digital rights, as well as having a
>> 'social-benefit-esque' organizational model. I think their doing a
>> review of our processor's security would be welcome help. Your thoughts?
> 
> their review is a mandatory requirement as part of the NLNet funding.
> i did point out to them that asking to have a private conversation
> about their role is not exactly very transparent :)
> 
> l.

Oh, very happy that this turns out to be a mandatory NLNet funding
requirement. I agree that their request for private conversation is odd
given the context.

Cole


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

Re: [libre-riscv-dev] daily kan-ban update 20may2020

[Luke Kenneth Casson Leighton]

On Wednesday, May 20, 2020, Cole Poirier <colepoirier@gmail.com> wrote:

> On May 20 2020, at 8:14 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
> > btw as a third (incremental) step, after integrating it and putting in
> > the unit test into soc.fu.logical.test/test_pipe_caller.py, you should
> > actually be able to integrate the formal proof into the Logical
> > pipeline as well.
>
> Will copy this to and comment on it at https://bugs.libre-soc.org/
> show_bug.cgi?id=316.


good call.


> >> > * talked with Marketnext about the resource requirements for the May
> >> > 30 Hackathon.
> >>
> >> Is there a document about this on the wiki?
> >
> > there isn't.  there should be.  however it is up to Marketnext.  the
> > issue is that i am not sure if they understand quite how high the
> > resource requirements are, and consequently how long it will take
> > people in India (and other places across the world) to install the
> > development environment.
>
> Ah that's an interesting constraint. Would it be possible (or even
> desirable) to provide them with a compressed archive of all the
> necessary repos, tools, etc in a frozen state?


this requires the organisers to understand.  they are not keenly
technical.  they love the 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