From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Kajol Jain <kjain@linux.ibm.com>,
mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org
Cc: atrajeev@linux.vnet.ibm.com, maddy@linux.ibm.com,
disgoel@linux.vnet.ibm.com, rnsastry@linux.ibm.com
Subject: Re: [PATCH 1/2] powerpc/perf: Fix the threshold compare group constraint for power10
Date: Tue, 24 May 2022 21:09:36 +1000 [thread overview]
Message-ID: <165339057636.1718562.13444860575931956627.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220506061015.43916-1-kjain@linux.ibm.com>
On Fri, 6 May 2022 11:40:14 +0530, Kajol Jain wrote:
> Thresh compare bits for a event is used to program thresh compare
> field in Monitor Mode Control Register A (MMCRA: 8-18 bits for power10).
> When scheduling events as a group, all events in that group should
> match value in threshold bits. Otherwise event open for the sibling
> events should fail. But in the current code, incase thresh compare bits are
> not valid, we are not failing in group_constraint function which can result
> in invalid group schduling.
>
> [...]
Applied to powerpc/next.
[1/2] powerpc/perf: Fix the threshold compare group constraint for power10
https://git.kernel.org/powerpc/c/505d31650ba96d6032313480fdb566d289a4698c
[2/2] powerpc/perf: Fix the threshold compare group constraint for power9
https://git.kernel.org/powerpc/c/ab0cc6bbf0c812731c703ec757fcc3fc3a457a34
cheers
prev parent reply other threads:[~2022-05-24 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 6:10 [PATCH 1/2] powerpc/perf: Fix the threshold compare group constraint for power10 Kajol Jain
2022-05-06 6:10 ` [PATCH 2/2] powerpc/perf: Fix the threshold compare group constraint for power9 Kajol Jain
2022-05-17 14:06 ` Athira Rajeev
2022-05-09 5:52 ` [PATCH 1/2] powerpc/perf: Fix the threshold compare group constraint for power10 Athira Rajeev
2022-05-24 11:09 ` 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=165339057636.1718562.13444860575931956627.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.vnet.ibm.com \
--cc=kjain@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=rnsastry@linux.ibm.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 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.