From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 257] Implement demo Load/Store queueing algorithm
Date: Wed, 22 Apr 2020 08:54:45 +0000
Message-ID: <bug-257-13-TG0ZgoTAxx@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-257-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=257
--- Comment #24 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #23)
> also, we're not doing an SMP core for the october 2020 deadline, because we
> are only doing a single core.
>
> therefore L1 and L2 SMP cache coherency is not needed.
Ok, we can write the code to basically have whatever cache coherency stuff gets
written when getting the memory interface working and not worry about the L2 or
other cores existing at all, treating it as a writethrough transparent cache.
The design I'm working on is integrated closely enough with the L1 cache that
it will still need at least a little of the coherence protocol to support
atomics, but it can be built to have a WishBone interface adaptor.
--
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: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-257-13@https.bugs.libre-soc.org/>
2020-04-22 2:58 ` bugzilla-daemon
2020-04-22 8:30 ` bugzilla-daemon
2020-04-22 8:39 ` bugzilla-daemon
2020-04-22 8:54 ` bugzilla-daemon [this message]
2020-04-22 9:48 ` bugzilla-daemon
2020-04-22 13:06 ` bugzilla-daemon
2020-04-22 13:38 ` bugzilla-daemon
2020-04-29 11:16 ` bugzilla-daemon
2020-04-29 21:39 ` bugzilla-daemon
2020-05-06 0:33 ` bugzilla-daemon
2020-05-06 0:36 ` bugzilla-daemon
2020-03-13 18:40 [libre-riscv-dev] [Bug 257] New: " bugzilla-daemon
2020-03-18 5:23 ` [libre-riscv-dev] [Bug 257] " bugzilla-daemon
2020-03-18 6:59 ` bugzilla-daemon
2020-03-20 11:03 ` bugzilla-daemon
2020-03-20 13:06 ` bugzilla-daemon
2020-03-20 18:34 ` bugzilla-daemon
2020-03-20 19:07 ` bugzilla-daemon
2020-03-20 19:53 ` bugzilla-daemon
2020-03-20 20:21 ` bugzilla-daemon
2020-03-21 0:48 ` bugzilla-daemon
2020-03-21 1:56 ` bugzilla-daemon
2020-03-21 4:12 ` bugzilla-daemon
2020-03-21 15:28 ` bugzilla-daemon
2020-03-21 15:36 ` bugzilla-daemon
2020-03-22 11:37 ` bugzilla-daemon
2020-03-24 11:16 ` bugzilla-daemon
2020-03-24 11:54 ` bugzilla-daemon
2020-03-25 13:07 ` bugzilla-daemon
2020-03-26 17:06 ` bugzilla-daemon
2020-03-26 20:58 ` bugzilla-daemon
2020-03-26 21:23 ` 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-257-13-TG0ZgoTAxx@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