All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Eric Farman <farman@linux.ibm.com>,
	Halil Pasic <pasic@linux.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Thomas Huth <thuth@redhat.com>
Cc: qemu-s390x@nongnu.org,
	Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org, Janosch Frank <frankja@linux.ibm.com>
Subject: Re: [RFC PATCH v1 2/2] s390x/kvm: Pass SIGP Stop flags
Date: Mon, 11 Oct 2021 09:09:25 +0200	[thread overview]
Message-ID: <0addcdbc-50cb-420d-5864-af3a8a894321@redhat.com> (raw)
In-Reply-To: <20211008203811.1980478-3-farman@linux.ibm.com>

On 08.10.21 22:38, Eric Farman wrote:
> When building a Stop IRQ to pass to KVM, we should incorporate
> the flags if handling the SIGP Stop and Store Status order.
> With that, KVM can reject other orders that are submitted for
> the same CPU while the operation is fully processed.
> 
> Signed-off-by: Eric Farman <farman@linux.ibm.com>
> Acked-by: Janosch Frank <frankja@linux.ibm.com>
> ---
>   target/s390x/kvm/kvm.c | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> diff --git a/target/s390x/kvm/kvm.c b/target/s390x/kvm/kvm.c
> index 5b1fdb55c4..701b9ddc88 100644
> --- a/target/s390x/kvm/kvm.c
> +++ b/target/s390x/kvm/kvm.c
> @@ -2555,6 +2555,10 @@ void kvm_s390_stop_interrupt(S390CPU *cpu)
>           .type = KVM_S390_SIGP_STOP,
>       };
>   
> +    if (cpu->env.sigp_order == SIGP_STOP_STORE_STATUS) {
> +        irq.u.stop.flags = KVM_S390_STOP_FLAG_STORE_STATUS;
> +    }
> +

KVM_S390_STOP_FLAG_STORE_STATUS tells KVM to perform the store status as 
well ... is that really what we want?

Maybe we want a different (more generic) way to tell KVM that a CPU is 
temporarily busy for SIGP orders?

-- 
Thanks,

David / dhildenb



  reply	other threads:[~2021-10-11  7:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 20:38 [RFC PATCH v1 0/2] Improvements to SIGP handling [QEMU] Eric Farman
2021-10-08 20:38 ` [RFC PATCH v1 1/2] s390x: sigp: Force Set Architecture to return Invalid Parameter Eric Farman
2021-10-09  5:40   ` Thomas Huth
2021-10-11  7:04   ` David Hildenbrand
2021-10-08 20:38 ` [RFC PATCH v1 2/2] s390x/kvm: Pass SIGP Stop flags Eric Farman
2021-10-11  7:09   ` David Hildenbrand [this message]
2021-10-11  8:40     ` Christian Borntraeger
2021-10-11  9:21       ` David Hildenbrand
2021-10-11 17:58         ` Eric Farman
2021-10-11 18:07           ` David Hildenbrand
2021-10-12  6:58 ` [RFC PATCH v1 0/2] Improvements to SIGP handling [QEMU] Thomas Huth

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=0addcdbc-50cb-420d-5864-af3a8a894321@redhat.com \
    --to=david@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --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.