From: Yonghong Song <yonghong.song@linux.dev>
To: Dave Thaler <dthaler1968=40googlemail.com@dmarc.ietf.org>,
bpf@vger.kernel.org
Cc: bpf@ietf.org, Dave Thaler <dthaler1968@gmail.com>
Subject: Re: [Bpf] [PATCH bpf-next] bpf, docs: Clarify that MOVSX is only for BPF_X not BPF_K
Date: Thu, 18 Jan 2024 15:53:01 -0800 [thread overview]
Message-ID: <9fe7008b-2fc2-47ad-879b-53da4d0f9c1d@linux.dev> (raw)
In-Reply-To: <20240118232954.27206-1-dthaler1968@gmail.com>
On 1/18/24 3:29 PM, Dave Thaler wrote:
> Per discussion on the mailing list at
> https://mailarchive.ietf.org/arch/msg/bpf/uQiqhURdtxV_ZQOTgjCdm-seh74/
> the MOVSX operation is only defined to support register extension.
>
> The document didn't previously state this and incorrectly implied
> that one could use an immediate value.
>
> Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
Acked-by: Yonghong Song <yonghong.song@linux.dev>
WARNING: multiple messages have this Message-ID (diff)
From: Yonghong Song <yonghong.song@linux.dev>
To: Dave Thaler <dthaler1968=40googlemail.com@dmarc.ietf.org>,
bpf@vger.kernel.org
Cc: bpf@ietf.org, Dave Thaler <dthaler1968@gmail.com>
Subject: Re: [Bpf] [PATCH bpf-next] bpf, docs: Clarify that MOVSX is only for BPF_X not BPF_K
Date: Thu, 18 Jan 2024 15:53:01 -0800 [thread overview]
Message-ID: <9fe7008b-2fc2-47ad-879b-53da4d0f9c1d@linux.dev> (raw)
Message-ID: <20240118235301.Ii9BGjN7yEoTVNSoZgoX2LUGlRiIls_oSMwNGxOKxhU@z> (raw)
In-Reply-To: <20240118232954.27206-1-dthaler1968@gmail.com>
On 1/18/24 3:29 PM, Dave Thaler wrote:
> Per discussion on the mailing list at
> https://mailarchive.ietf.org/arch/msg/bpf/uQiqhURdtxV_ZQOTgjCdm-seh74/
> the MOVSX operation is only defined to support register extension.
>
> The document didn't previously state this and incorrectly implied
> that one could use an immediate value.
>
> Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
Acked-by: Yonghong Song <yonghong.song@linux.dev>
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next prev parent reply other threads:[~2024-01-18 23:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 23:29 [PATCH bpf-next] bpf, docs: Clarify that MOVSX is only for BPF_X not BPF_K Dave Thaler
2024-01-18 23:29 ` [Bpf] " Dave Thaler
2024-01-18 23:45 ` David Vernet
2024-01-18 23:45 ` David Vernet
2024-01-18 23:53 ` Yonghong Song [this message]
2024-01-18 23:53 ` Yonghong Song
2024-01-23 23:40 ` patchwork-bot+netdevbpf
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=9fe7008b-2fc2-47ad-879b-53da4d0f9c1d@linux.dev \
--to=yonghong.song@linux.dev \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=dthaler1968=40googlemail.com@dmarc.ietf.org \
--cc=dthaler1968@gmail.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