qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, 陳韋任 <chenwj@iis.sinica.edu.tw>
Subject: Re: [Qemu-devel] Multi-threaded user program support?
Date: Fri, 19 Aug 2011 09:19:00 -0700	[thread overview]
Message-ID: <4E4E8CF4.80605@twiddle.net> (raw)
In-Reply-To: <CAFEAcA_u3YHmvwAUN-grbNVCWbgxAjrPb2ZDM8_=o_PMhAGv+g@mail.gmail.com>

On 08/18/2011 08:13 PM, Peter Maydell wrote:
> On 19 August 2011 03:59, 陳韋任 <chenwj@iis.sinica.edu.tw> wrote:
>>> More generally and not x86-specific, there are problems with
>>> the multithreaded user-mode support which I suspect exist because
>>> nobody has ever sat down and worked out a coherent design for it,
>>> including what might need to be thread-local and what locking
>>> is required. So the result is that it mostly works but if you
>>
>>  You mean some QEMU data structures need to be thread-local or lock
>> protected in order to emulate guest multi-threaded program correctly?
> 
> Approximately, yes (the third option being "redesign the data
> structure so it can be sensibly protected"). See
> https://bugs.launchpad.net/qemu/+bug/668799 for discussion of
> one example.

I suspect that to make things tractable for i386, which has so
many LOCKable instructions, that we'll also have to implement
at least a compare-and-swap primitive in TCG.


r~

  reply	other threads:[~2011-08-19 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18  2:35 [Qemu-devel] Multi-threaded user program support? 陳韋任
2011-08-18  3:00 ` Peter Maydell
2011-08-19  2:59   ` 陳韋任
2011-08-19  3:13     ` Peter Maydell
2011-08-19 16:19       ` Richard Henderson [this message]
2011-08-20  2:35   ` 陳韋任

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=4E4E8CF4.80605@twiddle.net \
    --to=rth@twiddle.net \
    --cc=chenwj@iis.sinica.edu.tw \
    --cc=peter.maydell@linaro.org \
    --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).