From: "Jan Beulich" <JBeulich@suse.com>
To: Kevin Tian <kevin.tian@intel.com>
Cc: Ian Jackson <Ian.Jackson@citrix.com>,
Paul Durrant <Paul.Durrant@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v10 1/3] ioreq-server: add support for multiple servers
Date: Wed, 04 Jun 2014 07:23:58 +0100 [thread overview]
Message-ID: <538ED79E02000078000179BD@mail.emea.novell.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D125EB6811@SHSMSX103.ccr.corp.intel.com>
>>> On 03.06.14 at 21:14, <kevin.tian@intel.com> wrote:
> One basic question first, though I think the answer is likely no. Is this
> ioreq server designed solely for multiple servers in user space? XenGT
> has all the necessary bits in a kernel driver in Dom0, except legacy VGA
> emulation still carried by Qemu. So want to make sure no obvious
> limitation against our usage.
The only slightly restricting factor (mechanical, not functional) I can
think of might be the need to use supposedly toolstack only control
operations from the kernel to set up such a server.
Jan
next prev parent reply other threads:[~2014-06-04 6:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 10:38 [PATCH v10 0/3] Support for running secondary emulators Paul Durrant
2014-05-22 10:38 ` [PATCH v10 1/3] ioreq-server: add support for multiple servers Paul Durrant
2014-05-22 13:26 ` Jan Beulich
2014-05-22 13:59 ` Paul Durrant
2014-05-28 8:39 ` Paul Durrant
2014-06-06 21:02 ` Daniel De Graaf
2014-06-02 8:05 ` Jan Beulich
2014-06-02 8:34 ` Paul Durrant
2014-06-02 8:40 ` Jan Beulich
2014-06-03 19:14 ` Tian, Kevin
2014-06-04 6:23 ` Jan Beulich [this message]
2014-06-04 8:33 ` Paul Durrant
2014-05-22 10:38 ` [PATCH v10 2/3] ioreq-server: remove p2m entries when server is enabled Paul Durrant
2014-05-22 10:38 ` [PATCH v10 3/3] ioreq-server: make buffered ioreq handling optional Paul Durrant
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=538ED79E02000078000179BD@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Jackson@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=Stefano.Stabellini@citrix.com \
--cc=kevin.tian@intel.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 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).