qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: David Hildenbrand <david@redhat.com>,
	Eric Farman <farman@linux.ibm.com>,
	 Halil Pasic <pasic@linux.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-s390x@nongnu.org,
	Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org
Subject: Re: [RFC PATCH v5 1/1] s390x: sigp: Reorder the SIGP STOP code
Date: Tue, 18 Jan 2022 15:20:56 +0100	[thread overview]
Message-ID: <c43b5baf-2645-1ba1-a66f-02a28c04835c@redhat.com> (raw)
In-Reply-To: <afbc20ac-5be6-c260-c9aa-afa2980b7b6e@redhat.com>

On 18/01/2022 14.34, David Hildenbrand wrote:
> On 13.12.21 22:09, Eric Farman wrote:
>> Let's wait to mark the VCPU STOPPED until the possible
>> STORE STATUS operation is completed, so that we know the
>> CPU is fully stopped and done doing anything. (When we
>> also clear the possible sigp_order field for STOP orders.)
>>
>> Suggested-by: David Hildenbrand <david@redhat.com>
>> Signed-off-by: Eric Farman <farman@linux.ibm.com>
>> ---
>>   target/s390x/sigp.c | 12 ++++++++----
>>   1 file changed, 8 insertions(+), 4 deletions(-)
>>
>> diff --git a/target/s390x/sigp.c b/target/s390x/sigp.c
>> index 51c727834c..9dd977349a 100644
>> --- a/target/s390x/sigp.c
>> +++ b/target/s390x/sigp.c
>> @@ -139,7 +139,7 @@ static void sigp_stop_and_store_status(CPUState *cs, run_on_cpu_data arg)
>>       case S390_CPU_STATE_OPERATING:
>>           cpu->env.sigp_order = SIGP_STOP_STORE_STATUS;
>>           cpu_inject_stop(cpu);
>> -        /* store will be performed in do_stop_interrup() */
>> +        /* store will be performed in do_stop_interrupt() */
>>           break;
>>       case S390_CPU_STATE_STOPPED:
>>           /* already stopped, just store the status */
>> @@ -479,13 +479,17 @@ void do_stop_interrupt(CPUS390XState *env)
>>   {
>>       S390CPU *cpu = env_archcpu(env);
>>   
>> -    if (s390_cpu_set_state(S390_CPU_STATE_STOPPED, cpu) == 0) {
>> -        qemu_system_shutdown_request(SHUTDOWN_CAUSE_GUEST_SHUTDOWN);
>> -    }
>> +    /*
>> +     * Complete the STOP operation before exposing the CPU as
>> +     * STOPPED to the system.
>> +     */
>>       if (cpu->env.sigp_order == SIGP_STOP_STORE_STATUS) {
>>           s390_store_status(cpu, S390_STORE_STATUS_DEF_ADDR, true);
>>       }
>>       env->sigp_order = 0;
>> +    if (s390_cpu_set_state(S390_CPU_STATE_STOPPED, cpu) == 0) {
>> +        qemu_system_shutdown_request(SHUTDOWN_CAUSE_GUEST_SHUTDOWN);
>> +    }
>>       env->pending_int &= ~INTERRUPT_STOP;
>>   }
>>   
> 
> Reviewed-by: David Hildenbrand <david@redhat.com>
> 

Thanks, queued to my s390x-next branch now:

  https://gitlab.com/thuth/qemu/-/commits/s390x-next/

  Thomas



      reply	other threads:[~2022-01-18 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 21:09 [RFC PATCH v5 0/1] s390x: Improvements to SIGP handling [QEMU] Eric Farman
2021-12-13 21:09 ` [RFC PATCH v5 1/1] s390x: sigp: Reorder the SIGP STOP code Eric Farman
2022-01-18 13:34   ` David Hildenbrand
2022-01-18 14:20     ` Thomas Huth [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=c43b5baf-2645-1ba1-a66f-02a28c04835c@redhat.com \
    --to=thuth@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.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 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).