|
[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
On 03/21/2016 05:29 PM, Boris Ostrovsky wrote: On 03/15/2016 12:57 PM, Olaf Hering wrote:On Tue, Mar 01, Boris Ostrovsky wrote:on domU:[root@dhcp-burlington7-2nd-B-east-10-152-55-140 ~]# od -N 1 -j 4096 /dev/memod: /dev/mem: read error: Bad address 0010000 [root@dhcp-burlington7-2nd-B-east-10-152-55-140 ~]# with (XEN) mm.c:1767:d14v0 Bad L1 flags 10How should we proceed with this bug?I can't see any way to avoid calling xen_pv_domain() so what you suggested should work. The only problem is that this will now cause reserved areas to also return 0: Olaf,Can you apply PAT changes from http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg02127.html and see if it helps? It should at least get rid of the splat (patch 3 is the one addresses no-MTRR problem that I mentioned above). We should still fix devmem_is_allowed() though. -boris _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |