All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>
Cc: KVM <kvm@vger.kernel.org>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	linux-s390 <linux-s390@vger.kernel.org>,
	David Hildenbrand <dahi@linux.vnet.ibm.com>,
	marc.zyngier@arm.com, cdall@cs.columbia.edu
Subject: Re: [GIT PULL 1/2] KVM: s390: allow user space to handle instr 0x0000
Date: Wed, 20 Jul 2016 16:35:49 +0200	[thread overview]
Message-ID: <578F8C45.6060505@de.ibm.com> (raw)
In-Reply-To: <1469018400-8397-2-git-send-email-borntraeger@de.ibm.com>

Marc, Christoffer,
FYI/FYA
the CAP number will conflict with your kvmarm changes.
I assume Paolo/Radim will resolve this when merging.

Seems that you have no hit in api.txt, correct?



> diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
> index c4d2fb0..299306d 100644
> --- a/Documentation/virtual/kvm/api.txt
> +++ b/Documentation/virtual/kvm/api.txt
[...]
> +7.8 KVM_CAP_S390_USER_INSTR0
> +
> +Architectures: s390
[...]

> --- a/include/uapi/linux/kvm.h
> +++ b/include/uapi/linux/kvm.h
> @@ -867,6 +867,7 @@ struct kvm_ppc_smmu_info {
>  #define KVM_CAP_VCPU_ATTRIBUTES 127
>  #define KVM_CAP_MAX_VCPU_ID 128
>  #define KVM_CAP_X2APIC_API 129
> +#define KVM_CAP_S390_USER_INSTR0 130

  reply	other threads:[~2016-07-20 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 12:39 PREVIEW: [GIT PULL 0/2] KVM: s390: Feature and fix for kvm/next (4.8) part 4 Christian Borntraeger
2016-07-20 12:39 ` [GIT PULL 1/2] KVM: s390: allow user space to handle instr 0x0000 Christian Borntraeger
2016-07-20 14:35   ` Christian Borntraeger [this message]
2016-07-20 14:43     ` Paolo Bonzini
2016-07-20 17:47     ` Marc Zyngier
2016-07-20 12:40 ` [GIT PULL 2/2] KVM: s390: let ptff intercepts result in cc=3 Christian Borntraeger
2016-07-20 12:41 ` PREVIEW: [GIT PULL 0/2] KVM: s390: Feature and fix for kvm/next (4.8) part 4 Christian Borntraeger
2016-07-21 13:07 ` Radim Krčmář

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=578F8C45.6060505@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=cdall@cs.columbia.edu \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dahi@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@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.