From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: mpe@ellerman.id.au, Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Cc: kjain@linux.ibm.com, maddy@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V3 1/2] powerpc/perf: Fix the power9 event alternatives array to have correct sort order
Date: Sun, 24 Apr 2022 22:15:22 +1000 [thread overview]
Message-ID: <165080252225.1540533.7252624381403538783.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220419114828.89843-1-atrajeev@linux.vnet.ibm.com>
On Tue, 19 Apr 2022 17:18:27 +0530, Athira Rajeev wrote:
> When scheduling a group of events, there are constraint checks
> done to make sure all events can go in a group. Example, one of
> the criteria is that events in a group cannot use same PMC.
> But platform specific PMU supports alternative event for some
> of the event codes. During perf_event_open, if any event
> group doesn't match constraint check criteria, further lookup
> is done to find alternative event.
>
> [...]
Applied to powerpc/fixes.
[1/2] powerpc/perf: Fix the power9 event alternatives array to have correct sort order
https://git.kernel.org/powerpc/c/0dcad700bb2776e3886fe0a645a4bf13b1e747cd
[2/2] powerpc/perf: Fix the power10 event alternatives array to have correct sort order
https://git.kernel.org/powerpc/c/c6cc9a852f123301d5271f1484df8e961b2b64f1
cheers
prev parent reply other threads:[~2022-04-24 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 11:48 [PATCH V3 1/2] powerpc/perf: Fix the power9 event alternatives array to have correct sort order Athira Rajeev
2022-04-19 11:48 ` [PATCH V3 2/2] powerpc/perf: Fix the power10 " Athira Rajeev
2022-04-24 12:15 ` Michael Ellerman [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=165080252225.1540533.7252624381403538783.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=kjain@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
/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.