From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org, Al Grant <al.grant@arm.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
David Ahern <dsahern@kernel.org>, Ian Rogers <irogers@google.com>,
Jin Yao <yao.jin@linux.intel.com>, Leo Yan <leo.yan@linaro.org>,
Like Xu <like.xu@linux.intel.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Sumanth Korikkar <sumanthk@linux.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Wei Li <liwei391@huawei.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL] perf tools fixes for v5.9
Date: Wed, 2 Sep 2020 10:30:34 -0300 [thread overview]
Message-ID: <20200902133034.GB3444345@kernel.org> (raw)
In-Reply-To: <CAHk-=wifL-04oOF3RAbX9Odyfgz4zc4dE=pq-QL+2C-aTxUmqw@mail.gmail.com>
Em Tue, Sep 01, 2020 at 07:43:33PM -0700, Linus Torvalds escreveu:
> On Tue, Sep 1, 2020 at 3:42 PM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> >
> > - The SNOOPX and REMOTE offsets in the data_src bitmask in perf records were
> > were both 37, SNOOPX is 38, fix it.
>
> The kernel uapi side thinks it's 37. What's up?
>
> $ git grep PERF_MEM_SNOOPX_SHIFT
>
> results in
>
> include/uapi/linux/perf_event.h:#define PERF_MEM_SNOOPX_SHIFT 37
> tools/include/uapi/linux/perf_event.h:#define PERF_MEM_SNOOPX_SHIFT 38
Its going in a separate patch, via PeterZ/Ingo,
- Arnaldo
next prev parent reply other threads:[~2020-09-02 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 22:41 [GIT PULL] perf tools fixes for v5.9 Arnaldo Carvalho de Melo
2020-09-02 2:43 ` Linus Torvalds
2020-09-02 13:30 ` Arnaldo Carvalho de Melo [this message]
2020-09-02 2:45 ` pr-tracker-bot
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=20200902133034.GB3444345@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=al.grant@arm.com \
--cc=chris@chris-wilson.co.uk \
--cc=dsahern@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=like.xu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=tmricht@linux.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=yangtiezhu@loongson.cn \
--cc=yao.jin@linux.intel.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