From: Stefan Hajnoczi <stefanha@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: virtio-fs@redhat.com, "Michael S. Tsirkin" <mst@redhat.com>,
"Ján Tomko" <jtomko@redhat.com>,
"qemu devel list" <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v2] vhost-user-fs: add the "bootindex" property
Date: Wed, 13 Jan 2021 10:36:29 +0000 [thread overview]
Message-ID: <20210113103629.GF250553@stefanha-x1.localdomain> (raw)
In-Reply-To: <20210112131603.12686-1-lersek@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]
On Tue, Jan 12, 2021 at 02:16:03PM +0100, Laszlo Ersek wrote:
> virtio-fs qualifies as a bootable device minimally under OVMF, but
> currently the necessary "bootindex" property is missing. Add the property.
>
> Expose the property only in the PCI device, for now. There is no boot
> support for virtiofs on s390x (ccw) for the time being [1] [2], so leave
> the CCW device unchanged. Add the property to the base device still,
> because adding the alias to the CCW device later will be easier this way
> [3].
>
> [1] https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg01745.html
> [2] https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg01870.html
> [3] https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg01751.html
>
> Example OpenFirmware device path for the "vhost-user-fs-pci" device in the
> "bootorder" fw_cfg file:
>
> /pci@i0cf8/pci-bridge@1,6/pci1af4,105a@0/filesystem@0
>
> Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> Cc: "Michael S. Tsirkin" <mst@redhat.com>
> Cc: Ján Tomko <jtomko@redhat.com>
> Cc: Stefan Hajnoczi <stefanha@redhat.com>
> Cc: virtio-fs@redhat.com
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
> Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
>
> Notes:
> v2:
> - drop "hw/s390x/vhost-user-fs-ccw.c" hunk [Christian, Cornelia]
>
> - document the same in the commit message
>
> - remove fw_cfg kernel boot reference from the commit message (somewhat
> similar use case, but a comparison or even a hint doesn't necessarily
> belong in the commit message)
>
> - pick up Dave's ACK
>
> include/hw/virtio/vhost-user-fs.h | 1 +
> hw/virtio/vhost-user-fs-pci.c | 2 ++
> hw/virtio/vhost-user-fs.c | 10 ++++++++++
> 3 files changed, 13 insertions(+)
Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-01-13 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 13:16 [PATCH v2] vhost-user-fs: add the "bootindex" property Laszlo Ersek
2021-01-13 10:36 ` Stefan Hajnoczi [this message]
2021-01-13 10:42 ` Laszlo Ersek
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=20210113103629.GF250553@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jtomko@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-fs@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).