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 09:57:37 -0500 [thread overview]
Message-ID: <47FE2AE1.4020404@goop.org> (raw)
In-Reply-To: <3883AEC7-3636-4809-8516-8870C1B9C7C4@cmu.edu>
Michael Abd-El-Malek wrote:
> On Apr 10, 2008, at 10:11 AM, Mark McLoughlin wrote:
>> On Thu, 2008-04-10 at 09:01 -0500, Jeremy Fitzhardinge wrote:
>>> Michael Abd-El-Malek wrote:
>>>> Is 64-bit domU support available anywhere at the moment? For example,
>>>> what is the status of the git://git.et.redhat.com/xen-pvops-64.git
>>>> tree? I pulled that tree and tried building 64-bit Xen domU support
>>>> (since this tree allows you to configure the kernel with that
>>>> capability, unlike the vanilla Linux tree). But compilation failed in
>>>> enlighten.c because xen_smp_ops isn't defined in x86_64.
>>
>> Try building without CONFIG_SMP, it doesn't support that yet.
>
> Other than SMP support, does the tree represent a fully functional
> 64-bit PV domU support? Does it also allow all hypercalls? Put
> another way: is a 64-bit PV domU from that tree less capable than a
> 64-bit PV domU from Xen's linux-2.6.18.8 tree?
The 32-bit domU implementation is less capable than 2.6.18-xen. For
example, it does not yet support suspend/resume/migrate or ballooning,
and a number of interesting features are not yet in a released kernel
(pvfb). Further out I hope we'll get things like dom0 support in as well.
(I'm not sure what you mean by "allow all hypercalls"; do you mean "all
features"?)
J
next prev parent reply other threads:[~2008-04-10 14:57 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 [this message]
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
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=47FE2AE1.4020404@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.