All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Mark Burton <mark.burton@greensocs.com>, mttcg@greensocs.com
Cc: Developers qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Atomic Instructions - comments please
Date: Mon, 15 Dec 2014 14:16:46 +0100	[thread overview]
Message-ID: <548EDF3E.2070407@redhat.com> (raw)
In-Reply-To: <5AD68BB8-35E0-4752-BD46-FA3CA9BC7F34@greensocs.com>



On 15/12/2014 13:56, Mark Burton wrote:
> A third proposal is to mark pages as IO when a ld/st ex is performed to
> them. Then to augment the memory API to indicate that a ld/st ex is in
> hand, allowing the memory chain to decide if it should allow the write
> or cause a fault. This would seem to be the closest approach to the real
> H/W. However it means marking pages as IO (which could cause us issues
> if there was code on that page?, or slow things down) - and it means
> adding to the memory API.

What are the intended semantics for reads/writes from the outside world?
 Should they cause the ll/sc pair to retry or not?

If not, it should not need any change to the memory API; you can do it
entirely within cputlb.c, roughly the same as the handling of
TLB_NOTDIRTY.  It also marks pages as I/O, but only internally within TCG.

Paolo

  reply	other threads:[~2014-12-15 13:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 12:56 [Qemu-devel] Atomic Instructions - comments please Mark Burton
2014-12-15 13:16 ` Paolo Bonzini [this message]
2014-12-15 13:23   ` Peter Maydell
2014-12-15 13:28     ` Paolo Bonzini
2014-12-15 13:36       ` Peter Maydell
2014-12-15 14:09   ` Peter Maydell
2014-12-15 13:28 ` Peter Maydell
2014-12-15 13:32   ` Paolo Bonzini
2014-12-15 13:37     ` Mark Burton
2014-12-15 13:39     ` Peter Maydell
2014-12-15 13:43       ` Mark Burton
2014-12-15 13:46       ` Paolo Bonzini
2014-12-15 13:35   ` Mark Burton
2014-12-15 18:15     ` Lluís Vilanova

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=548EDF3E.2070407@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=mark.burton@greensocs.com \
    --cc=mttcg@greensocs.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.