[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] identify a Xen PV domU to fix devmem_is_allowed

To: Olaf Hering <olaf@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxx>
From: David Vrabel <david.vrabel@xxxxxxxxxx>
Date: Tue, 1 Mar 2016 15:29:29 +0000
Delivery-date: Tue, 01 Mar 2016 15:29:36 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 29/02/16 10:28, Olaf Hering wrote:
> What is the correct way to identify a Xen PV domU in the kenrel?
> devmem_is_allowed() used to disable access to pages < 256 in domU.
> With pvops this check was removed, or never ported forward.
> 
> Would this change be the correct fix?

I think the bug is in range_is_allowed() as it is using
devmem_is_allowed() to avoid having to correctly check for aliases.

David

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Prev by Date: Re: [Xen-devel] [PATCH v4 13/24] arm/acpi: Map all other tables for Dom0
Next by Date: [Xen-devel] [PATCH] arm: remove unneeded ifdef CONFIG_ARM in efi-boot.h
Previous by thread: Re: [Xen-devel] identify a Xen PV domU to fix devmem_is_allowed
Next by thread: Re: [Xen-devel] identify a Xen PV domU to fix devmem_is_allowed
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.