From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 325] create POWER9 TRAP pipeline
Date: Tue, 02 Jun 2020 17:54:29 +0000
Message-ID: <bug-325-13-EbBX4qrY3x@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-325-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=325
--- Comment #17 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
Cole: example (A is to B, as C is to D). examine case OP_TRAP and case OP_SC.
A:
ctrl_tmp.irq_nia <= std_logic_vector(to_unsigned(16#C00#, 64));
ctrl_tmp.srr1 <= msr_copy(ctrl.msr);
B:
????
C:
ctrl_tmp.irq_nia <= std_logic_vector(to_unsigned(16#700#,
64));
ctrl_tmp.srr1 <= msr_copy(ctrl.msr);
D:
comb += self.o.nia.data.eq(0x700) # trap address
comb += self.o.nia.ok.eq(1)
it should be BLINDINGLY obvious that B should be:
comb += self.o.nia.data.eq(0xC00) # trap address
comb += self.o.nia.ok.eq(1)
therefore, in switch statement OP_SC, that's what goes into that function.
and that's it.
ta-daaa. OP_SC is completed.
wasn't that easy?
Q: do you understand or know what OP_SC is or does?
A: i don't... and don't care, and it is completely irrelevant to you, as well.
(it's *optional* to have understanding: you may *desire* understanding,
you may *like* to have understanding, but it is, fundamentally, *completely
irrelevant* to the actual task)
Q: do we *need* to understand or know what OP_SC is or does?
A: no we do not.
Q: will it work?
A: yes it will.
Q: will there be bugs?
A: most probably, and those can be found with unit tests.
Q: do absolutely all the required unit tests have to be written *right now*?
A: no they do not.
Q: do we need to freeze and lock up solid in total fear at our total and
complete lack of understanding just because those unit tests do not exist?
A: of course not.
so reading a 1300 page PDF is completely and utterly pointless. and making
reading that 1300 page PDF a hard, fixed, absolute critical dependency on
*completing this task* is a false assumption, isn't it?
--
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
next prev parent reply index
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 12:28 [libre-riscv-dev] [Bug 325] New: " bugzilla-daemon
2020-05-19 12:29 ` [libre-riscv-dev] [Bug 325] " bugzilla-daemon
2020-05-19 12:30 ` bugzilla-daemon
2020-05-19 14:11 ` bugzilla-daemon
2020-05-19 14:57 ` bugzilla-daemon
2020-05-19 15:49 ` bugzilla-daemon
2020-05-19 16:54 ` bugzilla-daemon
2020-05-19 18:09 ` bugzilla-daemon
2020-05-19 18:13 ` bugzilla-daemon
2020-05-19 20:43 ` bugzilla-daemon
2020-05-19 23:19 ` bugzilla-daemon
2020-05-19 23:31 ` bugzilla-daemon
2020-05-24 3:41 ` bugzilla-daemon
2020-05-24 3:43 ` bugzilla-daemon
2020-05-25 2:41 ` bugzilla-daemon
2020-05-27 14:43 ` bugzilla-daemon
2020-05-27 14:48 ` bugzilla-daemon
2020-05-27 14:49 ` bugzilla-daemon
2020-06-01 19:05 ` bugzilla-daemon
2020-06-02 11:21 ` bugzilla-daemon
2020-06-02 14:06 ` bugzilla-daemon
2020-06-02 17:54 ` bugzilla-daemon [this message]
2020-06-02 23:07 ` bugzilla-daemon
2020-06-02 23:07 ` bugzilla-daemon
2020-06-02 23:46 ` bugzilla-daemon
2020-06-02 23:54 ` bugzilla-daemon
2020-06-02 23:59 ` bugzilla-daemon
2020-06-03 0:11 ` bugzilla-daemon
2020-06-03 0:38 ` bugzilla-daemon
2020-06-03 0:47 ` bugzilla-daemon
2020-06-03 1:13 ` bugzilla-daemon
2020-06-03 1:28 ` bugzilla-daemon
2020-06-03 1:35 ` bugzilla-daemon
2020-06-03 1:41 ` bugzilla-daemon
2020-06-03 1:50 ` bugzilla-daemon
2020-06-03 2:31 ` bugzilla-daemon
2020-06-03 3:27 ` bugzilla-daemon
2020-06-04 0:29 ` bugzilla-daemon
2020-06-04 0:34 ` bugzilla-daemon
2020-06-04 22:41 ` bugzilla-daemon
2020-06-05 0:32 ` bugzilla-daemon
2020-06-05 0:35 ` bugzilla-daemon
2020-06-05 1:06 ` bugzilla-daemon
2020-06-05 1:09 ` bugzilla-daemon
2020-06-05 1:25 ` bugzilla-daemon
2020-06-05 2:13 ` bugzilla-daemon
2020-06-05 2:34 ` bugzilla-daemon
2020-06-05 3:37 ` bugzilla-daemon
2020-06-05 3:52 ` bugzilla-daemon
2020-06-05 4:19 ` bugzilla-daemon
2020-06-05 14:16 ` bugzilla-daemon
2020-06-05 15:12 ` bugzilla-daemon
2020-06-05 15:21 ` bugzilla-daemon
2020-06-05 15:33 ` bugzilla-daemon
2020-06-05 15:43 ` bugzilla-daemon
2020-06-05 15:46 ` bugzilla-daemon
2020-06-05 16:14 ` bugzilla-daemon
2020-06-05 18:14 ` bugzilla-daemon
2020-06-05 19:08 ` bugzilla-daemon
2020-06-05 19:15 ` bugzilla-daemon
2020-06-05 19:49 ` bugzilla-daemon
2020-06-05 20:12 ` bugzilla-daemon
2020-06-05 21:59 ` bugzilla-daemon
2020-06-05 22:02 ` bugzilla-daemon
2020-06-05 23:25 ` bugzilla-daemon
2020-06-05 23:46 ` bugzilla-daemon
2020-06-06 2:23 ` bugzilla-daemon
2020-06-07 0:31 ` bugzilla-daemon
2020-06-07 0:38 ` bugzilla-daemon
2020-06-07 0:39 ` bugzilla-daemon
2020-06-07 0:44 ` bugzilla-daemon
2020-06-07 0:51 ` bugzilla-daemon
2020-06-07 1:32 ` bugzilla-daemon
2020-06-07 1:42 ` bugzilla-daemon
2020-06-07 1:52 ` bugzilla-daemon
2020-06-07 2:09 ` bugzilla-daemon
2020-06-07 2:36 ` bugzilla-daemon
2020-06-07 3:09 ` bugzilla-daemon
2020-06-07 3:23 ` bugzilla-daemon
2020-06-07 6:11 ` bugzilla-daemon
2020-06-07 6:26 ` bugzilla-daemon
2020-06-07 20:42 ` bugzilla-daemon
2020-06-07 20:45 ` bugzilla-daemon
2020-06-07 20:51 ` bugzilla-daemon
2020-06-07 21:11 ` bugzilla-daemon
2020-06-07 21:18 ` bugzilla-daemon
2020-06-07 21:23 ` bugzilla-daemon
2020-06-07 21:31 ` bugzilla-daemon
2020-06-07 22:32 ` bugzilla-daemon
2020-06-07 22:34 ` bugzilla-daemon
2020-06-08 12:59 ` bugzilla-daemon
2020-06-08 13:42 ` bugzilla-daemon
2020-06-08 21:03 ` bugzilla-daemon
2020-06-08 22:51 ` bugzilla-daemon
2020-06-09 19:32 ` bugzilla-daemon
2020-06-09 20:59 ` 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=bug-325-13-EbBX4qrY3x@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--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