All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu on 2.6.0-rc1
Date: Wed, 07 Jan 2004 12:53:40 +1100	[thread overview]
Message-ID: <20040107015929.BBFF22C21D@lists.samba.org> (raw)
In-Reply-To: Your message of "Tue, 06 Jan 2004 22:48:54 BST." <3FFB2D46.90002@free.fr>

In message <3FFB2D46.90002@free.fr> you write:
> It seems I need to update the documentation :-)
> 
> Did you try to submit the non QEMU specific patches to Linus ? I think 
> it is dangerous to leave harcoded constants in somes parts of the kernel.

I'll see if Andrew takes the whole thing first.  If not, I'll submit
the "cleanup" part by itself.  I'd really like the whole thing.

> BTW, in the current CVS, qemu-fast is about 2.3 times faster as the 
> previous version (still 9 times slower than native on a P2 500 MHz on a 
> typical 'gcc -pipe' compilation task which involves a lot of task 
> switches).

0.5.1 feels about 10x slower booting the kernel (didn't measure, but
it's that order of mag).  Under 3 would really sway me...

> and SMP is getting closer now with my last changes.

Any idea when it'll be testable?  And do you prefer cash or check?

Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2004-01-07  3:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 22:31 [Qemu-devel] qemu on 2.6.0-rc1 Rutger Nijlunsing
2004-01-05 23:01 ` J. Mayer
2004-01-06  0:57 ` Rusty Russell
2004-01-06 21:48   ` Fabrice Bellard
2004-01-07  1:53     ` Rusty Russell [this message]
2004-01-07  7:01       ` Herbert Poetzl
2004-01-07 21:33         ` Fabrice Bellard
2004-01-07 21:41           ` Daniel Jacobowitz
2004-01-07 21:37       ` Fabrice Bellard

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=20040107015929.BBFF22C21D@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --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 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.