From: Greg KH <gregkh@linuxfoundation.org>
To: kajoljain <kjain@linux.ibm.com>
Cc: will@kernel.org, hao.wu@intel.com, mark.rutland@arm.com,
trix@redhat.com, yilun.xu@intel.com, mdf@kernel.org,
linux-fpga@vger.kernel.org, maddy@linux.vnet.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] fpga: dfl: fme: Fix cpu hotplug issue in performance reporting
Date: Tue, 29 Jun 2021 09:27:00 +0200 [thread overview]
Message-ID: <YNrLRLyyUeDemxTS@kroah.com> (raw)
In-Reply-To: <adc3b013-d39b-a183-dfce-86ca857949b8@linux.ibm.com>
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@vger.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>
next prev parent reply other threads:[~2021-06-29 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 10:17 [PATCH] fpga: dfl: fme: Fix cpu hotplug issue in performance reporting Kajol Jain
2021-06-29 7:15 ` kajoljain
2021-06-29 7:27 ` Greg KH [this message]
2021-06-29 8:08 ` 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=YNrLRLyyUeDemxTS@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=hao.wu@intel.com \
--cc=kjain@linux.ibm.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.vnet.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 \
/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;
as well as URLs for NNTP newsgroup(s).