xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
	Xen-devel List <xen-devel@lists.xen.org>
Subject: Re: RFC Userspace hypercalls
Date: Wed, 6 Jan 2016 16:41:18 +0000	[thread overview]
Message-ID: <568D43AE.1030007@citrix.com> (raw)
In-Reply-To: <568D4F6502000078000C418C@prv-mh.provo.novell.com>

On 06/01/16 16:31, Jan Beulich wrote:
>>>> On 06.01.16 at 15:44, <andrew.cooper3@citrix.com> wrote:
>> We did have an internal request for an HVM guest userspace netfront
>> driver to be able to use evntchnop calls directly.
> 
> And this can't be accomplished using the evtchn and/or privcmd
> drivers?

It can and should be done with the evtchn driver.

Even for tests I think it should return to kernel mode to perform
hypercalls.  Tests should not run in a "magic" mode that normal guests
won't use.

If there are failure cases where return to kernel isn't possible and
some logging would be useful, perhaps writing to a memory buffer and
retrieving this via a crash dump would be ok?

David

  parent reply	other threads:[~2016-01-06 16:41 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 [this message]
2016-01-07 10:42 ` Ian Campbell
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=568D43AE.1030007@citrix.com \
    --to=david.vrabel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).