All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1] s390x: refactor reset/reipl handling
Date: Wed, 9 May 2018 16:36:07 +0200	[thread overview]
Message-ID: <20180509163607.499e13af.cohuck@redhat.com> (raw)
In-Reply-To: <7c418965-f96f-fbbc-0010-8dd853280f6b@redhat.com>

On Wed, 9 May 2018 16:15:38 +0200
David Hildenbrand <david@redhat.com> wrote:

> On 24.04.2018 12:18, David Hildenbrand wrote:
> > Calling pause_all_vcpus()/resume_all_vcpus() from a VCPU thread might
> > not be the best idea. As pause_all_vcpus() temporarily drops the qemu
> > mutex, two parallel calls to pause_all_vcpus() can be active at a time,
> > resulting in a deadlock. (either by two VCPUs or by the main thread and a
> > VCPU)
> > 
> > Let's handle it via the main loop instead, as suggested by Paolo. If we
> > would have two parallel reset requests by two different VCPUs at the
> > same time, the last one would win.
> > 
> > We use the existing ipl device to handle it. The nice side effect is
> > that we can get rid of reipl_requested.
> > 
> > This change implies that all reset handling now goes via the common
> > path, so "no-reboot" handling is now active for all kinds of reboots.
> > 
> > Let's execute any CPU initialization code on the target CPU using
> > run_on_cpu.
> > 
> > Signed-off-by: David Hildenbrand <david@redhat.com>
> > ---
> > 
> > RFC -> v1:
> > - initital -> initial
> > - get rid of goto
> > - store CPU index instead of CPU. Fallback to any CPU in case not found
> > - handle default case in switch-case  
> 
> Very friendly ping :)

I'm currently inclined to just go ahead and merge it -- so if anyone
still wants to provide review, now's the time :)

  reply	other threads:[~2018-05-09 14:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 10:18 [Qemu-devel] [PATCH v1] s390x: refactor reset/reipl handling David Hildenbrand
2018-04-26  9:50 ` Cornelia Huck
2018-05-09 14:15 ` David Hildenbrand
2018-05-09 14:36   ` Cornelia Huck [this message]
2018-05-09 16:56 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-05-14  9:24 ` [Qemu-devel] " Cornelia Huck
2018-06-21 15:49 ` Christian Borntraeger
2018-06-21 16:04   ` David Hildenbrand
2018-06-21 16:04   ` Cornelia Huck
2018-06-21 16:06     ` Christian Borntraeger
2018-06-21 16:08       ` David Hildenbrand
2018-06-21 16:59         ` Paolo Bonzini
2018-06-21 16:07     ` David Hildenbrand
2018-06-21 16:10       ` Christian Borntraeger
2018-06-21 16:15   ` David Hildenbrand
2018-06-21 16:20     ` Christian Borntraeger
2018-06-21 16:21       ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-06-21 16:22         ` David Hildenbrand

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=20180509163607.499e13af.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=pbonzini@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.