From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Michael Abd-El-Malek <mabdelmalek@cmu.edu>
Cc: Mark McLoughlin <markmc@redhat.com>,
xen-devel <xen-devel@lists.xensource.com>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: Vanilla Linux 64-bit paravirt guest support
Date: Thu, 10 Apr 2008 10:40:24 -0500 [thread overview]
Message-ID: <47FE34E8.6010606@goop.org> (raw)
In-Reply-To: <9BAE25D5-5463-4C00-890E-551B6EBFBAFD@cmu.edu>
Michael Abd-El-Malek wrote:
> For my purposes, suspend/resume/migrate isn't required. But I might
> need ballooning. Would I be able to take the balloon driver from
> 2.6.18.8 and use it in those new trees? The new tree seems to have
> all the hypercalls and defines the
> increase_reservation/decrease_reservation op codes. I can add the
> stub code for these calls.
I have pending patches for balloon support in x86.git
(http://people.redhat.com/mingo/x86.git/README)
>> (I'm not sure what you mean by "allow all hypercalls"; do you mean
>> "all features"?)
>
> I was thinking along the lines of grant hypercalls for mapping another
> domU's grants. HVM can't let me do that. But I need to be able to do
> this for my work.
If you have a kernel driver, then you can use those hypercalls.
J
next prev parent reply other threads:[~2008-04-10 15:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 4:20 Vanilla Linux 64-bit paravirt guest support Michael Abd-El-Malek
2008-04-08 21:29 ` Jeremy Fitzhardinge
2008-04-10 4:14 ` Michael Abd-El-Malek
2008-04-10 14:01 ` Jeremy Fitzhardinge
2008-04-10 14:11 ` Mark McLoughlin
2008-04-10 14:25 ` Jeremy Fitzhardinge
2008-04-10 14:40 ` Mark McLoughlin
2008-04-10 15:04 ` Jeremy Fitzhardinge
2008-04-19 15:11 ` Bastian Blank
2008-04-10 14:32 ` Michael Abd-El-Malek
2008-04-10 14:49 ` Mark McLoughlin
2008-04-10 14:57 ` Jeremy Fitzhardinge
2008-04-10 15:06 ` Fix a typo in p2m.c Huang2, Wei
2008-04-10 15:14 ` Vanilla Linux 64-bit paravirt guest support Michael Abd-El-Malek
2008-04-10 15:40 ` Jeremy Fitzhardinge [this message]
2008-05-06 16:22 ` Mark McLoughlin
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=47FE34E8.6010606@goop.org \
--to=jeremy@goop.org \
--cc=ehabkost@redhat.com \
--cc=mabdelmalek@cmu.edu \
--cc=markmc@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.