From: Leon Hwang <hffilwlqm@gmail.com>
To: Cupertino Miranda <cupertino.miranda@oracle.com>
Cc: bpf@vger.kernel.org,
"Jose E. Marchesi" <jose.marchesi@oracle.com>,
david.faust@oracle.com
Subject: Re: Question regarding "Add testcases for tailcall hierarchy fixing"
Date: Fri, 2 Aug 2024 10:28:59 +0800 [thread overview]
Message-ID: <4ee78b54-04c1-4c76-883c-8ddcbb7d2b3f@gmail.com> (raw)
In-Reply-To: <871q38gk6g.fsf@oracle.com>
On 2/8/24 02:41, Cupertino Miranda wrote:
>
> Hi Leon,
>
> In the following commit:
>
> commit b83b936f3e9a3c63896852198a1814e90e68eef5
> Author: Leon Hwang <hffilwlqm@gmail.com>
>
> selftests/bpf: Add testcases for tailcall hierarchy fixing
>
> you created 2 tests files that contain the following inline assembly.
>
> asm volatile (""::"r+"(ret));
>
> I presume the actual intent is to force the unused ret variable to
> exist as a register.
>
> When compiling that line in GCC it produces the following error:
>
> progs/tailcall_bpf2bpf_hierarchy2.c: In function 'tailcall_bpf2bpf_hierarchy_2':
> progs/tailcall_bpf2bpf_hierarchy2.c:66:9: error: input operand constraint contains '+'
> 66 | asm volatile (""::"r+"(ret));
> | ^~~
>
> After analysing the reasoning behind the error, the plausible solution
> is to change the constraint to "+r" and move it from the input operands
> list to output operands, i.e:
>
> asm volatile ("":"+r"(ret));
>
> Can you please confirm that this change would be complient with the test
> semantics ?
Hi Cupertino,
The purpose of this "asm volatile" is to prevent that compiler optimizes
the return value of the function by returning 0 directly and maybe
eliminating bpf_tail_call_static().
Therefore, it's better to use "__sink()" defined in "bpf_misc.h":
/* make it look to compiler like value is read and written */
#define __sink(expr) asm volatile("" : "+g"(expr))
Here's the diff:
diff --git
a/tools/testing/selftests/bpf/progs/tailcall_bpf2bpf_hierarchy2.c
b/tools/testing/selftests/bpf/progs/tailcall_bpf2bpf_hierarchy2.c
index 37604b0b97af..72fd0d577506 100644
--- a/tools/testing/selftests/bpf/progs/tailcall_bpf2bpf_hierarchy2.c
+++ b/tools/testing/selftests/bpf/progs/tailcall_bpf2bpf_hierarchy2.c
@@ -58,12 +58,12 @@ __retval(33)
SEC("tc")
int tailcall_bpf2bpf_hierarchy_2(struct __sk_buff *skb)
{
- volatile int ret = 0;
+ int ret = 0;
subprog_tail0(skb);
subprog_tail1(skb);
- asm volatile (""::"r+"(ret));
+ __sink(ret);
return (count1 << 16) | count0;
}
diff --git
a/tools/testing/selftests/bpf/progs/tailcall_bpf2bpf_hierarchy3.c
b/tools/testing/selftests/bpf/progs/tailcall_bpf2bpf_hierarchy3.c
index 0cdbb781fcbc..a7fb91cb05b7 100644
--- a/tools/testing/selftests/bpf/progs/tailcall_bpf2bpf_hierarchy3.c
+++ b/tools/testing/selftests/bpf/progs/tailcall_bpf2bpf_hierarchy3.c
@@ -51,11 +51,11 @@ __retval(33)
SEC("tc")
int tailcall_bpf2bpf_hierarchy_3(struct __sk_buff *skb)
{
- volatile int ret = 0;
+ int ret = 0;
bpf_tail_call_static(skb, &jmp_table0, 0);
- asm volatile (""::"r+"(ret));
+ __sink(ret);
return ret;
}
Thanks,
Leon
>
> Regards,
> Cupertino
prev parent reply other threads:[~2024-08-02 2:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 18:41 Question regarding "Add testcases for tailcall hierarchy fixing" Cupertino Miranda
2024-08-02 2:28 ` Leon Hwang [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=4ee78b54-04c1-4c76-883c-8ddcbb7d2b3f@gmail.com \
--to=hffilwlqm@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=cupertino.miranda@oracle.com \
--cc=david.faust@oracle.com \
--cc=jose.marchesi@oracle.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