From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel List <xen-devel@lists.xen.org>
Cc: Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: RFC Userspace hypercalls
Date: Thu, 7 Jan 2016 10:42:27 +0000 [thread overview]
Message-ID: <1452163347.21055.178.camel@citrix.com> (raw)
In-Reply-To: <568CFE3A.8080505@citrix.com>
On Wed, 2016-01-06 at 11:44 +0000, Andrew Cooper wrote:
> All console logging is synchronous (to ensure that log messages have
> escaped the VM before an action occurs) and by default, an HVM test will
> use the qemu debug port, console_io hypercall, and PV console (which
> uses evtchn hypercalls).
All three simultaneously, or it picks one depending on the scenario?
> There are already scenarios under test where we cannot rely on the test
> kernel having a fully functioning set of entry points (e.g. the DPL part
> of the test above). Therefore I specifically want to make it possible
> to make userspace hypercalls, rather than simply making them possible to
> be trapped-and-forwarded.
And in these test cases there is useful logging to be done between the
break the world and repair the world phases which I suppose follows if
things didn't crash?
> As a result, I proposing introducing a hypercall which allows a domain
> to adjust its entry criteria for hypercalls (e.g. set_hypercall_iopl).
> Doing this for HVM guests is straight forward, but PV guests are harder,
> as they bounce through Xen entrypoints.
>
> For PV guests, I propose that userspace hypercalls get implemented with
> the int $0x82 path exclusively. i.e. enabling userspace hypercalls
> causes the hypercall page writing logic to consider the guest a ring1
> kernel, and the int $0x82 entrypoint suitably delegates between a
> regular hypercall and a compat hypercall.
>
> Thoughts?
Would a xenconsoled mode which polls for updates (on specific guests only),
along with the guest spinning waiting for the cons pointer to catch the
prod one if it cares about synchronous logging be sufficient for this use
case?
Other random ideas:
Implement the debug io port for PV guests too
Log to a in guest buffer, as David suggested, possibly use xenaccess or
similar to trap updates or as a doorbell.
>
> ~Andrew
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-07 10:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 11:44 RFC Userspace hypercalls Andrew Cooper
2016-01-06 14:14 ` Jan Beulich
2016-01-06 14:44 ` Andrew Cooper
2016-01-06 16:09 ` Jan Beulich
2016-01-06 16:20 ` Andrew Cooper
2016-01-06 16:24 ` Jan Beulich
2016-01-06 16:31 ` Jan Beulich
2016-01-06 16:38 ` Andrew Cooper
2016-01-06 16:49 ` Jan Beulich
2016-01-06 17:06 ` Andrew Cooper
2016-01-06 16:41 ` David Vrabel
2016-01-07 10:42 ` Ian Campbell [this message]
2016-01-07 10:55 ` 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=1452163347.21055.178.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=tim@xen.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.