From: Song Liu <songliubraving@fb.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: KP Singh <kpsingh@chromium.org>,
open list <linux-kernel@vger.kernel.org>,
bpf <bpf@vger.kernel.org>, Florent Revest <revest@google.com>,
"Alexei Starovoitov" <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"Martin Lau" <kafai@fb.com>, Yonghong Song <yhs@fb.com>,
Florent Revest <revest@chromium.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>
Subject: Re: [PATCH v2] samples/bpf: Add a workaround for asm_inline
Date: Wed, 2 Oct 2019 21:05:12 +0000 [thread overview]
Message-ID: <E7A6B893-9E4B-4C22-A0CC-833AF45AF460@fb.com> (raw)
In-Reply-To: <CAEf4BzY4tXd=sHbkN=Bbhj5=7=W_PBs_BB=wjGJ4-bHenKz6sw@mail.gmail.com>
> On Oct 2, 2019, at 1:22 PM, Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
>
> On Wed, Oct 2, 2019 at 12:17 PM KP Singh <kpsingh@chromium.org> wrote:
>>
>> From: KP Singh <kpsingh@google.com>
>>
>> This was added in:
>>
>> commit eb111869301e ("compiler-types.h: add asm_inline definition")
>>
>> and breaks samples/bpf as clang does not support asm __inline.
>>
>> Co-developed-by: Florent Revest <revest@google.com>
>> Signed-off-by: Florent Revest <revest@google.com>
>> Signed-off-by: KP Singh <kpsingh@google.com>
>> ---
>>
>> Changes since v1:
>>
>> - Dropped the rename from asm_workaround.h to asm_goto_workaround.h
>> - Dropped the fix for task_fd_query_user.c as it is updated in
>> https://lore.kernel.org/bpf/20191001112249.27341-1-bjorn.topel@gmail.com/
>>
>> samples/bpf/asm_goto_workaround.h | 13 ++++++++++++-
>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/samples/bpf/asm_goto_workaround.h b/samples/bpf/asm_goto_workaround.h
>> index 7409722727ca..7048bb3594d6 100644
>> --- a/samples/bpf/asm_goto_workaround.h
>> +++ b/samples/bpf/asm_goto_workaround.h
>> @@ -3,7 +3,8 @@
>> #ifndef __ASM_GOTO_WORKAROUND_H
>> #define __ASM_GOTO_WORKAROUND_H
>>
>> -/* this will bring in asm_volatile_goto macro definition
>> +/*
>> + * This will bring in asm_volatile_goto and asm_inline macro definitions
>> * if enabled by compiler and config options.
>> */
>> #include <linux/types.h>
>> @@ -13,5 +14,15 @@
>> #define asm_volatile_goto(x...) asm volatile("invalid use of asm_volatile_goto")
>> #endif
>>
>> +/*
>> + * asm_inline is defined as asm __inline in "include/linux/compiler_types.h"
>> + * if supported by the kernel's CC (i.e CONFIG_CC_HAS_ASM_INLINE) which is not
>> + * supported by CLANG.
>> + */
>> +#ifdef asm_inline
>> +#undef asm_inline
>> +#define asm_inline asm
>> +#endif
>
> Would it be better to just #undef CONFIG_CC_HAS_ASM_INLINE for BPF programs?
I guess that is still useful when gcc fully support BPF?
Thanks,
Song
next prev parent reply other threads:[~2019-10-02 21:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 19:16 [PATCH v2] samples/bpf: Add a workaround for asm_inline KP Singh
2019-10-02 20:22 ` Andrii Nakryiko
2019-10-02 21:05 ` Song Liu [this message]
2019-10-02 21:13 ` Andrii Nakryiko
2019-10-02 20:52 ` Song Liu
2019-10-03 15:40 ` Daniel Borkmann
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=E7A6B893-9E4B-4C22-A0CC-833AF45AF460@fb.com \
--to=songliubraving@fb.com \
--cc=acme@redhat.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=revest@chromium.org \
--cc=revest@google.com \
--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).