From: Mark McLoughlin <markmc@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Michael Abd-El-Malek <mabdelmalek@cmu.edu>
Subject: Re: Vanilla Linux 64-bit paravirt guest support
Date: Tue, 06 May 2008 17:22:57 +0100 [thread overview]
Message-ID: <1210090977.12273.3.camel@muff> (raw)
In-Reply-To: <1207836684.16779.8.camel@muff>
On Thu, 2008-04-10 at 15:11 +0100, 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.
>
> > Redhat have some patches which they're shipping in Fedora 9. Once F9 is
> > out the door, I'm hoping they'll polish them into an upstreamable form.
> > I don't know whether that git tree represents what's in F9, or if that's
> > somewhere else; at the very least I'd expect you'd be able to pull the
> > patches out of the srpm.
>
> Yep, this tree:
>
> http://git.et.redhat.com/?p=xen-pvops-64.git
>
> is the work-in-progress x86_64 tree.
FYI, here's the config options that's currently needed to get this tree
working:
# CONFIG_SMP is not set
# CONFIG_NUMA is not set
# CONFIG_NEED_MULTIPLE_NODES is not set
# x86_64 breaks with a different CONFIG_PHYSICAL_START, currently
CONFIG_PHYSICAL_START=0x200000
# x86_64 breaks with CONFIG_SPARSEMEM_VMEMMAP, currently
# CONFIG_SPARSEMEM_VMEMMAP is not set
# 32-bit emulation isn't ready yet
# CONFIG_IA32_EMULATION is not set
Cheers,
Mark.
prev parent reply other threads:[~2008-05-06 16:22 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
2008-05-06 16:22 ` Mark McLoughlin [this message]
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=1210090977.12273.3.camel@muff \
--to=markmc@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jeremy@goop.org \
--cc=mabdelmalek@cmu.edu \
--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.