From: Greg KH <gregkh@linuxfoundation.org>
To: Yicong Yang <yangyicong@hisilicon.com>
Cc: alexander.shishkin@linux.intel.com, helgaas@kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
lorenzo.pieralisi@arm.com, jonathan.cameron@huawei.com,
song.bao.hua@hisilicon.com, prime.zeng@huawei.com,
linux-doc@vger.kernel.org, linuxarm@huawei.com
Subject: Re: [PATCH 0/4] Add support for HiSilicon PCIe Tune and Trace device
Date: Tue, 6 Apr 2021 15:49:23 +0200 [thread overview]
Message-ID: <YGxm49c9cT69NV5Q@kroah.com> (raw)
In-Reply-To: <1617713154-35533-1-git-send-email-yangyicong@hisilicon.com>
On Tue, Apr 06, 2021 at 08:45:50PM +0800, Yicong Yang wrote:
> HiSilicon PCIe tune and trace device(PTT) is a PCIe Root Complex
> integrated Endpoint(RCiEP) device, providing the capability
> to dynamically monitor and tune the PCIe traffic(tune),
> and trace the TLP headers(trace). The driver exposes the user
> interface through debugfs, so no need for extra user space tools.
> The usage is described in the document.
Why use debugfs and not the existing perf tools for debugging?
thanks,
greg k-h
next prev parent reply other threads:[~2021-04-06 13:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 12:45 [PATCH 0/4] Add support for HiSilicon PCIe Tune and Trace device Yicong Yang
2021-04-06 12:45 ` [PATCH 1/4] hwtracing: Add trace function " Yicong Yang
2021-04-06 13:51 ` Greg KH
2021-04-06 16:14 ` kernel test robot
2021-04-06 22:48 ` kernel test robot
2021-04-06 12:45 ` [PATCH 2/4] hwtracing: Add tune " Yicong Yang
2021-04-06 12:45 ` [PATCH 3/4] docs: Add documentation for HiSilicon PTT device driver Yicong Yang
2021-04-07 18:55 ` Bjorn Helgaas
2021-04-08 13:22 ` Yicong Yang
2021-04-08 16:57 ` Bjorn Helgaas
2021-04-09 14:09 ` Yicong Yang
2021-04-06 12:45 ` [PATCH 4/4] MAINTAINERS: Add maintainer for HiSilicon PTT driver Yicong Yang
2021-04-06 13:49 ` Greg KH [this message]
2021-04-07 10:03 ` [PATCH 0/4] Add support for HiSilicon PCIe Tune and Trace device Yicong Yang
2021-04-07 10:25 ` Greg KH
2021-04-08 13:25 ` Yicong Yang
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=YGxm49c9cT69NV5Q@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=prime.zeng@huawei.com \
--cc=song.bao.hua@hisilicon.com \
--cc=yangyicong@hisilicon.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).