public inbox for linux-api@vger.kernel.org
 help / color / mirror / Atom feed
From: Wu Hao <hao.wu@intel.com>
To: mdf@kernel.org, will@kernel.org, mark.rutland@arm.com,
	gregkh@linuxfoundation.org, linux-fpga@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: linux-api@vger.kernel.org, atull@kernel.org, yilun.xu@intel.com
Subject: Re: [PATCH v8 0/2] add performance reporting support to FPGA DFL drivers
Date: Mon, 9 Mar 2020 15:47:58 +0800	[thread overview]
Message-ID: <20200309074758.GA4295@hao-dev> (raw)
In-Reply-To: <1582503707-10737-1-git-send-email-hao.wu@intel.com>

Hi Will,

Just a gentle ping. Do you have Any comments to this new version?

Hao

On Mon, Feb 24, 2020 at 08:21:45AM +0800, Wu Hao wrote:
> Hi all,
> 
> This patchset adds performance reporting support for FPGA DFL drivers. It
> introduces one pmu to expose userspace interfaces via standard perf API.
> User could use standard perf tool to access perf events exposed via pmu.
> 
> This patchset is generated based on 5.6-rc2.
> 
> Main changes from v7:
>  - rename pmu name from "fme%d" to "dfl_fme%d".
>  - monitor cpu hotplug for cpumask sysfs and update cpumask sysfs doc.
>  - add extra read for 64bit counter registers to avoid 2-32bit readl issue.
> 
> Main changes from v6:
>  - add a new ABI/testing/ sysfs documentation in patch #2.
>  - fix a warning reported by kbuild in patch #2.
> 
> Main changes from v5:
>  - use dev_ext_attribute instead of fme_perf_event_attr.
>  - use is_visible function to decide which events to expose per
>    hardware capability, and add event_init checking for all events.
> 
> Main changes from v4:
>  - rebase and clean up.
>  - update Kconfig for PERF_EVENTS dependency.
> 
> Main changes from v3:
>  - add more descriptions in doc, including how to use perf tool for these
>    hardware counters. (patch #1)
>  - use standard perf API instead of sysfs entries. (patch #2)
> 
> Wu Hao (1):
>   fpga: dfl: fme: add performance reporting support
> 
> Xu Yilun (1):
>   Documentation: fpga: dfl: add description for performance reporting
>     support
> 
>  .../testing/sysfs-bus-event_source-devices-dfl_fme |  104 ++
>  Documentation/fpga/dfl.rst                         |   84 ++
>  drivers/fpga/Kconfig                               |    2 +-
>  drivers/fpga/Makefile                              |    1 +
>  drivers/fpga/dfl-fme-main.c                        |    4 +
>  drivers/fpga/dfl-fme-perf.c                        | 1021 ++++++++++++++++++++
>  drivers/fpga/dfl-fme.h                             |    2 +
>  drivers/fpga/dfl.h                                 |    2 +
>  8 files changed, 1219 insertions(+), 1 deletion(-)
>  create mode 100644 Documentation/ABI/testing/sysfs-bus-event_source-devices-dfl_fme
>  create mode 100644 drivers/fpga/dfl-fme-perf.c
> 
> -- 
> 1.8.3.1

      parent reply	other threads:[~2020-03-09  8:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24  0:21 [PATCH v8 0/2] add performance reporting support to FPGA DFL drivers Wu Hao
2020-02-24  0:21 ` [PATCH v8 1/2] Documentation: fpga: dfl: add description for performance reporting support Wu Hao
2020-02-24  0:21 ` [PATCH v8 2/2] fpga: dfl: fme: add " Wu Hao
2020-03-09  7:47 ` Wu Hao [this message]

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=20200309074758.GA4295@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=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