From: kajoljain <kjain@linux.ibm.com> To: will@kernel.org, hao.wu@intel.com, mark.rutland@arm.com Cc: trix@redhat.com, yilun.xu@intel.com, mdf@kernel.org, linux-fpga@vger.kernel.org, maddy@linux.ibm.com, atrajeev@linux.vnet.ibm.com, linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, rnsastry@linux.ibm.com, linux-perf-users@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH v3] fpga: dfl: fme: Fix cpu hotplug issue in performance reporting Date: Mon, 2 Aug 2021 13:15:00 +0530 [thread overview] Message-ID: <61495dc0-f496-992c-1d2a-9229a04e6e44@linux.ibm.com> (raw) In-Reply-To: <20210713074216.208391-1-kjain@linux.ibm.com> On 7/13/21 1:12 PM, Kajol Jain wrote: > The performance reporting driver added cpu hotplug > feature but it didn't add pmu migration call in cpu > offline function. > This can create an issue incase the current designated > cpu being used to collect fme pmu data got offline, > as based on current code we are not migrating fme pmu to > new target cpu. Because of that perf will still try to > fetch data from that offline cpu and hence we will not > get counter data. > > Patch fixed this issue by adding pmu_migrate_context call > in fme_perf_offline_cpu function. > > Fixes: 724142f8c42a ("fpga: dfl: fme: add performance reporting support") > Tested-by: Xu Yilun <yilun.xu@intel.com> > Acked-by: Wu Hao <hao.wu@intel.com> > Signed-off-by: Kajol Jain <kjain@linux.ibm.com> > Cc: stable@vger.kernel.org > --- Any update on this patch? Please let me know if any changes required. Thanks, Kajol Jain > drivers/fpga/dfl-fme-perf.c | 2 ++ > 1 file changed, 2 insertions(+) > > --- > Changelog: > v2 -> v3: > - Added Acked-by tag > - Removed comment as suggested by Wu Hao > - Link to patch v2: https://lkml.org/lkml/2021/7/9/143 > > v1 -> v2: > - Add stable@vger.kernel.org in cc list > - Link to patch v1: https://lkml.org/lkml/2021/6/28/275 > > RFC -> PATCH v1 > - Remove RFC tag > - Did nits changes on subject and commit message as suggested by Xu Yilun > - Added Tested-by tag > - Link to rfc patch: https://lkml.org/lkml/2021/6/28/112 > --- > > diff --git a/drivers/fpga/dfl-fme-perf.c b/drivers/fpga/dfl-fme-perf.c > index 4299145ef347..587c82be12f7 100644 > --- a/drivers/fpga/dfl-fme-perf.c > +++ b/drivers/fpga/dfl-fme-perf.c > @@ -953,6 +953,8 @@ static int fme_perf_offline_cpu(unsigned int cpu, struct hlist_node *node) > return 0; > > priv->cpu = target; > + perf_pmu_migrate_context(&priv->pmu, cpu, target); > + > return 0; > } > >
next prev parent reply other threads:[~2021-08-02 7:45 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-13 7:42 Kajol Jain 2021-08-02 7:45 ` kajoljain [this message] 2021-08-02 8:58 ` Moritz Fischer 2021-08-02 11:46 ` kajoljain
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=61495dc0-f496-992c-1d2a-9229a04e6e44@linux.ibm.com \ --to=kjain@linux.ibm.com \ --cc=atrajeev@linux.vnet.ibm.com \ --cc=hao.wu@intel.com \ --cc=linux-fpga@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-perf-users@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=maddy@linux.ibm.com \ --cc=mark.rutland@arm.com \ --cc=mdf@kernel.org \ --cc=rnsastry@linux.ibm.com \ --cc=stable@vger.kernel.org \ --cc=trix@redhat.com \ --cc=will@kernel.org \ --cc=yilun.xu@intel.com \ --subject='Re: [PATCH v3] fpga: dfl: fme: Fix cpu hotplug issue in performance reporting' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).