[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3f067ced-8fe3-2e4a-79bb-909b8636db17@oracle.com>
Date: Thu, 2 Jun 2022 15:09:00 -0400
From: Boris Ostrovsky <boris.ostrovsky@...cle.com>
To: Oleksandr <olekstysh@...il.com>, xen-devel@...ts.xenproject.org,
x86@...nel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Cc: Juergen Gross <jgross@...e.com>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@...m.com>,
Stefano Stabellini <sstabellini@...nel.org>,
Russell King <linux@...linux.org.uk>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>, Julien Grall <julien@....org>,
"Michael S. Tsirkin" <mst@...hat.com>,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH V3 4/8] xen/virtio: Enable restricted memory access using
Xen grant mappings
On 6/2/22 8:49 AM, Oleksandr wrote:
>
> On 31.05.22 00:00, Oleksandr Tyshchenko wrote:
>
> Hello all.
>
>> From: Juergen Gross <jgross@...e.com>
>>
>> In order to support virtio in Xen guests add a config option XEN_VIRTIO
>> enabling the user to specify whether in all Xen guests virtio should
>> be able to access memory via Xen grant mappings only on the host side.
>>
>> Also set PLATFORM_VIRTIO_RESTRICTED_MEM_ACCESS feature from the guest
>> initialization code on Arm and x86 if CONFIG_XEN_VIRTIO is enabled.
>>
>> Signed-off-by: Juergen Gross <jgross@...e.com>
>> Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@...m.com>
>> Reviewed-by: Stefano Stabellini <sstabellini@...nel.org>
>> ---
>> Changes V1 -> V2:
>> - new patch, split required changes from commit:
>> "[PATCH V1 3/6] xen/virtio: Add option to restrict memory access under Xen"
>> - rework according to new platform_has() infrastructure
>>
>> Changes V2 -> V3:
>> - add Stefano's R-b
>
> May I please ask for the ack or comments for x86 side here?
>
>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@...cle.com>
Powered by blists - more mailing lists