From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@suse.de>,
Chris Wright <chrisw@sous-sol.org>,
Zachary Amsden <zach@vmware.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "[PATCH] paravirt: Add startup infrastructure for paravirtualization"
Date: Fri, 04 May 2007 07:59:53 -0700 [thread overview]
Message-ID: <463B4A69.6020203@goop.org> (raw)
In-Reply-To: <m1y7k4smmo.fsf@ebiederm.dsl.xmission.com>
Eric W. Biederman wrote:
> It's not theatrical. It makes this code path extremely brittle and
> very hard to change, which over the long term means that it is
> impossible to maintain. Quickly resulting in a state where any little
> change will break something.
Removing the code now is premature. I'm presuming you're proposing this
as a .23 change, since we're planning on changing the paravirt boot to
make use of bzImage and the boot protocol then anyway.
The world isn't going to fall apart if its in there for a couple of months.
J
next prev parent reply other threads:[~2007-05-04 15:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 11:56 [PATCH] Revert "[PATCH] paravirt: Add startup infrastructure for paravirtualization" Eric W. Biederman
2007-05-04 12:12 ` Rusty Russell
2007-05-04 14:13 ` Eric W. Biederman
2007-05-04 14:37 ` Rusty Russell
2007-05-04 15:07 ` Eric W. Biederman
2007-05-05 1:22 ` Rusty Russell
2007-05-05 2:45 ` David Miller
2007-05-05 3:14 ` Eric W. Biederman
2007-05-05 3:50 ` David Miller
2007-05-05 2:53 ` Eric W. Biederman
2007-05-05 3:22 ` Rusty Russell
2007-05-05 11:18 ` [PATCH] lguest: don't use paravirt_probe, it's dying Rusty Russell
2007-05-07 1:53 ` Eric W. Biederman
2007-05-04 15:58 ` [PATCH] Revert "[PATCH] paravirt: Add startup infrastructure for paravirtualization" Andrew Morton
2007-05-05 1:55 ` Rusty Russell
2007-05-04 14:59 ` Jeremy Fitzhardinge [this message]
2007-05-04 15:20 ` Eric W. Biederman
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=463B4A69.6020203@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox