[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200212100211.GA10436@hao-dev>
Date: Wed, 12 Feb 2020 18:02:11 +0800
From: Wu Hao <hao.wu@...el.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Will Deacon <will@...nel.org>, mdf@...nel.org,
mark.rutland@....com, linux-fpga@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
atull@...nel.org, yilun.xu@...el.com,
Luwei Kang <luwei.kang@...el.com>
Subject: Re: [PATCH v7 2/2] fpga: dfl: fme: add performance reporting support
On Tue, Feb 11, 2020 at 09:30:35PM -0800, Greg KH wrote:
> On Wed, Feb 12, 2020 at 11:19:29AM +0800, Wu Hao wrote:
> > 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/.
>
> No, do not abuse platform drivers, you have a real device, use it.
Sure, thanks for the comments. Then I don't have any other idea to move code to
drivers/perf/ directory, so probably only can live with current code.
Thanks
Hao
Powered by blists - more mailing lists