From: ebiederm@xmission.com (Eric W. Biederman)
To: Andi Kleen <ak@suse.de>
Cc: James.Bottomley@hansenpartnership.com,
virtualization@lists.osdl.org, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: The virtuailization patches break Voyager.
Date: Sat, 28 Apr 2007 09:24:46 -0600 [thread overview]
Message-ID: <m1fy6kfrnl.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200704281137.52460.ak@suse.de> (Andi Kleen's message of "Sat, 28 Apr 2007 11:37:52 +0200")
Andi Kleen <ak@suse.de> writes:
> On Saturday 28 April 2007 11:15:33 Eric W. Biederman wrote:
>
> Scary thought. But I don't see why people using embedded x86s should suddenly
> design new interrupt controllers etc. - after all the main value of using x86s
> embedded is some degree of compatibility to PC software. Ok, we'll see what
> happens.
Right but visws main difference was that it did not run a x86 BIOS
as I recall. My memory says all of it's hardware was standard.
>> So I think it makes a lot of sense to see if we can fold mach-visws
>> and mach-voyager into appropriate pluggable interfaces.
>
> For voyager and NUMAQ i think it's fine to just wait until the last machine dies
> (James, how many do you have left? @] iirc the number of NUMAQs still in
> operation
> is also slowly decreasing)
Maybe. Again if we could convert them along with everything else to
a modern structure it probably would not matter.
I honestly think it is irresponsible to keep code in tree and not at least
try to keep it working.
Eric
next prev parent reply other threads:[~2007-04-28 15:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 6:40 The virtuailization patches break Voyager Eric W. Biederman
2007-04-28 6:59 ` Jeremy Fitzhardinge
2007-04-28 7:25 ` Eric W. Biederman
2007-04-28 7:52 ` Jeremy Fitzhardinge
2007-04-28 8:32 ` Eric W. Biederman
2007-04-28 8:52 ` Jeremy Fitzhardinge
2007-04-28 9:34 ` Andi Kleen
2007-04-28 16:05 ` James Bottomley
2007-04-28 17:15 ` Andi Kleen
2007-04-28 8:42 ` Andi Kleen
2007-04-28 9:13 ` Thomas Gleixner
2007-04-28 9:15 ` Jeremy Fitzhardinge
2007-04-28 9:39 ` Andi Kleen
2007-04-28 9:48 ` Thomas Gleixner
2007-04-28 9:15 ` Eric W. Biederman
2007-04-28 9:37 ` Andi Kleen
2007-04-28 15:24 ` Eric W. Biederman [this message]
2007-04-28 16:08 ` James Bottomley
2007-04-28 15:54 ` James Bottomley
2007-04-28 17:15 ` Andi Kleen
2007-04-28 16:40 ` H. Peter Anvin
2007-04-28 17:00 ` Eric W. Biederman
2007-04-28 17:07 ` H. Peter Anvin
2007-04-28 15:47 ` James Bottomley
2007-04-28 16:02 ` Eric W. Biederman
2007-04-28 16:18 ` Jeremy Fitzhardinge
2007-04-28 16:20 ` James Bottomley
2007-04-28 17:23 ` Andi Kleen
2007-04-28 17:22 ` Andi Kleen
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=m1fy6kfrnl.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.osdl.org \
/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;
as well as URLs for NNTP newsgroup(s).