From: Wu Hao <hao.wu@intel.com>
To: Will Deacon <will@kernel.org>
Cc: mdf@kernel.org, mark.rutland@arm.com, gregkh@linuxfoundation.org,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, atull@kernel.org, yilun.xu@intel.com,
Luwei Kang <luwei.kang@intel.com>
Subject: Re: [PATCH v7 2/2] fpga: dfl: fme: add performance reporting support
Date: Wed, 12 Feb 2020 11:19:29 +0800 [thread overview]
Message-ID: <20200212031929.GB5645@hao-dev> (raw)
In-Reply-To: <20200210163400.GA21900@willie-the-truck>
On Mon, Feb 10, 2020 at 04:34:01PM +0000, Will Deacon wrote:
> Hi,
>
> On Mon, Feb 10, 2020 at 11:47:49AM +0800, Wu Hao wrote:
> > This patch adds support for performance reporting private feature
> > for FPGA Management Engine (FME). Now it supports several different
> > performance counters, including 'basic', 'cache', 'fabric', 'vtd'
> > and 'vtd_sip'. It allows user to use standard linux tools to access
> > these performance counters.
>
> I had a quick look at this, and it mostly looks alright to me. Just a few
> high-level comments/questions:
Hi Will
Thanks a lot for the review! :)
>
> - I would still prefer for the PMU drivers to live under drivers/perf/
Hm.. one possible way is to create a platform device, and introduce a new
platform device driver under drivers/perf/.
>
> - You should probably give the PMU a better name than "fme%d", for example
> "intel_fpga_dfl_fme%d".
Sure. as it's not intel only, so will use "fpga_dfl_fme" or "dfl_fme" instead.
>
> - CPU0 can be hotplugged off on non-x86 systems. How do you cope with
> that?
Oh.. then we can't just always return CPU0 for cpumask, have to switch
to another available cpu. Will add code to handle this case in the next
version. Thanks!
>
> - readq() will emit 2x32-bit reads on some architectures. What happens
> in this case?
64bit counter may increase and carry out of bit31 between 2-32bit reads,
we probably need some more code (add extra reads?) to handle this case.
Thanks again for these valuable comments, will try to fix all of them in
the next version. : )
Hao
>
> Will
next prev parent reply other threads:[~2020-02-12 3:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 3:47 [PATCH v7 0/2] add performance reporting support to FPGA DFL drivers Wu Hao
2020-02-10 3:47 ` [PATCH v7 1/2] Documentation: fpga: dfl: add description for performance reporting support Wu Hao
2020-02-10 3:47 ` [PATCH v7 2/2] fpga: dfl: fme: add " Wu Hao
2020-02-10 16:34 ` Will Deacon
2020-02-12 3:19 ` Wu Hao [this message]
2020-02-12 5:30 ` Greg KH
2020-02-12 10:02 ` Wu Hao
2020-02-12 13:20 ` Greg KH
2020-02-13 2:51 ` Wu Hao
2020-02-10 20:56 ` Greg KH
2020-02-12 2:39 ` Wu Hao
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=20200212031929.GB5645@hao-dev \
--to=hao.wu@intel.com \
--cc=atull@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luwei.kang@intel.com \
--cc=mark.rutland@arm.com \
--cc=mdf@kernel.org \
--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).