From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Yehowshua <yimmanuel3@gatech.edu>
Cc: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Finished Scoreboard
Date: Tue, 5 May 2020 17:26:14 +0100
Message-ID: <CAPweEDxJ1HYkOYcn58jUtuUjz6q2jossMdRw54xhN4aANkW0mQ@mail.gmail.com> (raw)
In-Reply-To: <74E24B62-C4E6-4F95-88AC-DE45C5117D88@gatech.edu>
On Tue, May 5, 2020 at 5:15 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> Do you think the scoreboard can be done by mid June?
i'm assuming you meant to ask this on the list.
the actual scoreboard (dependency matrices) themselves are "done". it
was only the change to multi-signal control at the register file that
needed alteration, and *that* was done several weeks ago (didn't take
long).
it's the "arbitration" connectivity to the register file (3 days
design work on the cyclic buffer system), the LDSTCompUnit (10 days
redesign, 2-3 days implementing, the change to the ALU CompUnit (8
days redesign, 2-3 days implementing) that is the time-sink.
the next phase is to create a POWER9 "Condition" Register File
containing CR0-CR7, CTR and other essential registers related to
Branch Control. this *extra register file* was the primary motivation
behind the additional scoreboard read/write "operand" wires, because
one set manages the INT/FP regfile, another set manages the "Condition
Register" regfile (oh, and another set - with a completely different
DM Matrix - manages the SPRs.
which is why we need people to focus on "ancillary" tasks because
without people focussing on ancillary tasks, we're not going to have
instructions completed, the pipelines designed, the memory interface
completed, no Branch Prediction Unit, no TLB, no RADIX MMU.
hence the urgency of asking people to focus on specific tasks, and not
anything else.
the amount that we have to do in such a short amount of time is
enormous, and we need to bash through it, without wasting *any* time.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next parent reply index
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <74E24B62-C4E6-4F95-88AC-DE45C5117D88@gatech.edu>
2020-05-05 16:26 ` Luke Kenneth Casson Leighton [this message]
2020-05-05 18:18 ` Yehowshua
2020-05-05 18:20 ` Immanuel, Yehowshua U
2020-05-06 9:06 ` Luke Kenneth Casson Leighton
2020-05-06 9:08 ` Luke Kenneth Casson Leighton
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=CAPweEDxJ1HYkOYcn58jUtuUjz6q2jossMdRw54xhN4aANkW0mQ@mail.gmail.com \
--to=lkcl@lkcl.net \
--cc=libre-riscv-dev@lists.libre-riscv.org \
--cc=yimmanuel3@gatech.edu \
/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