From: Jijie Shao <shaojijie@huawei.com>
To: Will Deacon <will@kernel.org>
Cc: <shaojijie@huawei.com>, <jonathan.cameron@huawei.com>,
<mark.rutland@arm.com>, <chenhao418@huawei.com>,
<shenjian15@huawei.com>, <wangjie125@huawei.com>,
<liuyonglong@huawei.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH drivers/perf: hisi: 2/2] drivers/perf: hisi: fix set wrong filter mode for running events issue
Date: Wed, 23 Aug 2023 10:33:07 +0800 [thread overview]
Message-ID: <7fb893ab-9f82-4dd6-ccf6-2432e9e1e769@huawei.com> (raw)
In-Reply-To: <20230821120440.GB19617@willie-the-truck>
on 2023/8/21 20:04, Will Deacon wrote:
>> - return tc_id != HNS3_PMU_FILTER_ALL_TC;
>> + return (tc_id != HNS3_PMU_FILTER_ALL_TC) && (!bdf);
>> }
> Sorry, but I'm struggling to see how this correlates with your example
> in the commit message, which implies that it's the config of 0x3 causing
> the problem rather than the bdf.
>
> Please can you explain the problem in more detail?
>
> Thanks,
>
> Will
We'll send the v2 patch to add more details.
Jijie Shao
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-08-23 2:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 9:46 [PATCH drivers/perf: hisi: 0/2] There are some bugfix for the hisi perf driver Jijie Shao
2023-08-16 9:46 ` [PATCH drivers/perf: hisi: 1/2] drivers/perf: hisi: hns3: default use hardware event 0 as group leader event Jijie Shao
2023-08-21 11:58 ` Will Deacon
2023-08-23 2:38 ` Jijie Shao
2023-08-16 9:46 ` [PATCH drivers/perf: hisi: 2/2] drivers/perf: hisi: fix set wrong filter mode for running events issue Jijie Shao
2023-08-21 12:04 ` Will Deacon
2023-08-21 12:08 ` Will Deacon
2023-08-21 12:32 ` Jijie Shao
2023-08-23 2:33 ` Jijie Shao [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=7fb893ab-9f82-4dd6-ccf6-2432e9e1e769@huawei.com \
--to=shaojijie@huawei.com \
--cc=chenhao418@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=mark.rutland@arm.com \
--cc=shenjian15@huawei.com \
--cc=wangjie125@huawei.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox