From: Eric Farman <farman@linux.ibm.com>
To: Vineeth Vijayan <vneethv@linux.ibm.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Matthew Rosato <mjrosato@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
Eric Farman <farman@linux.ibm.com>
Subject: [PATCH v2 0/2] s390/vfio-ccw: addressing fixes
Date: Mon, 21 Nov 2022 17:58:34 +0100 [thread overview]
Message-ID: <20221121165836.283781-1-farman@linux.ibm.com> (raw)
Hi everyone,
Here's the update to the couple small addressing fixes
created/used by vfio-ccw, which are shared with hardware,
which I'd sent a week or two ago.
One thing left un-done is a broader rework of the cp_get_orb()
interface that Matthew suggested [1]. I intend to address that
with a larger series that reworks the whole channel program
path in the not-too-distant future; doing it here expands the
otherwise tidy scope of these commits more than I'd like.
[1] https://lore.kernel.org/linux-s390/c9e7229e-a88d-2185-bb6b-a94e9dac7b7a@linux.ibm.com/
v1->v2:
- [MR, NB] Patch 1: Update commit message per suggestions
- [MR, NB] Add reviewed-by tags (thank you!)
v1: https://lore.kernel.org/linux-s390/20221109202157.1050545-1-farman@linux.ibm.com/
Alexander Gordeev (1):
vfio/ccw: sort out physical vs virtual pointers usage
Eric Farman (1):
vfio/ccw: identify CCW data addresses as physical
drivers/s390/cio/vfio_ccw_cp.c | 4 ++--
drivers/s390/cio/vfio_ccw_fsm.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2022-11-21 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 16:58 Eric Farman [this message]
2022-11-21 16:58 ` [PATCH v2 1/2] vfio/ccw: sort out physical vs virtual pointers usage Eric Farman
2022-11-21 16:58 ` [PATCH v2 2/2] vfio/ccw: identify CCW data addresses as physical Eric Farman
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=20221121165836.283781-1-farman@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=vneethv@linux.ibm.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).