public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: kvm@vger.kernel.org, borntraeger@de.ibm.com, thuth@redhat.com,
	david@redhat.com, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org, scgl@linux.ibm.com,
	seiden@linux.ibm.com, nrb@linux.ibm.com
Subject: Re: [PATCH v14 3/6] KVM: s390: pv: add KVM_CAP_S390_PROTECTED_ASYNC_DISABLE
Date: Mon, 10 Oct 2022 14:15:11 +0200	[thread overview]
Message-ID: <20221010141511.25eca963@p-imbrenda> (raw)
In-Reply-To: <748d07b8-1746-c12a-ccfb-89c8b15901d9@linux.ibm.com>

On Mon, 10 Oct 2022 13:45:54 +0200
Janosch Frank <frankja@linux.ibm.com> wrote:

> On 9/30/22 16:01, Claudio Imbrenda wrote:
> > Add KVM_CAP_S390_PROTECTED_ASYNC_DISABLE to signal that the
> > KVM_PV_ASYNC_DISABLE and KVM_PV_ASYNC_DISABLE_PREPARE commands for the
> > KVM_S390_PV_COMMAND ioctl are available.
> > 
> > Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> > Reviewed-by: Nico Boehr <nrb@linux.ibm.com>
> > ---
> >   arch/s390/kvm/kvm-s390.c | 3 +++
> >   include/uapi/linux/kvm.h | 1 +
> >   2 files changed, 4 insertions(+)
> > 
> > diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> > index d0027964a6f5..7a3bd68efd85 100644
> > --- a/arch/s390/kvm/kvm-s390.c
> > +++ b/arch/s390/kvm/kvm-s390.c
> > @@ -618,6 +618,9 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
> >   	case KVM_CAP_S390_BPB:
> >   		r = test_facility(82);
> >   		break;
> > +	case KVM_CAP_S390_PROTECTED_ASYNC_DISABLE:
> > +		r = async_destroy && is_prot_virt_host();
> > +		break;
> >   	case KVM_CAP_S390_PROTECTED:
> >   		r = is_prot_virt_host();
> >   		break;
> > diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
> > index 02602c5c1975..9afe0084b2c5 100644
> > --- a/include/uapi/linux/kvm.h
> > +++ b/include/uapi/linux/kvm.h
> > @@ -1177,6 +1177,7 @@ struct kvm_ppc_resize_hpt {
> >   #define KVM_CAP_VM_DISABLE_NX_HUGE_PAGES 220
> >   #define KVM_CAP_S390_ZPCI_OP 221
> >   #define KVM_CAP_S390_CPU_TOPOLOGY 222
> > +#define KVM_CAP_S390_PROTECTED_ASYNC_DISABLE 225  
> 
> I can see 223 in Paolo's next, is there a 224 that I've missed?

no, I set this to an arbitrarily high value to avoid conficts

seems like I got it more or less right :)

feel free to change the value of the macro when merging, so it's
contiguous.

> 
> 
> >   
> >   #ifdef KVM_CAP_IRQ_ROUTING
> >     
> 


  reply	other threads:[~2022-10-10 12:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 14:01 [PATCH v14 0/6] KVM: s390: pv: implement lazy destroy for reboot Claudio Imbrenda
2022-09-30 14:01 ` [PATCH v14 1/6] KVM: s390: pv: asynchronous " Claudio Imbrenda
2022-10-04 13:43   ` Steffen Eiden
2022-10-04 16:56     ` Claudio Imbrenda
2022-10-10 11:38   ` Janosch Frank
2022-09-30 14:01 ` [PATCH v14 2/6] KVM: s390: pv: api documentation for asynchronous destroy Claudio Imbrenda
2022-10-04 13:43   ` Steffen Eiden
2022-10-10 11:41   ` Janosch Frank
2022-09-30 14:01 ` [PATCH v14 3/6] KVM: s390: pv: add KVM_CAP_S390_PROTECTED_ASYNC_DISABLE Claudio Imbrenda
2022-10-04 13:44   ` Steffen Eiden
2022-10-10 11:45   ` Janosch Frank
2022-10-10 12:15     ` Claudio Imbrenda [this message]
2022-10-10 13:10       ` Janosch Frank
2022-09-30 14:01 ` [PATCH v14 4/6] KVM: s390: pv: avoid export before import if possible Claudio Imbrenda
2022-10-04 13:47   ` Steffen Eiden
2022-09-30 14:01 ` [PATCH v14 5/6] KVM: s390: pv: support for Destroy fast UVC Claudio Imbrenda
2022-10-04 13:48   ` Steffen Eiden
2022-09-30 14:01 ` [PATCH v14 6/6] KVM: s390: pv: module parameter to fence asynchronous destroy Claudio Imbrenda
2022-10-04 13:48   ` Steffen Eiden

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=20221010141511.25eca963@p-imbrenda \
    --to=imbrenda@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nrb@linux.ibm.com \
    --cc=scgl@linux.ibm.com \
    --cc=seiden@linux.ibm.com \
    --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