LKML Archive on
help / color / mirror / Atom feed
From: (Eric W. Biederman)
To: Jeremy Fitzhardinge <>
Cc: "H. Peter Anvin" <>,
	Andrew Morton <>,
	Andi Kleen <>, Zachary Amsden <>,
	Linux Kernel Mailing List <>
Subject: Re: [PATCH] i386: For debugging, make the initial page table setup less forgiving.
Date: Wed, 25 Apr 2007 13:01:19 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Jeremy Fitzhardinge's message of "Wed, 25 Apr 2007 11:18:12 -0700")

Jeremy Fitzhardinge <> writes:

> I might have introduced it as part of the paravirt_ops patches.  When
> setting up pagetables under Xen, we need to make sure we preserve the
> initial mappings Xen put in place (it starts the VM with paging enabled,
> and a sane initial pagetable).  This may have leaked over into native if
> it doesn't replace an existing entry.

Yes in paravirt_ops-hooks-to-set-up-initial-pagetable
Grr.  That is what I get for trying to avoid conflicts by working
against the -mm tree.

I thought that code had been like that for a while.  Since it hasn't
been merged upstream it looks to me like that patch needs to be fixed.
And we can keep HPA debugging patch.

> Hm, but it should be overwriting small mappings with large ones.  Maybe
> I overlooked that.

Nope.  It's not overwriting anything.  I'm not at all convinced we
should preserve the Xen sillyness.  I'm not exactly against it,
but it adds complexity to already complex code.

>> I'm halfway through putting together a patchset to address a
>> bunch of these.
>> I haven't yet resolved how I want to allocate the pages for the
>> identity mapping of the page table yet.  I can't use the bootmem
>> allocate as it exists because that assumes the page is mapped
>> into the address space already.
> Are you going to clash horribly with the paravirt pagetable setup?  We
> should probably coordinate if so.

We will have to see.  Currently the paravirt pagetable setup clashes
horrible with actually running a kernel on real hardware.

Color me not impressed by the paravirt mess.


  reply	other threads:[~2007-04-25 19:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-13 21:49 H. Peter Anvin
2007-04-13 22:18 ` Zachary Amsden
2007-04-13 22:26   ` H. Peter Anvin
2007-04-13 22:40     ` Zachary Amsden
2007-04-13 22:26   ` Jeremy Fitzhardinge
2007-04-25 11:48 ` Andrew Morton
2007-04-25 15:28   ` H. Peter Anvin
2007-04-25 17:50     ` Eric W. Biederman
2007-04-25 17:56       ` H. Peter Anvin
2007-04-25 18:23         ` Eric W. Biederman
2007-04-25 18:18       ` Jeremy Fitzhardinge
2007-04-25 19:01         ` Eric W. Biederman [this message]
2007-04-25 19:19           ` Jeremy Fitzhardinge
2007-04-25 22:08           ` Jeremy Fitzhardinge
2007-04-25 22:27             ` Eric W. Biederman
2007-04-25 23:08               ` Jeremy Fitzhardinge
2007-04-25 23:45                 ` Eric W. Biederman
2007-04-26  0:14                   ` Jeremy Fitzhardinge
2007-04-27  5:02                     ` Eric W. Biederman
2007-04-26  3:27                   ` Zachary Amsden

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] i386: For debugging, make the initial page table setup less forgiving.' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).