From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>,
Diederik de Haas <didi.debian@cknow.org>
Cc: xen-devel@lists.xen.org
Subject: Re: Is: EPT violations. Was:Re: Problems with pci/vga passthrough
Date: Tue, 24 Jan 2017 13:28:28 -0500 [thread overview]
Message-ID: <ddff0e8d-a33f-98e6-969b-68ce17e86584@oracle.com> (raw)
In-Reply-To: <58878ABA020000780013373E@prv-mh.provo.novell.com>
On 01/24/2017 11:11 AM, Jan Beulich wrote:
>>>> On 24.01.17 at 16:59, <didi.debian@cknow.org> wrote:
>> Reported it at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852324 but
>> given Ben Hutchings' reaction it seems to be a Xen problem after all.
>>
>> Relevant part of earlier attached dmesg:
>>
>> [ 13.588386] WARNING: CPU: 18 PID: 1 at
>> /build/linux-zDY19G/linux-4.8.15/arch/x86/mm/dump_pagetables.c:225 note_page+0x5e8/0x790
>> [ 13.588388] x86/mm: Found insecure W+X mapping at address ffff880000000000/0xffff880000000000
>> ...
>> [ 13.608867] x86/mm: Checked W+X mappings: FAILED, 4602 W+X pages found.
> Now this is a know issue, but I'm pretty convinced one that's entirely
> unrelated to your problem.
I thought we fixed this. That's what is_hypervisor_range() was
introduced for, and I haven't seen this warning since then.
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-24 18:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 1:37 Problems with pci/vga passthrough Diederik de Haas
2017-01-18 16:20 ` Is: EPT violations. Was:Re: " Konrad Rzeszutek Wilk
2017-01-18 16:42 ` Jan Beulich
[not found] ` <1890797.J70arCvF62@bagend>
2017-01-19 8:18 ` Jan Beulich
2017-01-18 16:47 ` George Dunlap
2017-01-22 18:30 ` Diederik de Haas
2017-01-24 15:59 ` Diederik de Haas
2017-01-24 16:11 ` Jan Beulich
2017-01-24 17:24 ` Diederik de Haas
2017-01-24 18:28 ` Boris Ostrovsky [this message]
2017-01-24 18:44 ` Diederik de Haas
2017-01-24 18:51 ` Boris Ostrovsky
2017-01-24 21:43 ` Boris Ostrovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ddff0e8d-a33f-98e6-969b-68ce17e86584@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=didi.debian@cknow.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.