From: Ira Weiny <ira.weiny@intel.com>
To: Ira Weiny <ira.weiny@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
"Ben Widawsky" <bwidawsk@kernel.org>,
Dan Williams <dan.j.williams@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Ira Weiny <ira.weiny@intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
Dave Jiang <dave.jiang@intel.com>
Subject: Re: [PATCH 0/2] cxl: Enhance trace point information
Date: Thu, 9 Feb 2023 23:07:36 -0800 [thread overview]
Message-ID: <63e5ed38d77d9_138fbc2947a@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20230208-cxl-event-names-v1-0-73f0ff3a3870@intel.com>
Ira Weiny wrote:
> Trace point definitions are reporting different linux devices for
> the same CXL hardware device. Clean this up and add parent device
> information to all the trace points.
I've found a couple of small changes that I wanted to make but got side
tracked and forgot when I sent this.
Also Dan reminded me we would like to see the device serial number in
these traces as well.
v2 coming shortly.
Ira
>
> Signed-off-by: Ira Weiny <ira.weiny@intel.com>
> ---
> Ira Weiny (2):
> cxl/trace: Standardize device information output
> cxl/trace: Add host output to trace points
>
> drivers/cxl/core/mbox.c | 14 ++++----
> drivers/cxl/core/pci.c | 8 ++---
> drivers/cxl/core/trace.h | 85 +++++++++++++++++++++++++++---------------------
> 3 files changed, 57 insertions(+), 50 deletions(-)
> ---
> base-commit: dbe9f7d1e155b97a42f7da81e22acc98fe0a9072
> change-id: 20230208-cxl-event-names-9372fb72a607
>
> Best regards,
> --
> Ira Weiny <ira.weiny@intel.com>
>
prev parent reply other threads:[~2023-02-10 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 6:40 [PATCH 0/2] cxl: Enhance trace point information Ira Weiny
2023-02-10 6:40 ` [PATCH 1/2] cxl/trace: Standardize device information output Ira Weiny
2023-02-10 6:40 ` [PATCH 2/2] cxl/trace: Add host output to trace points Ira Weiny
2023-02-10 7:07 ` Ira Weiny [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=63e5ed38d77d9_138fbc2947a@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=vishal.l.verma@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