From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: xc_evtchn_status fails with EFAULT on HVM, the same on PV works
Date: Fri, 13 Jan 2017 19:59:22 +0100 [thread overview]
Message-ID: <20170113185922.GL1341@mail-itl> (raw)
In-Reply-To: <a5dd1ddd-1a60-b47f-7e94-54aafcd7c8e0@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 986 bytes --]
On Fri, Jan 13, 2017 at 06:37:06PM +0000, Andrew Cooper wrote:
> On 13/01/17 18:32, Marek Marczykowski-Górecki wrote:
> > On Fri, Jan 13, 2017 at 06:15:35PM +0000, Andrew Cooper wrote:
> >> Can you get the result of this piece of debugging in the failure case?
> > I've got this:
> > ** d4v0 CFG(24, 00007f794bd07004, 1) = 24
>
> Silly question (and I really hope the answer isn't yes, but I have a
> sinking feeling it is).
>
> Is the guest in question using SMAP? If so, does disabling SMAP fix the
> problem?
How can I check that? If looking at 0x200000 CR4 bit in `xl debug-keys
v` output enough, then yes - it's enabled. And booting hypervisor with
smap=0 "fixed" the problem.
So, what would be the correct solution? I'd prefer not to disable SMAP
"just" for this reason...
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-13 18:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 17:31 xc_evtchn_status fails with EFAULT on HVM, the same on PV works Marek Marczykowski-Górecki
2017-01-13 17:38 ` Andrew Cooper
2017-01-13 18:03 ` Marek Marczykowski-Górecki
2017-01-13 18:15 ` Andrew Cooper
2017-01-13 18:32 ` Marek Marczykowski-Górecki
2017-01-13 18:37 ` Andrew Cooper
2017-01-13 18:59 ` Marek Marczykowski-Górecki [this message]
2017-01-13 19:27 ` Andrew Cooper
2017-01-13 19:40 ` Marek Marczykowski-Górecki
2017-01-13 19:54 ` Andrew Cooper
2017-01-13 20:32 ` Marek Marczykowski-Górecki
2017-01-14 1:47 ` Andrew Cooper
2017-01-14 2:52 ` Marek Marczykowski-Górecki
2017-01-16 12:17 ` Jan Beulich
2017-01-16 23:06 ` Marek Marczykowski-Górecki
2017-01-16 23:41 ` Andrew Cooper
2017-06-22 8:23 ` Marek Marczykowski-Górecki
2017-06-22 8:27 ` Andrew Cooper
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=20170113185922.GL1341@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--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.