From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf auxtrace: Fix auxtrace queue conflict
Date: Tue, 9 Mar 2021 09:35:42 -0300 [thread overview]
Message-ID: <YEdrngHYJh3L6zXH@kernel.org> (raw)
In-Reply-To: <20210308165437.GA203350@tassilo.jf.intel.com>
Em Mon, Mar 08, 2021 at 08:54:37AM -0800, Andi Kleen escreveu:
> On Mon, Mar 08, 2021 at 05:11:43PM +0200, Adrian Hunter wrote:
> > The only requirement of an auxtrace queue is that the buffers are in
> > time order. That is achieved by making separate queues for separate
> > perf buffer or AUX area buffer mmaps.
> >
> > That generally means a separate queue per cpu for per-cpu contexts,
> > and a separate queue per thread for per-task contexts.
> >
> > When buffers are added to a queue, perf checks that the buffer cpu
> > and thread id (tid) match the queue cpu and thread id.
> >
> > However, generally, that need not be true, and perf will queue
> > buffers correctly anyway, so the check is not needed.
> >
> > In addition, the check gets erroneously hit when using sample mode
> > to trace multiple threads.
> >
> > Consequently, fix that case by removing the check.
>
> Thanks!
>
> Reviewed-by: Andi Kleen <ak@linux.intel.com>
Thanks, applied.
- Arnaldo
prev parent reply other threads:[~2021-03-09 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 15:11 [PATCH] perf auxtrace: Fix auxtrace queue conflict Adrian Hunter
2021-03-08 16:54 ` Andi Kleen
2021-03-09 12:35 ` Arnaldo Carvalho de Melo [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=YEdrngHYJh3L6zXH@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.