From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com
Subject: Re: [PATCH kvm-unit-tests v2 0/2] arm/arm64: smp: on_cpu improvements
Date: Wed, 7 Jun 2017 17:00:06 +0200 [thread overview]
Message-ID: <20170607150006.GI28750@potion> (raw)
In-Reply-To: <20170602153109.2904-1-drjones@redhat.com>
2017-06-02 17:31+0200, Andrew Jones:
> After posting on_cpu() support yesterday I thought of some potential
> issues.
> 1) cpu0 was the only cpu allowed to call on_cpus, and no cpu was
> allowed to call on_cpu on cpu0 (as it'll never idle).
> 2) deadlocks are easy with this idle state scheduling model, but
> also easy to detect, so we should.
>
> v2:
> - fix race in cpu_wait() by ordering set/check correctly
Applied, thanks.
prev parent reply other threads:[~2017-06-07 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 15:31 [PATCH kvm-unit-tests v2 0/2] arm/arm64: smp: on_cpu improvements Andrew Jones
2017-06-02 15:31 ` [PATCH kvm-unit-tests v2 1/2] arm/arm64: smp: cpu0 is special Andrew Jones
2017-06-02 15:31 ` [PATCH kvm-unit-tests v2 2/2] arm/arm64: smp: add deadlock detection Andrew Jones
2017-06-03 8:28 ` [PATCH kvm-unit-tests v2 3/2] arm/arm64: smp: detect deadlock cycles Andrew Jones
2017-06-07 15:00 ` Radim Krčmář [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=20170607150006.GI28750@potion \
--to=rkrcmar@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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).