public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jan Beulich <jbeulich@novell.com>,
	Glauber de Oliveira Costa <glommer@gmail.com>
Subject: [PATCH 0/4] pagetable unification: this time for sure!
Date: Fri, 14 Dec 2007 00:11:59 -0800	[thread overview]
Message-ID: <47623ACF.3050108@goop.org> (raw)

Here's a new set of patches.  I've compiled tested:

    * 32-bit PAE paravirt
    * 32-bit non-PAE paravirt
    * 32-bit PAE non-paravirt
    * 32-bit non-PAE non-paravirt
    * 64-bit

and test-booted them to usermode under kvm (though I'm currently typing
this under 32-bit PAE paravirt).

The patches are based on linux-2.6-x86.git commit
022b7918fe3ac93ea171558e95d391efe82af4bb.

The net effect of these patches is little more than refactoring and code
motion, though I wouldn't expect the generated code to be identical.

    J

                 reply	other threads:[~2007-12-14  8:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47623ACF.3050108@goop.org \
    --to=jeremy@goop.org \
    --cc=glommer@gmail.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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