From: Keir Fraser <keir@xen.org>
To: Ian Campbell <Ian.Campbell@citrix.com>,
David Vrabel <david.vrabel@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Scalable Event Channel ABI design (draft A)
Date: Tue, 05 Feb 2013 18:02:01 +0000 [thread overview]
Message-ID: <CD36F999.5A4AC%keir@xen.org> (raw)
In-Reply-To: <1360080697.23001.28.camel@zakaz.uk.xensource.com>
On 05/02/2013 16:11, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:
>>> Okay, I wonder how much it actually matters anyhow...
>>>
>>> Oh by the way you say the control block is 128 bytes and will easily fit in
>>> the existing struct vcpu_info. That existing structure is 64 bytes in total.
>>> So how does that work then?
>>
>> I meant struct vcpu_info can be extended without it growing to more than
>> a page. i.e., it fits into the guest page provided in the
>> VCPUOP_register_vcpu_info call so no additional pages need to be
>> globally mapped for the control block.
>
> VCPUOP_register_vcpu_info doesn't require each vcpu_info to be on a page
> by itself, even if that happens to be the Linux implementation today (I
> haven't checked that).
Having guest agree that vcpu_info grows by size of the per-vcpu control
block, if using this new event-channel interface, is reasonable though.
-- Keir
next prev parent reply other threads:[~2013-02-05 18:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 17:52 Scalable Event Channel ABI design (draft A) David Vrabel
2013-02-04 19:59 ` Keir Fraser
2013-02-05 14:48 ` David Vrabel
2013-02-05 15:16 ` Wei Liu
2013-02-05 18:05 ` George Dunlap
2013-02-05 18:57 ` David Vrabel
2013-02-05 19:03 ` Wei Liu
2013-02-06 11:32 ` George Dunlap
2013-02-06 13:53 ` Keir Fraser
2013-03-14 19:20 ` David Vrabel
2013-02-05 15:49 ` Keir Fraser
2013-02-05 15:54 ` David Vrabel
2013-02-05 16:11 ` Ian Campbell
2013-02-05 18:02 ` Keir Fraser [this message]
2013-02-06 9:38 ` Ian Campbell
2013-02-06 10:41 ` Keir Fraser
2013-02-06 10:42 ` Wei Liu
2013-02-06 10:52 ` Ian Campbell
2013-02-06 11:09 ` Wei Liu
2013-02-05 16:11 ` Keir Fraser
2013-02-06 11:46 ` Jan Beulich
2013-02-04 21:07 ` Wei Liu
2013-02-04 22:16 ` Keir Fraser
2013-02-05 18:36 ` David Vrabel
2013-02-05 16:10 ` Ian Campbell
2013-02-05 18:18 ` David Vrabel
2013-02-06 9:35 ` Ian Campbell
2013-02-06 9:13 ` Ian Campbell
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=CD36F999.5A4AC%keir@xen.org \
--to=keir@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=wei.liu2@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).