diff options
| author |  Juergen Gross <jgross@suse.com>
| 2022-06-22 08:38:38 +0200 |
|---|---|---|
| committer | Juergen Gross <jgross@suse.com>
| 2022-08-01 07:43:03 +0200 |
| commit | 251e90e7e346a23742b90e2c4db19d322e071d99 (patch) | |
| tree | c4c3477288ae1ab03b0933fbeeaff78020c1b63f /kernel/time/timekeeping.c | |
| parent | kernel: remove platform_has() infrastructure (diff) | |
| download | linux-251e90e7e346a23742b90e2c4db19d322e071d99.tar.gz linux-251e90e7e346a23742b90e2c4db19d322e071d99.tar.bz2 linux-251e90e7e346a23742b90e2c4db19d322e071d99.zip | |
xen: don't require virtio with grants for non-PV guests
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.
On Arm require VIRTIO_F_ACCESS_PLATFORM for devices having been listed
in the device tree to use grants.
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")
Reported-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Tested-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> # Arm64 guest using Xen
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Link: https://lore.kernel.org/r/20220622063838.8854-4-jgross@suse.com
Signed-off-by: Juergen Gross <jgross@suse.com>
Diffstat (limited to 'kernel/time/timekeeping.c')
0 files changed, 0 insertions, 0 deletions