From: Keir Fraser <keir@xensource.com>
To: Ky Srinivasan <ksrinivasan@novell.com>, xen-devel@lists.xensource.com
Subject: Re: HVM hypercalls
Date: Fri, 15 Dec 2006 19:54:28 +0000 [thread overview]
Message-ID: <C1A8ADF4.62BF%keir@xensource.com> (raw)
In-Reply-To: <458297C8.E57C.0030.0@novell.com>
On 15/12/06 18:46, "Ky Srinivasan" <ksrinivasan@novell.com> wrote:
> Currently, only a very small subset of the hypercalls are exposed to HVM
> guests. Was this set arrived at based on what was required to host
> para-virtualized drivers? Or are there other considerations that governed
> this decision. Specifically, would there be any objections to opening up more
> hypercalls to HVM guests.
They need auditing one-by-one, and also we have to worry about 32-on-64
compatibility issues (which will be helped by the PV PAE-on-64 work by Jan
Beulich). We do plan to broaden the supported set of hypercalls (memory_op
for example).
-- Keir
next prev parent reply other threads:[~2006-12-15 19:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 18:46 HVM hypercalls Ky Srinivasan
2006-12-15 19:54 ` Keir Fraser [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-19 14:38 HVM Hypercalls Kumar, Venkat
2008-08-19 14:53 ` Keir Fraser
2008-08-20 11:48 ` Kumar, Venkat
2008-08-20 12:11 ` Keir Fraser
2010-07-28 19:22 HVM hypercalls Ruslan Nikolaev
2010-07-29 1:05 ` Dan Magenheimer
2010-07-29 7:30 ` Juergen Gross
2010-07-29 18:55 ` Ruslan Nikolaev
2010-07-29 19:47 ` Jeremy Fitzhardinge
2010-07-30 16:06 ` Ruslan Nikolaev
2010-07-31 0:07 ` Jeremy Fitzhardinge
2010-08-03 19:48 ` Ruslan Nikolaev
2010-08-03 21:40 ` Jeremy Fitzhardinge
2010-08-04 17:41 ` Ruslan Nikolaev
2010-08-05 7:25 ` Christoph Egger
2010-08-05 10:31 ` Stefano Stabellini
2011-05-23 7:48 ` veeruyours
2011-05-23 8:22 ` Ian Campbell
2011-05-23 13:52 ` veerasena reddy
2011-05-24 12:06 ` Ian Campbell
2011-05-24 13:58 ` veeruyours
2011-05-24 14:09 ` Ian Campbell
2011-05-25 7:38 ` veeruyours
2010-08-02 0:32 Ruslan Nikolaev
2010-08-03 20:30 Ruslan Nikolaev
2010-08-06 21:58 Ruslan Nikolaev
2010-08-09 9:41 ` Stefano Stabellini
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=C1A8ADF4.62BF%keir@xensource.com \
--to=keir@xensource.com \
--cc=ksrinivasan@novell.com \
--cc=xen-devel@lists.xensource.com \
/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).