linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wu Hao <hao.wu@intel.com>
To: mdf@kernel.org, will@kernel.org, mark.rutland@arm.com,
	linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: linux-api@vger.kernel.org, atull@kernel.org,
	gregkh@linuxfoundation.org, hao.wu@intel.com
Subject: Re: [PATCH v6 0/2] add performance reporting support to FPGA DFL drivers
Date: Mon, 25 Nov 2019 11:34:12 +0800	[thread overview]
Message-ID: <20191125033412.GB890@hao-dev> (raw)
In-Reply-To: <1573622695-25607-1-git-send-email-hao.wu@intel.com>

On Wed, Nov 13, 2019 at 01:24:53PM +0800, Wu Hao wrote:
> Hi Moritz and all,

Hi Will and Mark,

Could you please help us on review this patchset? as this patchset mainly 
introduced a new perf driver following the similar way as drivers/perf/*.

Hi Moritz,

Could you please help us on review the other parts?

This patchset has been submitted for a long time but didn't receive any
comment after v4. we appreciate any review comments! thanks in advance. :)


Hao

> 
> 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 fpga/for-next branch.
> 
> 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
> 
>  Documentation/fpga/dfl.rst  |  83 ++++
>  drivers/fpga/Makefile       |   1 +
>  drivers/fpga/dfl-fme-main.c |   4 +
>  drivers/fpga/dfl-fme-perf.c | 943 ++++++++++++++++++++++++++++++++++++++++++++
>  drivers/fpga/dfl-fme.h      |   2 +
>  drivers/fpga/dfl.h          |   2 +
>  6 files changed, 1035 insertions(+)
>  create mode 100644 drivers/fpga/dfl-fme-perf.c
> 
> -- 
> 1.8.3.1

  parent reply	other threads:[~2019-11-25  3:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13  5:24 [PATCH v6 0/2] add performance reporting support to FPGA DFL drivers Wu Hao
2019-11-13  5:24 ` [PATCH v6 1/2] Documentation: fpga: dfl: add description for performance reporting support Wu Hao
2019-11-13  5:24 ` [PATCH v6 2/2] fpga: dfl: fme: add " Wu Hao
2019-11-27  1:45   ` Moritz Fischer
2019-11-25  3:34 ` Wu Hao [this message]
2019-11-25  8:01   ` [PATCH v6 0/2] add performance reporting support to FPGA DFL drivers Will Deacon
2019-11-25  8:08     ` Wu Hao
2019-12-09  2:45       ` Wu Hao
2019-12-16  1:01         ` Xu Yilum
2020-01-06  2:37           ` Wu Hao
2020-01-14  5:56             ` Wu Hao
2020-01-15  5:10               ` Moritz Fischer
2020-01-15  8:14                 ` Greg KH
2020-01-16  2:53                   ` 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=20191125033412.GB890@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 \
    /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).