All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabien Chouteau <chouteau@adacore.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Multiple instances of Qemu on Windows multicore
Date: Wed, 02 Nov 2011 16:38:55 +0100	[thread overview]
Message-ID: <4EB1640F.2090604@adacore.com> (raw)

Hello fellow Qemu aficionados,

On Windows, Qemu sets the affinity mask in order to run all thread on
CPU0, with this comment in the code (os-win32.c:182):

    /* Note: cpu_interrupt() is currently not SMP safe, so we force
       QEMU to run on a single CPU */

This was added by Fabrice Bellard in 2006 (git show a8e5ac33d).

I can't find/understand any reason for this CPU affinity restriction. So
I'm asking to the experts:

 1 - Is this comment still applicable?
 2 - If yes, what is the problem with cpu_interrupt on SMP?
 3 - Why is this different on Linux?

This is a real drawback, especially to run automated tests.

Thanks in advance,

-- 
Fabien Chouteau

             reply	other threads:[~2011-11-02 15:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 15:38 Fabien Chouteau [this message]
2011-11-02 16:25 ` [Qemu-devel] Multiple instances of Qemu on Windows multicore Paolo Bonzini
2011-11-02 17:10   ` Fabien Chouteau
2011-11-02 17:16     ` malc
2011-11-02 17:45       ` Paolo Bonzini
2011-11-02 17:55         ` malc
2011-11-02 18:01         ` Peter Maydell
2011-11-02 19:52           ` Paolo Bonzini
2011-11-02 19:57             ` Peter Maydell
2011-11-03  9:56               ` Fabien Chouteau
2011-11-03  9:54             ` Fabien Chouteau
2011-11-03 10:10               ` Paolo Bonzini
2011-11-03 10:29                 ` Avi Kivity
2011-11-03 11:50                   ` Paolo Bonzini
2011-11-04  9:27                     ` Fabien Chouteau
2011-11-04  9:34                       ` Paolo Bonzini

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=4EB1640F.2090604@adacore.com \
    --to=chouteau@adacore.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.