From: Eric Farman <farman@linux.ibm.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>,
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: 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
Subject: Re: [PATCH 1/2] vfio-ccw: sort out physical vs virtual pointers usage
Date: Wed, 09 Nov 2022 21:15:18 -0500 [thread overview]
Message-ID: <c459f18c3ccd8ea39b9f585537366b4a9d19d626.camel@linux.ibm.com> (raw)
In-Reply-To: <c9e7229e-a88d-2185-bb6b-a94e9dac7b7a@linux.ibm.com>
On Wed, 2022-11-09 at 17:20 -0500, Matthew Rosato wrote:
> On 11/9/22 3:21 PM, Eric Farman wrote:
> > From: Alexander Gordeev <agordeev@linux.ibm.com>
> >
> > The ORB is a construct that is sent to the real hardware,
> > so should contain a physical address in its interrupt
> > parameter field. Let's clarify that.
> >
> > Note: this currently doesn't fix a real bug, since virtual
> > addresses are identical to physical ones.
> >
> > Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
> > [EF: Updated commit message]
> > Signed-off-by: Eric Farman <farman@linux.ibm.com>
> > ---
> > drivers/s390/cio/vfio_ccw_fsm.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/s390/cio/vfio_ccw_fsm.c
> > b/drivers/s390/cio/vfio_ccw_fsm.c
> > index a59c758869f8..0a5e8b4a6743 100644
> > --- a/drivers/s390/cio/vfio_ccw_fsm.c
> > +++ b/drivers/s390/cio/vfio_ccw_fsm.c
> > @@ -29,7 +29,7 @@ static int fsm_io_helper(struct vfio_ccw_private
> > *private)
> >
> > spin_lock_irqsave(sch->lock, flags);
> >
> > - orb = cp_get_orb(&private->cp, (u32)(addr_t)sch, sch->lpm);
> > + orb = cp_get_orb(&private->cp, (u32)virt_to_phys(sch), sch-
> > >lpm);
>
> Nit: I think it would make more sense to do the virt_to_phys inside
> cp_get_orb at the time we place the address in the orb (since that's
> what gets sent to hardware), rather than requiring all callers of
> cp_get_orb to pass a physical address. I realize there is only 1
> caller today.
Eh, maybe so. But that takes me into the 'what are we passing to this
routine and how can we simplify it' rabbit hole, and it stops becoming
a nit pretty quickly. I'd rather keep this patch as the simple change
described here. I have some more involved rework in the broader cp code
in the pipe, and can include your suggestion with that.
>
> Nit++: Can we make the patch subjects match? vfio/ccw or vfio-ccw
Heh, fair. "vfio/ccw" has been the style du jour of late.
>
> Either way:
>
> Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
Thanks!
>
> > if (!orb) {
> > ret = -EIO;
> > goto out;
>
next prev parent reply other threads:[~2022-11-10 2:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 20:21 [PATCH 0/2] s390/vfio-ccw: addressing fixes Eric Farman
2022-11-09 20:21 ` [PATCH 1/2] vfio-ccw: sort out physical vs virtual pointers usage Eric Farman
2022-11-09 22:20 ` Matthew Rosato
2022-11-10 2:15 ` Eric Farman [this message]
2022-11-10 9:24 ` Nico Boehr
2022-11-10 14:28 ` Eric Farman
2022-11-10 16:26 ` Nico Boehr
2022-11-09 20:21 ` [PATCH 2/2] vfio/ccw: identify CCW data addresses as physical Eric Farman
2022-11-10 8:53 ` Nico Boehr
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=c459f18c3ccd8ea39b9f585537366b4a9d19d626.camel@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