virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Andi Kleen <ak@suse.de>
Cc: zippel@linux-m68k.org, moriai.satoshi@lab.ntt.co.jp,
	Yoshimi Ichiyanagi <ichiyanagi.yoshimi@lab.ntt.co.jp>,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] i386: modified CONFIG_PHYSICAL_ALIGN
Date: Tue, 14 Aug 2007 13:17:28 +1000	[thread overview]
Message-ID: <1187061448.11093.63.camel@localhost.localdomain> (raw)
In-Reply-To: <20070814032903.GB3903@bingen.suse.de>

On Tue, 2007-08-14 at 05:29 +0200, Andi Kleen wrote:
> On Tue, Aug 14, 2007 at 09:55:50AM +0900, Yoshimi Ichiyanagi wrote:
> 
> How is this related to virtualization?
> 
> > The problem is, if you compile x86_64 kernel, the value of 
> > CONFIG_PHYSICAL_ALIGN will be fixed, and the next time you compile i386 
> > kernel, previous CONFIG_PHYSICAL_ALIGN value of x86_64(default: 2MB) will 
> > be used by default.
> 
> 2/4MB is better for i386 too for PAE/non PAE because
> it will use less TLB entries. I guess it's better to just change
> the defaults.
> 
> Anyways, both values should work, or did you see 
> failures?

I had this problem too: Lguest assumes 1MB when loading bzImages, and
the only time that gets changed is when building from an x86-64 config.
I considered it purely an lguest issue.

The correct fix is to have lguest run bzImages rather than trying to
unpack them itself, but that requires a bootloader change, and the
proposals to do that got lost in a flurry of far more ambitious patches.

Jeremy would know the status of that work...
Rusty.

  reply	other threads:[~2007-08-14  3:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14  0:55 [PATCH] i386: modified CONFIG_PHYSICAL_ALIGN Yoshimi Ichiyanagi
2007-08-14  3:29 ` Andi Kleen
2007-08-14  3:17   ` Rusty Russell [this message]
2007-08-14  8:59     ` Yoshimi Ichiyanagi
2007-08-14 18:35     ` Jeremy Fitzhardinge

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=1187061448.11093.63.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=ak@suse.de \
    --cc=ichiyanagi.yoshimi@lab.ntt.co.jp \
    --cc=moriai.satoshi@lab.ntt.co.jp \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=zippel@linux-m68k.org \
    /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).