From: dthaler1968@googlemail.com
To: "'Yonghong Song'" <yonghong.song@linux.dev>
Cc: <bpf@ietf.org>, <bpf@vger.kernel.org>
Subject: RE: Sign extension ISA question
Date: Tue, 16 Jan 2024 17:56:24 -0800 [thread overview]
Message-ID: <095f01da48e8$611687d0$23439770$@gmail.com> (raw)
In-Reply-To: <829aa552-b04e-4f08-9874-b3f929741852@linux.dev>
Yonghong Song <yonghong.song@linux.dev> wrote:
> > Is there any semantic difference between the following two instructions?
> >
> > {.opcode = BPF_ALU64 | BPF_MOV | BPF_K, .offset = 0, .imm = -1}
>
> This is supported. Sign extension of -1 will be put into ALU64 reg.
>
> >
> > {.opcode = BPF_ALU64 | BPF_MOVSX | BPF_K, .offset = 32, .imm = -1}
>
> This is not supported. BPF_MOVSX only supports register extension.
> We should make it clear in the doc.
Is that limitation a Linux-specific implementation statement? (i.e., put into
linux-notes.txt)
Or that the meaning is undefined for all runtimes and could be used
for some other purpose in the future? (i.e., put into instruction-set.rst)
For now I'll interpret it as the latter.
Thanks,
Dave
WARNING: multiple messages have this Message-ID (diff)
From: dthaler1968=40googlemail.com@dmarc.ietf.org
To: "'Yonghong Song'" <yonghong.song@linux.dev>
Cc: <bpf@ietf.org>, <bpf@vger.kernel.org>
Subject: Re: [Bpf] Sign extension ISA question
Date: Tue, 16 Jan 2024 17:56:24 -0800 [thread overview]
Message-ID: <095f01da48e8$611687d0$23439770$@gmail.com> (raw)
Message-ID: <20240117015624.4j4FJ5RWqqh5J-PyEYHo_ed2O7bT-Ju3X-SD31Y6pwM@z> (raw)
In-Reply-To: <829aa552-b04e-4f08-9874-b3f929741852@linux.dev>
Yonghong Song <yonghong.song@linux.dev> wrote:
> > Is there any semantic difference between the following two instructions?
> >
> > {.opcode = BPF_ALU64 | BPF_MOV | BPF_K, .offset = 0, .imm = -1}
>
> This is supported. Sign extension of -1 will be put into ALU64 reg.
>
> >
> > {.opcode = BPF_ALU64 | BPF_MOVSX | BPF_K, .offset = 32, .imm = -1}
>
> This is not supported. BPF_MOVSX only supports register extension.
> We should make it clear in the doc.
Is that limitation a Linux-specific implementation statement? (i.e., put into
linux-notes.txt)
Or that the meaning is undefined for all runtimes and could be used
for some other purpose in the future? (i.e., put into instruction-set.rst)
For now I'll interpret it as the latter.
Thanks,
Dave
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next prev parent reply other threads:[~2024-01-17 1:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 20:38 [Bpf] Sign extension ISA question dthaler1968=40googlemail.com
2024-01-16 20:55 ` dthaler1968
2024-01-16 20:55 ` [Bpf] " dthaler1968=40googlemail.com
2024-01-16 22:34 ` Yonghong Song
2024-01-16 22:34 ` [Bpf] " Yonghong Song
2024-01-17 1:56 ` dthaler1968 [this message]
2024-01-17 1:56 ` dthaler1968=40googlemail.com
2024-01-17 3:48 ` Yonghong Song
2024-01-17 3:48 ` [Bpf] " Yonghong Song
2024-01-24 2:07 ` Jump instructions clarification dthaler1968
2024-01-24 2:07 ` [Bpf] " dthaler1968=40googlemail.com
2024-01-24 19:33 ` Yonghong Song
2024-01-24 19:33 ` [Bpf] " Yonghong Song
2024-01-26 1:12 ` 64-bit immediate " dthaler1968
2024-01-26 1:12 ` [Bpf] " dthaler1968=40googlemail.com
2024-01-26 5:34 ` Yonghong Song
2024-01-26 5:34 ` [Bpf] " Yonghong Song
2024-01-26 22:27 ` dthaler1968
2024-01-26 22:27 ` [Bpf] " dthaler1968=40googlemail.com
2024-01-27 3:41 ` Yonghong Song
2024-01-27 3:41 ` [Bpf] " Yonghong Song
2024-01-27 6:56 ` dthaler1968
2024-01-27 6:56 ` [Bpf] " dthaler1968=40googlemail.com
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='095f01da48e8$611687d0$23439770$@gmail.com' \
--to=dthaler1968@googlemail.com \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=yonghong.song@linux.dev \
/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).