From: malc <av1474@comtv.ru>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Fabien Chouteau <chouteau@adacore.com>
Subject: Re: [Qemu-devel] Multiple instances of Qemu on Windows multicore
Date: Wed, 2 Nov 2011 21:55:57 +0400 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.00.1111022155220.2632@linmac> (raw)
In-Reply-To: <4EB181C4.1090501@redhat.com>
On Wed, 2 Nov 2011, Paolo Bonzini wrote:
> On 11/02/2011 06:16 PM, malc wrote:
> > (mm)Timers have a possibility of running on a thread of their own which
> > might be schedulled on the CPU different from the thread that runs
> > emulated code, unchaining TBs and can (and will) fail in this case.
>
> This should not be a problem with dynticks+iothread (i.e. it should work or
> not work equally). We now run just this basically when an alarm fires:
>
I was explaining rationale behind pinning stuff at the time it was done.
> t->expired = t->pending = 1;
> qemu_notify_event();
>
> The rest is always done in the iothread. The iothread will then
> suspend/resume the VCPU thread around the unchaining, so what matters is (in
> Unix parlance) signal-safety of the unchaining, not thread-safety.
>
> Paolo
>
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2011-11-02 17:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 15:38 [Qemu-devel] Multiple instances of Qemu on Windows multicore Fabien Chouteau
2011-11-02 16:25 ` 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 [this message]
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=alpine.LNX.2.00.1111022155220.2632@linmac \
--to=av1474@comtv.ru \
--cc=chouteau@adacore.com \
--cc=pbonzini@redhat.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 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).