[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YNrLRLyyUeDemxTS@kroah.com>
Date: Tue, 29 Jun 2021 09:27:00 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: kajoljain <kjain@...ux.ibm.com>
Cc: will@...nel.org, hao.wu@...el.com, mark.rutland@....com,
trix@...hat.com, yilun.xu@...el.com, mdf@...nel.org,
linux-fpga@...r.kernel.org, maddy@...ux.vnet.ibm.com,
atrajeev@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, rnsastry@...ux.ibm.com,
linux-perf-users@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] fpga: dfl: fme: Fix cpu hotplug issue in performance
reporting
On Tue, Jun 29, 2021 at 12:45:20PM +0530, kajoljain wrote:
>
>
> On 6/28/21 3:47 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.
> >
>
> Adding stable@...r.kernel.org in cc list as suggested by Moritz Fischer.
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
Powered by blists - more mailing lists