All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	xen-devel@lists.xensource.com
Subject: Re: [PATCH] let XEN depend on PAE
Date: Fri, 22 Feb 2008 16:00:13 +0100	[thread overview]
Message-ID: <47BEE37D.8040703@nets.rwth-aachen.de> (raw)
In-Reply-To: <1203687425.15721.45.camel@localhost.localdomain>

Ian Campbell schrieb:
> On Fri, 2008-02-22 at 12:00 +0100, Arnd Hannemann wrote:
>> As paravirtualized xen guests won't work with !X86_PAE, change the Kconfig
>> accordingly.
> 
> Really? Xen guests should work on non-PAE if you have a non-PAE
> hypervisor (which most distros don't ship but which does exist).

Well if it should work, then something else is broken.
I have a non-PAE hypervisor, still xen guests compiled with !X86_PAE
from 2.6.24.2  and latest git won't work.
All the same with PAE enabled works.

http://lists.xensource.com/archives/html/xen-devel/2008-02/msg00716.html

> 
> Ian.
> 

Best regards,
Arnd

  reply	other threads:[~2008-02-22 15:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 11:00 [PATCH] let XEN depend on PAE Arnd Hannemann
2008-02-22 13:37 ` Ian Campbell
2008-02-22 15:00   ` Arnd Hannemann [this message]
2008-02-22 16:37 ` [Xen-devel] " Jeremy Fitzhardinge
2008-02-22 16:54   ` Arnd Hannemann
2008-02-22 18:59     ` Jeremy Fitzhardinge
2008-02-22 18:59       ` Jeremy Fitzhardinge
2008-02-22 19:45       ` [Xen-devel] " Arnd Hannemann
2008-02-22 19:45         ` Arnd Hannemann
2008-02-22 21:13         ` [Xen-devel] " Jeremy Fitzhardinge
2008-02-22 21:13           ` Jeremy Fitzhardinge
2008-02-23 12:37         ` [Xen-devel] " Arnd Hannemann

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=47BEE37D.8040703@nets.rwth-aachen.de \
    --to=hannemann@nets.rwth-aachen.de \
    --cc=ijc@hellion.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --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.