kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: KVM <kvm@vger.kernel.org>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Tony Krowiak <akrowiak@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/5] KVM: s390: SIE considerations for AP Queue virtualization
Date: Wed, 8 Nov 2017 10:06:47 +0100	[thread overview]
Message-ID: <20171108100647.4b2a22b6.cohuck@redhat.com> (raw)
In-Reply-To: <20171108084143.78654-3-borntraeger@de.ibm.com>

On Wed,  8 Nov 2017 09:41:40 +0100
Christian Borntraeger <borntraeger@de.ibm.com> wrote:

> From: Tony Krowiak <akrowiak@linux.vnet.ibm.com>
> 
> The Crypto Control Block (CRYCB) is referenced by the SIE state
> description and controls KVM guest access to the Adjunct
> Processor (AP) adapters, usage domains and control domains.
> This patch defines the AP control blocks to be used for
> controlling guest access to the AP adapters and domains.
> 
> Signed-off-by: Tony Krowiak <akrowiak@linux.vnet.ibm.com>
> Message-Id: <1507916344-3896-2-git-send-email-akrowiak@linux.vnet.ibm.com>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
>  arch/s390/include/asm/kvm_host.h | 25 +++++++++++++++++++++----
>  1 file changed, 21 insertions(+), 4 deletions(-)

I obviously can't verify (no doc), but I trust that you have done so,
so:

Acked-by: Cornelia Huck <cohuck@redhat.com>

  reply	other threads:[~2017-11-08  9:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08  8:41 [PATCH 0/5] KVM: s390: patches for 4.15 Christian Borntraeger
2017-11-08  8:41 ` [PATCH 1/5] KVM: s390: document memory ordering for kvm_s390_vcpu_wakeup Christian Borntraeger
2017-11-08  9:05   ` Cornelia Huck
2017-11-08  9:37   ` David Hildenbrand
2017-11-08  8:41 ` [PATCH 2/5] KVM: s390: SIE considerations for AP Queue virtualization Christian Borntraeger
2017-11-08  9:06   ` Cornelia Huck [this message]
2017-11-08  9:29   ` David Hildenbrand
2017-11-09  8:59     ` Christian Borntraeger
2017-11-08  8:41 ` [PATCH 3/5] KVM: s390: vsie: use common code functions for pinning Christian Borntraeger
2017-11-08  9:07   ` Cornelia Huck
2017-11-08  8:41 ` [PATCH 4/5] KVM: s390: abstract conversion between isc and enum irq_types Christian Borntraeger
2017-11-08  9:11   ` Cornelia Huck
2017-11-08  9:41   ` David Hildenbrand
2017-11-08  8:41 ` [PATCH 5/5] KVM: s390: clear_io_irq() requests are not expected for adapter interrupts Christian Borntraeger
2017-11-08  9:19   ` Cornelia Huck
2017-11-08 11:04     ` Christian Borntraeger
2017-11-08 11:09       ` Cornelia Huck
2017-11-08 12:14         ` Michael Mueller
2017-11-13 12:25           ` Cornelia Huck
2017-11-08 11:10 ` [PATCH 0/5] KVM: s390: patches for 4.15 Cornelia Huck

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=20171108100647.4b2a22b6.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=akrowiak@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.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).