From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: "Ravi Bangoria" <ravi.bangoria@amd.com>,
"Andrii Nakryiko" <andrii.nakryiko@gmail.com>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Jiri Olsa" <jolsa@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Ian Rogers" <irogers@google.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
bpf <bpf@vger.kernel.org>, "Manu Bretelle" <chantra@meta.com>,
"Daniel Müller" <deso@posteo.net>,
"Mykola Lysenko" <mykolal@meta.com>
Subject: Re: [BUG] perf test: Regression because of d6e6286a12e7
Date: Thu, 13 Jul 2023 17:57:53 -0300 [thread overview]
Message-ID: <ZLBlUXDxRqzNRup3@kernel.org> (raw)
In-Reply-To: <CAADnVQLpfmJ7yg-QtwfOFATJb=JcSDDxo11JG32KOQ6K=sNp4Q@mail.gmail.com>
Em Wed, Jul 12, 2023 at 11:20:27AM -0700, Alexei Starovoitov escreveu:
> On Wed, Jul 12, 2023 at 8:39 AM Arnaldo Carvalho de Melo
> <acme@kernel.org> wrote:
> >
> > Right, perhaps the libbpf CI could try building perf, preferably with
> > BUILD_BPF_SKEL=1, to enable these tools:
>
>
> That would be great.
> perf experts probably should do pull-req to bpf CI to enable that.
> See slides:
> http://vger.kernel.org/bpfconf2022_material/lsfmmbpf2022-bpf-ci.pdf
>
> "How to contribute?
> Depending on what part of CI you are changing, you can create a pull request to
> https://github.com/kernel-patches/vmtest/
> https://github.com/libbpf/ci
> "
Sure, I still recall Quentin's talk about CI, etc in Dublin, will come
up with something and submit.
- Arnaldo
next prev parent reply other threads:[~2023-07-13 20:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 4:37 [BUG] perf test: Regression because of d6e6286a12e7 Ravi Bangoria
2023-07-07 23:16 ` Andrii Nakryiko
2023-07-10 4:03 ` Ravi Bangoria
2023-07-10 21:36 ` Andrii Nakryiko
2023-07-12 14:08 ` Ravi Bangoria
2023-07-12 15:39 ` Arnaldo Carvalho de Melo
2023-07-12 18:20 ` Alexei Starovoitov
2023-07-13 20:57 ` Arnaldo Carvalho de Melo [this message]
2023-07-14 18:15 ` Mykola Lysenko
[not found] ` <SA1PR15MB46099ABDC08009096019B5B4CBF7A@SA1PR15MB4609.namprd15.prod.outlook.com>
2023-09-14 21:54 ` Ian Rogers
2023-09-17 9:22 ` Arnaldo Carvalho de Melo
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=ZLBlUXDxRqzNRup3@kernel.org \
--to=acme@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chantra@meta.com \
--cc=deso@posteo.net \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mykolal@meta.com \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@amd.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).