From: "Jan Beulich" <JBeulich@suse.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: Ian Jackson <Ian.Jackson@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: Mon, 02 Jun 2014 09:40:45 +0100 [thread overview]
Message-ID: <538C54AD0200007800016B55@mail.emea.novell.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD038BC94@AMSPEX01CL01.citrite.net>
>>> On 02.06.14 at 10:34, <Paul.Durrant@citrix.com> wrote:
>> -----Original Message-----
>> From: Jan Beulich [mailto:JBeulich@suse.com]
>> Sent: 02 June 2014 09:05
>> To: Paul Durrant
>> Cc: Ian Jackson; Stefano Stabellini; xen-devel@lists.xen.org
>> Subject: Re: [PATCH v10 1/3] ioreq-server: add support for multiple servers
>>
>> >>> On 22.05.14 at 12:38, <paul.durrant@citrix.com> wrote:
>> > The previous single ioreq server that was created on demand now
>> > becomes the default server and an API is created to allow secondary
>> > servers, which handle specific IO ranges or PCI devices, to be added.
>> >
>> > When the guest issues an IO the list of secondary servers is checked
>> > for a matching IO range or PCI device. If none is found then the IO
>> > is passed to the default server.
>> >
>> > Secondary servers use guest pages to communicate with emulators, in
>> > the same way as the default server. These pages need to be in the
>> > guest physmap otherwise there is no suitable reference that can be
>> > queried by an emulator in order to map them. Therefore a pool of
>> > pages in the current E820 reserved region, just below the special
>> > pages is used. Secondary servers allocate from and free to this pool
>> > as they are created and destroyed.
>> >
>> > The size of the pool is currently hardcoded in the domain build at a
>> > value of 8. This should be sufficient for now and both the location and
>> > size of the pool can be modified in future without any need to change the
>> > API.
>> >
>> > Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
>> > Acked-by: Ian Campbell <ian.campbell@citrix.com>
>>
>> I committed and pushed this, but I had to fix up two build errors
>> with XSM enabled. Please in the future make sure patches you
>> submit build in all relevant modes.
>>
>
> Apologies. I didn't realise I had to explicitly enable it in the build.
In fact any XSM changes would need to be tested both ways - with
in enabled (non-default) and disabled (default).
Jan
next prev parent reply other threads:[~2014-06-02 8:40 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 [this message]
2014-06-03 19:14 ` Tian, Kevin
2014-06-04 6:23 ` Jan Beulich
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=538C54AD0200007800016B55@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Jackson@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=Stefano.Stabellini@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 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).