From: Oleksandr <olekstysh@gmail.com>
To: Juergen Gross <jgross@suse.com>
Cc: xen-devel@lists.xenproject.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Subject: Re: [PATCH] xen: don't require virtio with grants for non-PV guests
Date: Wed, 15 Jun 2022 18:47:54 +0300 [thread overview]
Message-ID: <6f5b1562-1270-5e83-bf9f-a9a7afc5a725@gmail.com> (raw)
In-Reply-To: <20220615084835.27113-1-jgross@suse.com>
On 15.06.22 11:48, Juergen Gross wrote:
Hello Juergen
> Commit fa1f57421e0b ("xen/virtio: Enable restricted memory access using
> Xen grant mappings") introduced a new requirement for using virtio
> devices: the backend now needs to support the VIRTIO_F_ACCESS_PLATFORM
> feature.
>
> This is an undue requirement for non-PV guests, as those can be operated
> with existing backends without any problem, as long as those backends
> are running in dom0.
>
> Per default allow virtio devices without grant support for non-PV
> guests.
>
> The setting can be overridden by using the new "xen_virtio_grant"
> command line parameter.
>
> Add a new config item to always force use of grants for virtio.
>
> Fixes: fa1f57421e0b ("xen/virtio: Enable restricted memory access using Xen grant mappings")
> Signed-off-by: Juergen Gross <jgross@suse.com>
Thank you for the fix.
I have tested it on Arm64 guest (XEN_HVM_DOMAIN), it works.
With the "__init" fix (pointed out by Viresh) applied you can add my:
Tested-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> #Arm64 only
[snip]
--
Regards,
Oleksandr Tyshchenko
next prev parent reply other threads:[~2022-06-15 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 8:48 Juergen Gross
2022-06-15 9:25 ` Viresh Kumar
2022-06-15 9:32 ` Juergen Gross
2022-06-15 11:24 ` Christoph Hellwig
2022-06-15 11:26 ` Juergen Gross
2022-06-15 11:28 ` Christoph Hellwig
2022-06-15 11:39 ` Juergen Gross
2022-06-15 11:54 ` Christoph Hellwig
2022-06-15 12:53 ` Juergen Gross
2022-06-15 13:43 ` Christoph Hellwig
2022-06-15 13:46 ` Juergen Gross
2022-06-15 15:47 ` Oleksandr [this message]
2022-06-15 23:40 ` Stefano Stabellini
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=6f5b1562-1270-5e83-bf9f-a9a7afc5a725@gmail.com \
--to=olekstysh@gmail.com \
--cc=corbet@lwn.net \
--cc=jgross@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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
all inboxes | Powered by JetHome®