From: Atish Patra <Atish.Patra@wdc.com>
To: "nikita.shubin@maquefel.me" <nikita.shubin@maquefel.me>
Cc: "mick@ics.forth.gr" <mick@ics.forth.gr>,
"wangkefeng.wang@huawei.com" <wangkefeng.wang@huawei.com>,
"vincent.chen@sifive.com" <vincent.chen@sifive.com>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"alankao@andestech.com" <alankao@andestech.com>,
"nickhu@andestech.com" <nickhu@andestech.com>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"guoren@linux.alibaba.com" <guoren@linux.alibaba.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Anup Patel <Anup.Patel@wdc.com>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"xypron.glpk@gmx.de" <xypron.glpk@gmx.de>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: Not compiling with CONFIG_BPF_SYSCALL enabled
Date: Wed, 1 Sep 2021 15:45:12 +0000 [thread overview]
Message-ID: <a2d921c6e8158327a0a018a075fd94694fd7ab7b.camel@wdc.com> (raw)
In-Reply-To: <20210901103634.26558-1-nikita.shubin@maquefel.me>
On Wed, 2021-09-01 at 13:36 +0300, Nikita Shubin wrote:
> Hello, Atish.
>
> The above series won't compile with CONFIG_BPF_SYSCALL set:
>
> linux/kernel/events/core.c:9912:18: error: assignment to
> 'bpf_user_pt_regs_t *' {aka 'struct user_regs_struct *'}
> from incompatible pointer type 'struct pt_regs *'
> [-Werror=incompatible-pointer-types]
> 9912 | ctx.regs = perf_arch_bpf_user_pt_regs(regs);
>
> Just informing you - hope this is helpful.
Thanks for reporting this. I am spinning the v3 of this series. I will
take look.
>
> Yours,
> Nikita Shubin
>
--
Regards,
Atish
next prev parent reply other threads:[~2021-09-01 15:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 18:43 [RFC v2 0/7] Improve RISC-V Perf support using SBI PMU extension Atish Patra
2021-05-28 18:43 ` [RFC v2 1/7] RISC-V: Remove the current perf implementation Atish Patra
2021-09-01 10:36 ` Not compiling with CONFIG_BPF_SYSCALL enabled Nikita Shubin
2021-09-01 15:45 ` Atish Patra [this message]
2021-05-28 18:44 ` [RFC v2 2/7] RISC-V: Add CSR encodings for all HPMCOUNTERS Atish Patra
2021-05-28 18:44 ` [RFC v2 3/7] RISC-V: Add a perf core library for pmu drivers Atish Patra
2021-05-28 18:44 ` [RFC v2 4/7] RISC-V: Add a simple platform driver for RISC-V legacy perf Atish Patra
2021-05-28 18:44 ` [RFC v2 5/7] RISC-V: Add RISC-V SBI PMU extension definitions Atish Patra
2021-05-28 18:44 ` [RFC v2 6/7] RISC-V: Add perf platform driver based on SBI PMU extension Atish Patra
2021-06-01 13:10 ` Stanislaw Kardach
2021-06-01 15:48 ` Anup Patel
2021-06-01 15:57 ` Anup Patel
2021-06-01 17:08 ` Stanislaw Kardach
2021-05-28 18:44 ` [RFC v2 7/7] Documentation: riscv: Remove the old documentation Atish Patra
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=a2d921c6e8158327a0a018a075fd94694fd7ab7b.camel@wdc.com \
--to=atish.patra@wdc.com \
--cc=Anup.Patel@wdc.com \
--cc=alankao@andestech.com \
--cc=bpf@vger.kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=guoren@linux.alibaba.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=nickhu@andestech.com \
--cc=nikita.shubin@maquefel.me \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=vincent.chen@sifive.com \
--cc=wangkefeng.wang@huawei.com \
--cc=xypron.glpk@gmx.de \
/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
all inboxes | Powered by JetHome®