All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice.bellard@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu on 2.6.0-rc1
Date: Tue, 06 Jan 2004 22:48:54 +0100	[thread overview]
Message-ID: <3FFB2D46.90002@free.fr> (raw)
In-Reply-To: <20040106054159.81B182C04F@lists.samba.org>

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.

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).

I am planning simple x86 host specific optimisations to get closer to 
native performance... and SMP is getting closer now with my last changes.

Fabrice.

Rusty Russell wrote:
> In message <20040105223155.GA14669@best.ms.philips.com> you write:
> 
>> Hi,
>> 
>> I try to run qemu-fast on Linux kernel 2.6.0-rc1. I could not find
>> the things which I should change in the documentation:
> 
> 
> Here's my patch, included below.  2.6.0 requires the vsyscall area to
>  move as well.
> 
> Sure, you can run the non-fast qemu, but it's MUCH slower.
> 
> Andrew?   This patch also has the benifit of moving all the constants
>  to one place, as well as adding a CONFIG_QEMU option.  I use it for 
> testing all the time.
> 
> Thanks, Rusty.

  reply	other threads:[~2004-01-06 22:51 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 [this message]
2004-01-07  1:53     ` Rusty Russell
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=3FFB2D46.90002@free.fr \
    --to=fabrice.bellard@free.fr \
    --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.