From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: n schembr <nschembr@yahoo.com>
Subject: Re: QEMU Automated Testing (was [Qemu-devel] qemu Makefile.target vl.h hw/acpi.c hw/adlib.c ...)
Date: Fri, 27 Jul 2007 12:55:08 -0500 [thread overview]
Message-ID: <46AA317C.7010908@codemonkey.ws> (raw)
In-Reply-To: <200707271838.20201.paul@codesourcery.com>
Paul Brook wrote:
>>> As Qemu cannot use multicore CPUs (partially due to missing thread
>>> safety), yet, you won't benefit from this unless you want to run
>>> multiple instances of Qemu in parallel.
>>>
>> how close is thread safey?
>>
>
> In a useful form: a fair way off.
>
> It's relatively simple to hack something together than runs. Making it work
> correctly and go fast is much harder though. My current prototype (running on
> 2 cores) runs about a quarter the speed of normal qemu, and dies shortly
> after booting because the guest atomic synchronisation primitives don't work
> right.
>
This later problem seems like the hardest to solve to me. Did you have
any ideas here that don't involve hand coding the translation for atomic
instructions?
Regards,
Anthony Liguori
> Either way, for a tinderbox or automated testing yo *do* have lots of
> different tests you can run in parallel, so it doesn't matter that each qemu
> instance only uses one core. We're only talking about small SMP here - maybe
> 16 cores, but not thousands.
>
> Paul
>
>
>
>
next prev parent reply other threads:[~2007-07-27 17:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 17:15 QEMU Automated Testing (was [Qemu-devel] qemu Makefile.target vl.h hw/acpi.c hw/adlib.c ...) n schembr
2007-07-27 17:38 ` Paul Brook
2007-07-27 17:55 ` Anthony Liguori [this message]
2007-07-27 22:03 ` Paul Brook
-- strict thread matches above, loose matches on Subject: below --
2007-07-27 22:59 n schembr
2007-04-07 18:14 [Qemu-devel] qemu Makefile.target vl.h hw/acpi.c hw/adlib.c Paul Brook
2007-04-07 20:45 ` Paul Brook
2007-04-07 22:18 ` J. Mayer
2007-04-07 23:13 ` Paul Brook
2007-04-07 23:54 ` J. Mayer
2007-04-08 0:04 ` Thiemo Seufer
2007-04-08 7:49 ` IRQ handling (was [Qemu-devel] qemu Makefile.target vl.h hw/acpi.c hw/adlib.c ...) J. Mayer
2007-04-08 14:41 ` Thiemo Seufer
2007-04-08 16:31 ` J. Mayer
2007-04-08 20:43 ` QEMU Automated Testing " Natalia Portillo
2007-04-08 22:07 ` Eduardo Felipe
2007-04-08 23:53 ` Natalia Portillo
2007-04-09 9:36 ` Eduardo Felipe
2007-04-09 21:19 ` Rob Landley
2007-04-10 11:24 ` Jamie Lokier
2007-04-10 12:00 ` Pierre d'Herbemont
2007-07-27 14:21 ` Dan Shearer
2007-07-27 14:29 ` Anthony Liguori
2007-07-27 14:34 ` Dan Shearer
2007-07-27 14:58 ` Sunil Amitkumar Janki
2007-07-27 15:12 ` Dan Shearer
2007-07-27 15:50 ` Sunil Amitkumar Janki
2007-07-27 16:04 ` Dan Shearer
2007-07-27 16:50 ` Jan Marten Simons
2007-07-27 18:51 ` Thiemo Seufer
2007-07-27 19:55 ` Sunil Amitkumar Janki
2007-07-28 10:17 ` Thiemo Seufer
2007-07-28 11:41 ` Sunil Amitkumar Janki
2007-07-27 18:54 ` Andreas Färber
2007-07-28 10:36 ` Thiemo Seufer
2007-07-29 15:31 ` Andreas Färber
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=46AA317C.7010908@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=nschembr@yahoo.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 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.