qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: sparc64 lazy conditional codes evaluation
Date: Mon, 10 May 2010 10:40:05 +0100	[thread overview]
Message-ID: <4BE7D475.6020205@siriusit.co.uk> (raw)
In-Reply-To: <i2lf43fc5581005091322q81cb89cfoab4b9ae448a51102@mail.gmail.com>

Blue Swirl wrote:

> Thanks a lot, with this patch my tests passed! I applied the combined patch.

Yes, I definitely see an improvement with this patch - at least my 
Debian lenny SPARC boot cd doesn't randomly kernel panic any more. It 
looks as if it now just can't find /init which could just be due to an 
incorrect device mapping somewhere.

> I also did a bit of refactoring to get the original Sparc64 issue fixed.

However, one thing I did notice is that this does introduce a noticeable 
performance penalty. With OpenBIOS SVN head I see the following:

With commit 72139e83a98eba2bfed2dbc2db2818fb19e47ca0 (just before the 
changes):

[   59.225406] Failed to execute /init
[   59.304088] Kernel panic - not syncing: No init found.  Try passing 
init= option to kernel.
[   59.450313] Press Stop-A (L1-A) to return to the boot prom

With commit 5a834bb47c373e887de5210b7ceae96e1ef413f7 (just after the 
changes):

[   70.384466] Failed to execute /init
[   70.474804] Kernel panic - not syncing: No init found.  Try passing 
init= option to kernel.


So while it's technically correct, it seems to have added ~15% overhead 
to the emulation :(


ATB,

Mark.

-- 
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063

Sirius Labs: http://www.siriusit.co.uk/labs

  reply	other threads:[~2010-05-10  9:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03  7:17 [Qemu-devel] sparc64 lazy conditional codes evaluation Igor Kovalenko
2010-05-03 19:24 ` [Qemu-devel] " Blue Swirl
2010-05-03 19:46   ` Igor Kovalenko
2010-05-03 19:54     ` Blue Swirl
2010-05-03 20:03       ` Igor Kovalenko
2010-05-04 20:21         ` Blue Swirl
2010-05-05 20:24           ` Igor Kovalenko
2010-05-06 18:51             ` Blue Swirl
2010-05-08  6:41               ` Igor Kovalenko
2010-05-09 20:22                 ` Blue Swirl
2010-05-10  9:40                   ` Mark Cave-Ayland [this message]
2010-05-10 18:33                     ` Blue Swirl
2010-05-15 12:56                       ` Mark Cave-Ayland

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=4BE7D475.6020205@siriusit.co.uk \
    --to=mark.cave-ayland@siriusit.co.uk \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.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).