From: Dave Thaler <dthaler@microsoft.com>
To: "bpf@vger.kernel.org" <bpf@vger.kernel.org>
Cc: "dthaler1968@googlemail.com" <dthaler1968@googlemail.com>
Subject: RE: [PATCH 1/9] bpf, docs: Add note about type convention
Date: Mon, 17 Oct 2022 20:42:13 +0000 [thread overview]
Message-ID: <DM4PR21MB3440B73030D09B1F09082807A3299@DM4PR21MB3440.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20221004224745.1430-1-dthaler1968@googlemail.com>
Just checking if there is any more feedback on this patch set,
as I've seen no comments since this set was posted on October 4th
which addresses comments received on the previous submission.
Let me know if I'm missing some step I should be doing as I'm new
to this submission process.
Thanks!
Dave
> -----Original Message-----
> From: dthaler1968@googlemail.com <dthaler1968@googlemail.com>
> Sent: Tuesday, October 4, 2022 3:48 PM
> To: bpf@vger.kernel.org
> Cc: Dave Thaler <dthaler@microsoft.com>
> Subject: [PATCH 1/9] bpf, docs: Add note about type convention
>
> From: Dave Thaler <dthaler@microsoft.com>
>
> Add note about type convention
>
> Signed-off-by: Dave Thaler <dthaler@microsoft.com>
> ---
> Documentation/bpf/instruction-set.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/bpf/instruction-set.rst
> b/Documentation/bpf/instruction-set.rst
> index 4997d2088..6847a4cbf 100644
> --- a/Documentation/bpf/instruction-set.rst
> +++ b/Documentation/bpf/instruction-set.rst
> @@ -7,6 +7,11 @@ eBPF Instruction Set Specification, v1.0
>
> This document specifies version 1.0 of the eBPF instruction set.
>
> +Documentation conventions
> +=========================
> +
> +For brevity, this document uses the type notion "u64", "u32", etc.
> +to mean an unsigned integer whose width is the specified number of bits.
>
> Registers and calling convention
> ================================
> @@ -116,6 +121,8 @@ BPF_END 0xd0 byte swap operations (see `Byte swap
> instructions`_ below)
>
> dst_reg = (u32) dst_reg + (u32) src_reg;
>
> +where '(u32)' indicates truncation to 32 bits.
> +
> ``BPF_ADD | BPF_X | BPF_ALU64`` means::
>
> dst_reg = dst_reg + src_reg
> --
> 2.33.4
next prev parent reply other threads:[~2022-10-17 20:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 22:47 [PATCH 1/9] bpf, docs: Add note about type convention dthaler1968
2022-10-04 22:47 ` [PATCH 2/9] bpf, docs: Fix modulo zero, division by zero, overflow, and underflow dthaler1968
2022-10-04 22:47 ` [PATCH 3/9] bpf, docs: Use consistent names for the same field dthaler1968
2022-10-04 22:47 ` [PATCH 4/9] bpf, docs: Explain helper functions dthaler1968
2022-10-04 22:47 ` [PATCH 5/9] bpf, docs: Add appendix of all opcodes in order dthaler1968
2022-10-04 22:47 ` [PATCH 6/9] bpf, docs: Improve English readability dthaler1968
2022-10-04 22:47 ` [PATCH 7/9] bpf, docs: Add extended 64-bit immediate instructions dthaler1968
2022-10-04 22:47 ` [PATCH 8/9] bpf, docs: Add extended call instructions dthaler1968
2022-10-04 22:47 ` [PATCH 9/9] bpf, docs: Add note about reserved instruction dthaler1968
2022-10-05 9:54 ` kernel test robot
2022-10-17 20:42 ` Dave Thaler [this message]
2022-10-17 21:41 ` [PATCH 1/9] bpf, docs: Add note about type convention Alexei Starovoitov
2022-10-17 23:16 ` Dave Thaler
2022-10-17 23:43 ` Alexei Starovoitov
2022-10-19 18:40 ` Dave Thaler
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=DM4PR21MB3440B73030D09B1F09082807A3299@DM4PR21MB3440.namprd21.prod.outlook.com \
--to=dthaler@microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=dthaler1968@googlemail.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 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.