From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: xc_evtchn_status fails with EFAULT on HVM, the same on PV works
Date: Fri, 13 Jan 2017 18:31:30 +0100 [thread overview]
Message-ID: <20170113173130.GI5268@mail-itl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 521 bytes --]
Hi,
I have a strange problem - xc_evtchn_status fails when running in HVM,
while exactly the same code (same kernel, same application etc) works
fine in PV. I've narrowed it down to copy_from_guest call in
common/event_channel.c, but no idea why it fails there. Xen version is
4.8.0. kernel is kernel-4.8.13-100.fc23. Any idea?
--
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 reply other threads:[~2017-01-13 17:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 17:31 Marek Marczykowski-Górecki [this message]
2017-01-13 17:38 ` xc_evtchn_status fails with EFAULT on HVM, the same on PV works 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
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=20170113173130.GI5268@mail-itl \
--to=marmarek@invisiblethingslab.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.