From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@kernel.org
Cc: perfbook@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH v2] future/formalregress: Use seL4 consistently
Date: Sat, 2 Dec 2023 13:33:46 -0800 [thread overview]
Message-ID: <20231202213346.23070-1-sj38.park@gmail.com> (raw)
formalregress.tex is using mixed use of SEL4 and seL4. SEL4 is used 8
times, while seL4 is used twice over the entire repository. That said,
seL4 seems the intended name since their website[1] uses the name. Use
seL4 consistently.
[1] https://sel4.systems/
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
Changes from v1
- Use seL4 instead of SEL4
future/formalregress.tex | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/future/formalregress.tex b/future/formalregress.tex
index b1a39b29..63c9021f 100644
--- a/future/formalregress.tex
+++ b/future/formalregress.tex
@@ -118,23 +118,23 @@ that the compiler is correct.
An alternative approach is to take the binary produced by the C compiler
as input, thereby accounting for any relevant compiler bugs.
This approach has been used in a number of verification efforts,
-perhaps most notably by the SEL4
+perhaps most notably by the seL4
project~\cite{ThomasSewell2013L4binaryVerification}.
\QuickQuiz{
Given the groundbreaking nature of the various verifiers used
- in the SEL4 project, why doesn't this chapter cover them in
+ in the seL4 project, why doesn't this chapter cover them in
more depth?
}\QuickQuizAnswer{
- There can be no doubt that the verifiers used by the SEL4
+ There can be no doubt that the verifiers used by the seL4
project are quite capable.
- However, SEL4 started as a single-CPU project.
- And although SEL4 has gained multi-processor
+ However, seL4 started as a single-CPU project.
+ And although seL4 has gained multi-processor
capabilities, it is currently using very coarse-grained
locking that is similar to the Linux kernel's old
Big Kernel Lock (BKL)\@.
There will hopefully come a day when it makes sense to add
- SEL4's verifiers to a book on parallel programming, but
+ seL4's verifiers to a book on parallel programming, but
this is not yet that day.
}\QuickQuizEnd
--
2.17.1
next reply other threads:[~2023-12-02 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 21:33 SeongJae Park [this message]
2023-12-02 23:35 ` [PATCH v2] future/formalregress: Use seL4 consistently Paul E. McKenney
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=20231202213346.23070-1-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).