From: Christoph Hellwig <hch@infradead.org>
To: Andi Kleen <ak@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Zachary Amsden <zach@vmware.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 8/8 Create MMU 2/3 level accessors in the sub-arch layer (i386)
Date: Sat, 6 Aug 2005 13:01:41 +0100 [thread overview]
Message-ID: <20050806120141.GA1827@infradead.org> (raw)
In-Reply-To: <20050806115836.GN8266@wotan.suse.de>
On Sat, Aug 06, 2005 at 01:58:36PM +0200, Andi Kleen wrote:
> > > 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.
> >
> > Especially as there's been no user shown for it, similar to all the other
> > ugly patches from vmware.
>
> Well, some of it can be counted as cleanup or even tuning like the excellent
> switch_to patch. But not that one and some of the more intrusive patches.
Yeah, I said ugly ones specificly. There's been some nice previous ones,
but most in this series (all the move of stuff to subarches) are rather
horrible and lack lots of explanation.
next prev parent reply other threads:[~2005-08-06 12:01 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 ` [PATCH] 8/8 Create MMU 2/3 level accessors in the sub-arch layer (i386) Andi Kleen
2005-08-06 11:56 ` Christoph Hellwig
2005-08-06 11:58 ` Andi Kleen
2005-08-06 12:01 ` Christoph Hellwig [this message]
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=20050806120141.GA1827@infradead.org \
--to=hch@infradead.org \
--cc=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.