From: Paolo Bonzini <pbonzini@redhat.com>
To: Francois WELLENREITER <francois.wellenreiter@bull.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PCI CAS implementation in qemu
Date: Tue, 20 Nov 2012 17:48:18 +0100 [thread overview]
Message-ID: <50ABB452.4070401@redhat.com> (raw)
In-Reply-To: <50ABB0A4.9030600@bull.net>
Il 20/11/2012 17:32, Francois WELLENREITER ha scritto:
>
> I order to develop a qemu module, I aim to use the PCI CAS (compare
> and swap) function to guarantee an atomic access somewhere in the
> guest memory (in a multi-core emulation case).
>
> Nevertheless, I did not find any routine in qemu implementing this
> function.
>
> Could anyone on this list tell me if this is implemented and if that's
> not the case, if this would be hard to get implemented ?
(I know nothing about PCI CAS).
Can you just use a compare-and-swap in the QEMU device model (via
__sync_val_compare_and_swap for example)?
Paolo
prev parent reply other threads:[~2012-11-20 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 16:32 [Qemu-devel] PCI CAS implementation in qemu Francois WELLENREITER
2012-11-20 16:48 ` Paolo Bonzini [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=50ABB452.4070401@redhat.com \
--to=pbonzini@redhat.com \
--cc=francois.wellenreiter@bull.net \
--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).