On Tue, Mar 22, Boris Ostrovsky wrote:
> 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
On Tue, Mar 22, Boris Ostrovsky wrote:
> Can you apply PAT changes from
> http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg02127.html
> and see if it helps?
I will try, thanks.
Olaf
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http
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/mem
od: /dev/mem: read error: Bad address
001
[root@dhcp-burlington7-2nd-B-e
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/mem
od: /dev/mem: read error: Bad address
001
[root@dhcp-burlington7-2nd-B-east-10-152-55-140 ~]#
with
(XEN) mm.c:1767:d14v0
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/mem
od: /dev/mem: read error: Bad address
001
[root@dhcp-burlington7-2nd-B-east-10-152-55-140 ~]#
with
(XEN) mm.c:1767:d14v0
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/mem
> od: /dev/mem: read error: Bad address
> 001
> [root@dhcp-burlington7-2nd-B-east-10-152-55-140 ~]#
>
> with
>
> (XEN) mm.c:1767:d14v0 Bad L1 flags 10
How shou
On Mon, Feb 29, Konrad Rzeszutek Wilk wrote:
> .. A fix for what issue?
#include
#include
#include
#include
#include
int main(void)
{
unsigned long long *p;
int fd;
fd = open("/dev/mem", O_RDWR);
if (fd < 0) {
perror("/dev/mem");
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
On Mon, Feb 29, Boris Ostrovsky wrote:
> Do you see any messages in hypervisor log (like "Bad L1 flags 10")?
Yes, with a debug build of xen.gz.
(XEN) mm.c:1882:d1v0 Bad L1 flags 10
Olaf
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.x
On 03/01/2016 09:34 AM, Konrad Rzeszutek Wilk wrote:
On Tue, Mar 01, 2016 at 03:38:55AM -0700, Jan Beulich wrote:
On 29.02.16 at 16:10, wrote:
On Mon, Feb 29, 2016 at 11:28:49AM +0100, Olaf Hering wrote:
What is the correct way to identify a Xen PV domU in the kenrel?
devmem_is_allowed() used
On Tue, Mar 01, 2016 at 03:38:55AM -0700, Jan Beulich wrote:
> >>> On 29.02.16 at 16:10, wrote:
> > On Mon, Feb 29, 2016 at 11:28:49AM +0100, 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 d
>>> On 29.02.16 at 16:10, wrote:
> On Mon, Feb 29, 2016 at 11:28:49AM +0100, 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.
>
On 02/29/2016 10:29 AM, Olaf Hering wrote:
On Mon, Feb 29, Konrad Rzeszutek Wilk wrote:
On Mon, Feb 29, 2016 at 11:28:49AM +0100, Olaf Hering wrote:
Would this change be the correct fix?
.. A fix for what issue?
mmap returns some pointer, but appearently that memory can not be used.
https:/
On Mon, Feb 29, Konrad Rzeszutek Wilk wrote:
> On Mon, Feb 29, 2016 at 11:28:49AM +0100, Olaf Hering wrote:
> > Would this change be the correct fix?
> .. A fix for what issue?
mmap returns some pointer, but appearently that memory can not be used.
https://bugzilla.suse.com/show_bug.cgi?id=96434
On Mon, Feb 29, 2016 at 11:28:49AM +0100, 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.
CC-ing Boris and Daniel.
Why is this n
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?
+++ b/arch/x86/mm/init.c
@@ -637,7 +637,7 @@ void __init init_mem_m
16 matches
Mail list logo
