From: Halil Pasic <pasic@linux.ibm.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: Halil Pasic <pasic@linux.ibm.com>, Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: [PATCH 0/2] two atomic_cmpxchg() related fixes
Date: Tue, 16 Jun 2020 06:50:33 +0200 [thread overview]
Message-ID: <20200616045035.51641-1-pasic@linux.ibm.com> (raw)
The story short: compiler can generate code that does two
distinct fetches of *ind_addr for old and _old. If that happens we can
not figure out if we had the desired xchg or not.
Halil Pasic (2):
virtio-ccw: fix virtio_set_ind_atomic
s390x/pci: fix set_ind_atomic
hw/s390x/s390-pci-bus.c | 16 +++++++++-------
hw/s390x/virtio-ccw.c | 18 ++++++++++--------
2 files changed, 19 insertions(+), 15 deletions(-)
base-commit: 7d3660e79830a069f1848bb4fa1cdf8f666424fb
--
2.17.1
next reply other threads:[~2020-06-16 4:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 4:50 Halil Pasic [this message]
2020-06-16 4:50 ` [PATCH 1/2] virtio-ccw: fix virtio_set_ind_atomic Halil Pasic
2020-06-16 5:58 ` Christian Borntraeger
2020-06-16 6:33 ` Cornelia Huck
2020-06-16 6:45 ` Christian Borntraeger
2020-06-19 7:14 ` Cornelia Huck
2020-06-17 23:56 ` Halil Pasic
2020-06-19 7:33 ` David Hildenbrand
2020-06-19 8:17 ` Halil Pasic
2020-06-16 9:31 ` Halil Pasic
2020-07-01 13:13 ` Christian Borntraeger
2020-07-04 18:34 ` Michael S. Tsirkin
2020-07-06 5:44 ` Christian Borntraeger
2020-07-06 11:19 ` Halil Pasic
2020-06-16 4:50 ` [PATCH 2/2] s390x/pci: fix set_ind_atomic Halil Pasic
2020-07-01 13:14 ` Christian Borntraeger
2020-07-01 12:01 ` [PATCH 0/2] two atomic_cmpxchg() related fixes Cornelia Huck
2020-07-01 12:06 ` Christian Borntraeger
2020-07-01 13:10 ` Cornelia Huck
2020-07-03 13:37 ` Halil Pasic
2020-07-03 14:03 ` Cornelia Huck
2020-07-02 11:18 ` Cornelia Huck
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=20200616045035.51641-1-pasic@linux.ibm.com \
--to=pasic@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=mjrosato@linux.ibm.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
/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.