From: Heiko Carstens <hca@linux.ibm.com>
To: Gerd Bayer <gbayer@linux.ibm.com>
Cc: Niklas Schnelle <schnelle@linux.ibm.com>,
Benjamin Block <bblock@linux.ibm.com>,
Ramesh Errabolu <ramesh@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
"Joerg Roedel (AMD)" <joro@8bytes.org>,
Farhan Ali <alifm@linux.ibm.com>, Cam Miller <cam@linux.ibm.com>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux.dev
Subject: Re: [PATCH v2 0/3] s390/pci: Updates to PCI insn tracing
Date: Mon, 12 Oct 2026 18:00:49 +0200 [thread overview]
Message-ID: <20261012160049.19350J7a-hca@linux.ibm.com> (raw)
In-Reply-To: <20261012-rpcit_trcfh_upstream-v2-0-1812db73dfa5@linux.ibm.com>
On Mon, Oct 12, 2026 at 04:21:48PM +0200, Gerd Bayer wrote:
> With this series applied (+ a test patch to trace RPCIT even in CC0
> situations) an entry in /sys/kernel/debug/s390dbf/pci_error/hex_ascii
> looks like the following (removed time-stamp and ASCII transcription,
> replaced instruction address with "<IA>"):
...
> Signed-off-by: Gerd Bayer <gbayer@linux.ibm.com>
> ---
> Changes in v2:
> - 1/3 and 3/3: Replace unnamed bitfields with named dummy members for
> padding (address Sashiko findings)
> - Link to v1: https://lore.kernel.org/r/20261007-rpcit_trcfh_upstream-v1-0-8a2718cfb90b@linux.ibm.com
>
> ---
> Gerd Bayer (3):
> s390/pci: Adjust alignment in insn trace
> s390/pci: Use 32-bit fh outside of inline asm
> s390/pci: Add function handle to RPCIT insn trace
>
> arch/s390/include/asm/pci_insn.h | 2 +-
> arch/s390/pci/pci_insn.c | 42 +++++++++++++++++++++++++++++++++-------
> drivers/iommu/s390-iommu.c | 8 +++-----
> 3 files changed, 39 insertions(+), 13 deletions(-)
Even though this touches drivers/iommu/s390-iommu.c I assume this
should go upstream via s390. Is this correct?
next prev parent reply other threads:[~2026-10-12 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 14:21 Gerd Bayer
2026-10-12 14:21 ` [PATCH v2 1/3] s390/pci: Adjust alignment in insn trace Gerd Bayer
2026-10-12 15:28 ` Matthew Rosato
2026-10-12 14:21 ` [PATCH v2 2/3] s390/pci: Use 32-bit fh outside of inline asm Gerd Bayer
2026-10-12 15:00 ` Matthew Rosato
2026-10-12 14:21 ` [PATCH v2 3/3] s390/pci: Add function handle to RPCIT insn trace Gerd Bayer
2026-10-12 15:00 ` Matthew Rosato
2026-10-12 16:00 ` Heiko Carstens [this message]
2026-10-12 16:10 ` [PATCH v2 0/3] s390/pci: Updates to PCI insn tracing Gerd Bayer
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=20261012160049.19350J7a-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=bblock@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cam@linux.ibm.com \
--cc=gbayer@linux.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=ramesh@linux.ibm.com \
--cc=robin.murphy@arm.com \
--cc=schnelle@linux.ibm.com \
--cc=svens@linux.ibm.com \
--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
all inboxes | Powered by JetHome®