public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	jbeulich@novell.com
Subject: Re: i387/FPU init issues...
Date: Sun, 04 May 2008 11:06:52 -0400	[thread overview]
Message-ID: <1209913612.6972.89.camel@localhost> (raw)
In-Reply-To: <004701c8ade8$266832c0$0201a8c0@zeug>


On Sun, 2008-04-05 at 15:08 +0200, Sebastian Herbszt wrote:


> this is the same result i get with qemu 0.8.2. 

Thanks for validating. 
I am embarassed to say I am still running version 0.7.0 - problem is i
have patched it semi-substantially to add features which i didnt get
much luck in pushing in; so i cant upgrade overnight.

> With version 0.9.0 and
> later it is:

Ok, maybe it is time to invest time to forward port my patches. I dont
see anything in the release notes between 0.8.2 and 0.9.0 which says
this problem was known and fixed in some specific version. Any pointers?

Thanks again - you saved me a lot of time.

cheers,
jamal


  reply	other threads:[~2008-05-04 15:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-03 10:32 i387/FPU init issues jamal
2008-05-03 10:57 ` James Courtier-Dutton
2008-05-03 13:53   ` jamal
2008-05-03 15:31 ` Thomas Gleixner
2008-05-03 17:02   ` jamal
2008-05-03 17:34     ` Ingo Molnar
2008-05-03 17:39       ` Thomas Gleixner
2008-05-04 21:31         ` Jan Engelhardt
2008-05-04 21:37           ` H. Peter Anvin
2008-05-05 13:00           ` Lennart Sorensen
2008-05-03 18:48     ` H. Peter Anvin
2008-05-03 20:07       ` Mikael Pettersson
2008-05-03 20:03     ` H. Peter Anvin
2008-05-03 17:42   ` H. Peter Anvin
2008-05-03 17:50     ` James Courtier-Dutton
2008-05-03 17:51       ` H. Peter Anvin
2008-05-03 18:18     ` Thomas Gleixner
2008-05-03 18:58       ` Mikael Pettersson
2008-05-03 19:03         ` H. Peter Anvin
2008-05-03 19:08         ` H. Peter Anvin
2008-05-03 19:17           ` Thomas Gleixner
2008-05-03 19:24             ` H. Peter Anvin
2008-05-03 19:54               ` Ingo Molnar
2008-05-03 19:56                 ` H. Peter Anvin
2008-05-03 19:49     ` Maciej W. Rozycki
2008-05-03 20:06       ` H. Peter Anvin
2008-05-03 21:17         ` Maciej W. Rozycki
2008-05-03 21:46           ` jamal
     [not found]         ` <Pine.LNX.4.55.0805032209480.20206@c <1209851170.6972.64.camel@localhost>
2008-05-04 13:08           ` Sebastian Herbszt
2008-05-04 15:06             ` jamal [this message]
2008-05-04 15:21               ` Sebastian Herbszt
2008-05-04 20:24         ` Arjan van de Ven
2008-05-04 21:07           ` H. Peter Anvin

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=1209913612.6972.89.camel@localhost \
    --to=hadi@cyberus.ca \
    --cc=arjan@linux.intel.com \
    --cc=herbszt@gmx.de \
    --cc=hpa@zytor.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    /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