From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/3] docs/s390x: document the virtual css
Date: Fri, 15 May 2020 10:51:33 +0200 [thread overview]
Message-ID: <20200515105133.12ffb2be.cohuck@redhat.com> (raw)
In-Reply-To: <7876d0f3-7bb9-38b9-6675-94ba6bd47a1a@redhat.com>
On Fri, 15 May 2020 09:04:13 +0200
Thomas Huth <thuth@redhat.com> wrote:
> On 05/05/2020 15.50, Cornelia Huck wrote:
> > +Examples
> > +--------
> > +
> > +* a virtio-net device, cssid/ssid/devno automatically assigned::
> > +
> > + -device virtio-net-ccw
> > +
> > + In a Linux guest (without default devices and no other devices specified
> > + prior to this one), this will show up as ``0.0.0000`` under subchannel
> > + ``0.0.0000``.
>
> Maybe mention the QEMU side again, e.g. that when you run "info qtree"
> in the HMP monitor, you see the device with dev_id = "fe.0.0000".
Yes, that's a good idea.
>
> > +* a virtio-rng device in subchannel set ``0``::
> > +
> > + -device virtio-rng-ccw,devno=fe.0.0042
> > +
> > + If added to the same Linux guest as above, it would show up as ``0.0.0042``
> > + under subchannel ``0.0.0001``.
>
> Does "same" matter here? Otherwise, maybe just say "to a Linux guest" ?
I wanted to provide the subchannel number in my examples as well. As
QEMU always picks the first free one (and you cannot specify it
manually), I wanted to make the examples build upon each other.
>
> > +* a virtio-gpu device in subchannel set ``2``::
> > +
> > + -device virtio-gpu-ccw,devno=fe.2.1111
> > +
> > + If added to the same Linux guest as above, it would show up as ``0.2.1111``
> > + under subchannel ``0.2.0000``.
>
> Dito.
dito :)
>
> > +* a virtio-mouse device in a non-standard channel subsystem::
> > +
> > + -device virtio-mouse-ccw,devno=2.0.2222
> > +
> > + This would not show up in a standard Linux guest.
>
> Ok ... and what happens if you use devno=0.0.1234 ? Will that then show
> up under fe.0.1234 in the guest??
That won't show up in the guest, either -- do you think I should add an
example for that as well?
next prev parent reply other threads:[~2020-05-15 8:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 13:50 [PATCH 0/3] s390x: improve documentation Cornelia Huck
2020-05-05 13:50 ` [PATCH 1/3] docs/s390x: document the virtual css Cornelia Huck
2020-05-15 7:04 ` Thomas Huth
2020-05-15 8:51 ` Cornelia Huck [this message]
2020-05-15 8:57 ` Thomas Huth
2020-05-15 9:40 ` Cornelia Huck
2020-05-05 13:50 ` [PATCH 2/3] docs/s390x: document 3270 Cornelia Huck
2020-05-15 7:29 ` Thomas Huth
2020-05-15 9:00 ` Cornelia Huck
2020-05-15 9:14 ` Thomas Huth
2020-05-15 9:45 ` Cornelia Huck
2020-05-15 10:01 ` Thomas Huth
2020-05-05 13:50 ` [PATCH 3/3] docs/s390x: document vfio-ccw Cornelia Huck
2020-05-15 7:54 ` Thomas Huth
2020-05-15 9:15 ` Cornelia Huck
2020-05-14 6:13 ` [PATCH 0/3] s390x: improve documentation Cornelia Huck
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=20200515105133.12ffb2be.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.