From: Andi Kleen <ak@suse.de>
To: Zachary Amsden <zach@vmware.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 8/8 Create MMU 2/3 level accessors in the sub-arch layer (i386)
Date: 06 Aug 2005 13:37:31 +0200 [thread overview]
Message-ID: <p73wtmz1ekk.fsf@bragg.suse.de> (raw)
In-Reply-To: <42F46558.9010202@vmware.com.suse.lists.linux.kernel>
Zachary Amsden <zach@vmware.com> writes:
> i386 Transparent paravirtualization sub-arch patch #8.
>
> Transparent paravirtualization support for MMU operations.
>
> All operations which update live page table entries have been moved to the
> sub-architecture layer. Unfortunately, this required yet another parallel set
> of pgtable-Nlevel-ops.h files, but this avoids the ugliness of having to use
> #ifdef's all of the code.
>
> This is pure code motion. Anything else would be a bug.
I think that patch is really ugly - it makes hacking VM on i386
even more painful than it already is because the convolutes the file
structure even more. Hope it is not applied.
-Andi
next parent reply other threads:[~2005-08-06 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42F46558.9010202@vmware.com.suse.lists.linux.kernel>
2005-08-06 11:37 ` Andi Kleen [this message]
2005-08-06 11:56 ` [PATCH] 8/8 Create MMU 2/3 level accessors in the sub-arch layer (i386) Christoph Hellwig
2005-08-06 11:58 ` Andi Kleen
2005-08-06 12:01 ` Christoph Hellwig
2005-08-06 18:28 ` Zachary Amsden
2005-08-06 22:58 ` Andrew Morton
2005-08-06 23:02 ` Chris Wright
2005-08-07 10:39 ` Zachary Amsden
2005-08-06 7:23 Zachary Amsden
2005-08-07 1:16 ` Chris Wright
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=p73wtmz1ekk.fsf@bragg.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zach@vmware.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.