From: Jeremy Fitzhardinge <jeremy@goop.org>
To: tglx@linutronix.de
Cc: James.Bottomley@hansenpartnership.com,
virtualization@lists.osdl.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: The virtuailization patches break Voyager.
Date: Sat, 28 Apr 2007 02:15:16 -0700 [thread overview]
Message-ID: <463310A4.1050806@goop.org> (raw)
In-Reply-To: <1177751601.7646.58.camel@localhost.localdomain>
Thomas Gleixner wrote:
> Last test was 2.6.21-rc7, where I fixed the non-WP thing. The
> FP-emulator seems to work.
>
> Which kind of breakage is new ?
>
We were just speculating about what breakage might exist. If you've
been applying anti-entropy to real 80386 machines, then I guess it
probably works better than I would have otherwise expected.
J
next prev parent reply other threads:[~2007-04-28 9:15 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 [this message]
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
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=463310A4.1050806@goop.org \
--to=jeremy@goop.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--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 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.