Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: "Immanuel, Yehowshua U" <yimmanuel3@gatech.edu>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] Advanced Topics on RISCV
Date: Tue, 24 Mar 2020 11:51:56 +0000
Message-ID: <0F80A1BC-0241-49FE-B374-B4F1D8F3F5BD@gatech.edu> (raw)

I’ve read through the Spike page and a good portion of the simpleV page.

My two goals at the moment are:
1. Understand how RISCV handles multiple processes and does page walking
2. Understand how multicore ROSCV would work

I’m hoping to play with FreeRTOS soon so I can run through its codebase for setting up page tables.
Also, do you know if spike tests the special instructions like exception instructions? Also, what RISCV instructions would a kernel use to set up the pagetables?

Lastly, do you know any good resources for intro to multicore systems? RISCV doesn’t seem to have any multicore specific instructions. My current questions would include things like:

1. How can the kernel assign tasks to a certain core? If you have a process with multiple threads, it would make sense to spread out the threads among available processors instead of concentrating them on a single core. How might this work with respect to RISCV?

2. Does the hardware ensure cache coherency - that is - externally - software sees one big cache all though I imagine each core would have a local cache that would have to communicate with other caches?

Yehowshua
_______________________________________________
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
2020-03-24 11:51 Immanuel, Yehowshua U [this message]
2020-03-24 12:06 ` Luke Kenneth Casson Leighton
2020-03-24 12:58   ` Immanuel, Yehowshua U
2020-03-24 12:23 ` Jean-Paul Chaput
2020-03-24 13:00   ` Immanuel, Yehowshua U
2020-03-24 13:08     ` Jean-Paul Chaput

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=0F80A1BC-0241-49FE-B374-B4F1D8F3F5BD@gatech.edu \
    --to=yimmanuel3@gatech.edu \
    --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