Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] [Bug 209] spectre-proof speculative execution
Date: Mon, 18 May 2020 20:38:52 +0100
Message-ID: <CAPweEDyucnHQyj0XyZa4XoKbFf64i56=McFL7hSoz_EkJmpdCA@mail.gmail.com> (raw)
In-Reply-To: <0C5BB73E-D5A4-4EE5-8BDE-C5F48188B74E@gatech.edu>

On Mon, May 18, 2020 at 8:25 PM Yehowshua <yimmanuel3@gatech.edu> wrote:

> > so basically this extends the Dependency Matrix "Shadow" concept actually
> > right down into the Caches.
>
> Exactly - keep in mind that this is only for variant 1.
> I’ll read up on the other variants later.
>
> Why do CPUs have to be so complicated...

Hugh said on one of the Virtual Coffee Calls, he's been in touch with
the IBM engineers for many years.  back when they first met, they told
him - straight up - that CPU design is hard.  however - it took
several years for him to properly and actually appreciate that when
they said "hard" they did not mean it in the ordinary sense of
"certain kinds of software engineering problems are hard", they meant,
like, REALLY hard.

this is why i recommended that we go with python, because not only can
we apply OO (Object-Orientated) techniques, we tap directly into the
"default mindset" behind python, which is that you *do not* write code
- ever - without having an adequate unit test.

this in combination with patiently following Mitch's advice of
drilling down to first principles, i am confident that we'll do fine.

l.

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

  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-209-13@https.bugs.libre-soc.org/>
2020-05-18 19:06 ` bugzilla-daemon
2020-05-18 19:24 ` bugzilla-daemon
2020-05-18 19:25   ` Yehowshua
2020-05-18 19:38     ` Luke Kenneth Casson Leighton [this message]
2020-05-18 19:59 ` bugzilla-daemon
2020-05-18 20:51 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPweEDyucnHQyj0XyZa4XoKbFf64i56=McFL7hSoz_EkJmpdCA@mail.gmail.com' \
    --to=lkcl@lkcl.net \
    --cc=libre-riscv-dev@lists.libre-riscv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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