From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] testandset asm fix
Date: Mon, 07 Feb 2005 19:46:49 +0100 [thread overview]
Message-ID: <4207B799.6020707@bellard.org> (raw)
In-Reply-To: <20050207173448.GA26461@xi.wantstofly.org>
Lennert Buytenhek wrote:
> On Mon, Feb 07, 2005 at 02:47:29PM +0100, Fabrice Bellard wrote:
>
>
>>OK. Anyway, the locking in QEMU is mostly boggus. If SMP is
>>implemented someday with host threads, then it will be the right
>>time to correct it !
>
>
> Differences in strict/loose memory ordering between different
> processor types will be a bigger problem for SMP emulation, IMHO.
> What are your plans on that?
For x86 on x86 it won't be a problem if we use the same locking
instructions. For the rest, using high level locks might suffice at the
expense of efficiency. In the worst case we can simply not use threads
and do explicit scheduling based on a cycle counter.
Fabrice.
prev parent reply other threads:[~2005-02-07 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 14:43 [Qemu-devel] testandset asm fix Paul Brook
2005-02-07 13:03 ` Piotras
2005-02-07 13:47 ` Fabrice Bellard
2005-02-07 14:26 ` Piotras
2005-02-07 14:28 ` Piotras
2005-02-07 17:34 ` Lennert Buytenhek
2005-02-07 18:46 ` Fabrice Bellard [this message]
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=4207B799.6020707@bellard.org \
--to=fabrice@bellard.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).