From: Edward Cree <ecree.xilinx@gmail.com>
To: Eduard Zingerman <eddyz87@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org
Cc: andrii@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
kernel-team@fb.com, yhs@fb.com
Subject: Re: [PATCH bpf-next v3 1/1] docs/bpf: Add description of register liveness tracking algorithm
Date: Thu, 2 Feb 2023 09:25:29 +0000 [thread overview]
Message-ID: <b6966500-c25f-cc31-5d61-eabf54f3e3b6@gmail.com> (raw)
In-Reply-To: <cc8561139d020136d0bfa01684317ef25996d184.camel@gmail.com>
On 01/02/2023 18:28, Eduard Zingerman wrote:
> How about the following?
>
> ---- 8< ---------------------------
>
> For each processed instruction, the verifier tracks read and written
> registers and stack slots. The main idea of the algorithm is that read
> marks propagate back along the state parentage chain until they hit a
> write mark, which 'screens off' earlier states from the read. The
> information about reads is propagated by function ``mark_reg_read()``
> which could be summarized as follows::
>
> ---- >8 ---------------------------
SGTM.
prev parent reply other threads:[~2023-02-02 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 18:11 [PATCH bpf-next v3 0/1] docs/bpf: Add description of register liveness tracking algorithm Eduard Zingerman
2023-01-31 18:11 ` [PATCH bpf-next v3 1/1] " Eduard Zingerman
2023-02-01 11:00 ` Edward Cree
2023-02-01 15:14 ` Eduard Zingerman
2023-02-01 16:13 ` Edward Cree
2023-02-01 18:28 ` Eduard Zingerman
2023-02-02 9:25 ` Edward Cree [this message]
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=b6966500-c25f-cc31-5d61-eabf54f3e3b6@gmail.com \
--to=ecree.xilinx@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=yhs@fb.com \
/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 NNTP newsgroup(s).