From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] CPU scheduling with TCG in SMP system emulation mode
Date: Fri, 10 May 2013 17:08:48 +0200 [thread overview]
Message-ID: <518D0D80.8000307@embedded-brains.de> (raw)
In-Reply-To: <CAMo8Bf+L2Ko0c8xH3bywr+moV2uLLciaX=sNxzronv8-v7YYjw@mail.gmail.com>
On 02/22/2013 01:46 AM, Max Filippov wrote:
> Hello.
>
> Do I understand it right that there's no dedicated mechanism
> other than icount that would switch current CPU in emulated
> SMP system and that in the absence of icount such scheduling
> is a side effect of interrupt delivery to the current CPU?
>
In case I start two CPUs and execute a while (1) loop in both of them with
interrupts disabled. Will Qemu ever switch from one CPU to the other?
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
parent reply other threads:[~2013-05-10 15:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAMo8Bf+L2Ko0c8xH3bywr+moV2uLLciaX=sNxzronv8-v7YYjw@mail.gmail.com>]
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=518D0D80.8000307@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--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).