From: SeongJae Park <sj38.park@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: SeongJae Park <sj38.park@gmail.com>, perfbook@vger.kernel.org
Subject: Re: [PATCH 7/7] future/formalregress: Use SEL4 consistently
Date: Sat, 2 Dec 2023 13:32:09 -0800 [thread overview]
Message-ID: <20231202213209.22836-1-sj@kernel.org> (raw)
In-Reply-To: <50a43146-d9dd-45fe-8569-0e33314a4648@paulmck-laptop>
On Sat, 2 Dec 2023 11:29:45 -0800 "Paul E. McKenney" <paulmck@kernel.org> wrote:
> On Sat, Dec 02, 2023 at 09:26:14AM -0800, SeongJae Park wrote:
> > formalregress.tex is using mixed use of SEL4 and seL4. SEL4 is used 8
> > times, while seL4 is used twice over the entire repository. Use SEL4
> > for the consistency. Note that use of seL4 in swtools.bib is not
> > changed by this commit.
> >
> > Signed-off-by: SeongJae Park <sj38.park@gmail.com>
>
> Nice, thank you!
You're very welcome, Paul!
>
> I queued and pushed all but this one. Their website [1] says seL4.
> At least I *think* that this is their website.
Agreed :)
>
> Either way, I agree that this should be consistent with their naming.
Sure, I will send a new revision soon.
>
> On the Promela/spin change, should a similar change be applied in the
> Formal Verification chapter?
I already finished the translation of the chapter, but hopefully I will revisit
it soon :) Don't wait for me, though!
Thanks,
SJ
>
> Thanx, Paul
>
> [1] https://sel4.systems/
>
> > ---
> > future/formalregress.tex | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/future/formalregress.tex b/future/formalregress.tex
> > index b1a39b29..40bf2b35 100644
> > --- a/future/formalregress.tex
> > +++ b/future/formalregress.tex
> > @@ -701,7 +701,7 @@ so they are all yellow with question marks.
> > Indeed there are!
> > This table focuses on those that Paul has used, but others are
> > proving to be useful.
> > - Formal verification has been heavily used in the seL4
> > + Formal verification has been heavily used in the SEL4
> > project~\cite{ThomasSewell2013L4binaryVerification},
> > and its tools can now handle modest levels of concurrency.
> > More recently, Catalin Marinas used Lamport's
> > --
> > 2.17.1
> >
> >
next prev parent reply other threads:[~2023-12-02 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 17:26 [PATCH 0/7] future: Trivial fixups SeongJae Park
2023-12-02 17:26 ` [PATCH 1/7] future/tm: Remove unnecessary spaces SeongJae Park
2023-12-02 17:26 ` [PATCH 2/7] future/tm: Add introduction of TM-availabe options for locking SeongJae Park
2023-12-02 17:26 ` [PATCH 3/7] future/tm: Consistently add dash between reader and writer of reader-writer lock SeongJae Park
2023-12-02 17:26 ` [PATCH 4/7] future/htm: Remove unnecessary extra 'and' SeongJae Park
2023-12-02 17:26 ` [PATCH 5/7] future/htm: Use \co{} in favor of $$ SeongJae Park
2023-12-02 17:26 ` [PATCH 6/7] future/formalregress: Use \co{} for spin SeongJae Park
2023-12-02 17:26 ` [PATCH 7/7] future/formalregress: Use SEL4 consistently SeongJae Park
2023-12-02 19:29 ` Paul E. McKenney
2023-12-02 21:32 ` SeongJae Park [this message]
2023-12-02 23:35 ` 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=20231202213209.22836-1-sj@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.