From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
Richard Henderson <rth@twiddle.net>,
Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1] s390x/tcg: fix locking problem with tcg_s390_tod_updated
Date: Mon, 2 Jul 2018 10:30:19 +0200 [thread overview]
Message-ID: <20180702103019.5b333e33.cohuck@redhat.com> (raw)
In-Reply-To: <20180629170520.13671-1-david@redhat.com>
On Fri, 29 Jun 2018 19:05:20 +0200
David Hildenbrand <david@redhat.com> wrote:
> tcg_s390_tod_updated() is always called with the iothread being locked
> (e.g. from S390TODClass->set() e.g. via HELPER(sck) or on incomming
s/incomming/incoming/
> migration). The helper we call takes the lock itself - bad.
>
> Let's change that by factoring out updating the ckc timer. This now looks
> much nicer than having to call a helper from another function.
>
> While touch it we also make sure that env->ckc is updated even if the new
s/touch/touching/
> value is -1ULL, for now it would not have been modified in that case.
>
> Reported-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
>
> This survives my tests and the iotests Christian mentioned.
OK, this will the last patch (I guess) before I send my final 3.0 pull
request.
>
> target/s390x/misc_helper.c | 26 ++++++++++++++++----------
> 1 file changed, 16 insertions(+), 10 deletions(-)
Thanks, applied.
prev parent reply other threads:[~2018-07-02 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 17:05 [Qemu-devel] [PATCH v1] s390x/tcg: fix locking problem with tcg_s390_tod_updated David Hildenbrand
2018-06-29 17:24 ` Richard Henderson
2018-07-02 8:30 ` Cornelia Huck [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=20180702103019.5b333e33.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=david@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 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).