From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Tony Krowiak <akrowiak@linux.ibm.com>,
Peter Maydell <peter.maydell@linaro.org>,
David Hildenbrand <david@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x <qemu-s390x@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH 1/1] docs/s390x: fix vfio-ap device_del description
Date: Thu, 18 Jun 2020 12:35:57 +0200 [thread overview]
Message-ID: <20200618123557.5c2ad135.cohuck@redhat.com> (raw)
In-Reply-To: <38f61553-10d9-2d45-0e10-ef30f9607b0f@redhat.com>
On Wed, 17 Jun 2020 19:17:54 +0200
Thomas Huth <thuth@redhat.com> wrote:
> On 17/06/2020 18.06, Christian Borntraeger wrote:
> > device_del requires an id and not a sysfsfile.
> >
> > Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> > ---
> > docs/system/s390x/vfio-ap.rst | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/docs/system/s390x/vfio-ap.rst b/docs/system/s390x/vfio-ap.rst
> > index 3cd84179a2df..f441df69edde 100644
> > --- a/docs/system/s390x/vfio-ap.rst
> > +++ b/docs/system/s390x/vfio-ap.rst
> > @@ -606,10 +606,11 @@ action.
> >
> > To hot plug a vfio-ap device, use the QEMU ``device_add`` command::
> >
> > - (qemu) device_add vfio-ap,sysfsdev="$path-to-mdev"
> > + (qemu) device_add vfio-ap,sysfsdev="$path-to-mdev",id="$id"
> >
> > Where the ``$path-to-mdev`` value specifies the absolute path to a mediated
> > device to which AP resources to be used by the guest have been assigned.
> > +``$id`` is the name value for the optional id parameter.
> >
> > Note that on Linux guests, the AP devices will be created in the
> > ``/sys/bus/ap/devices`` directory when the AP bus subsequently performs its periodic
> > @@ -632,10 +633,9 @@ or a prior hot plug action.
> >
> > To hot unplug a vfio-ap device, use the QEMU ``device_del`` command::
> >
> > - (qemu) device_del vfio-ap,sysfsdev="$path-to-mdev"
> > + (qemu) device_del "id"
>
> Do you want to use $id instead of id here?
> >
> > -Where ``$path-to-mdev`` is the same as the path specified when the vfio-ap
> > -device was attached to the virtual machine's ap-bus.
> > +Where ``$id`` is the same id that was specified at device creation.
>
> ^--- ... since you use $id here.
>
> > On a Linux guest, the AP devices will be removed from the ``/sys/bus/ap/devices``
> > directory on the guest when the AP bus subsequently performs its periodic scan,
>
> With the 1 $ question fixed:
>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
Indeed, no reason to skimp on the $s :)
Fixed up and pushed to s390-next, thanks.
prev parent reply other threads:[~2020-06-18 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 16:06 [PATCH 1/1] docs/s390x: fix vfio-ap device_del description Christian Borntraeger
2020-06-17 16:07 ` Christian Borntraeger
2020-06-17 16:17 ` Cornelia Huck
2020-06-17 17:17 ` Thomas Huth
2020-06-18 10:35 ` Cornelia Huck [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=20200618123557.5c2ad135.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.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).