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>
Subject: Re: [PATCH 0/5] KVM: s390: patches for 4.15
Date: Wed, 8 Nov 2017 12:10:53 +0100 [thread overview]
Message-ID: <20171108121053.172fa481.cohuck@redhat.com> (raw)
In-Reply-To: <20171108084143.78654-1-borntraeger@de.ibm.com>
On Wed, 8 Nov 2017 09:41:38 +0100
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> My next pull request will be pretty small it seems as exitless
> interrupt, crypto and large page support are all not ready yet.
I'm looking forward to the exitless interrupt patches :)
> Anyway here is what I have pending as of today and what will
> be part of my next pull request.
Yup, looks sane to me.
>
> Christian Borntraeger (1):
> KVM: s390: document memory ordering for kvm_s390_vcpu_wakeup
>
> David Hildenbrand (1):
> KVM: s390: vsie: use common code functions for pinning
>
> Michael Mueller (2):
> KVM: s390: abstract conversion between isc and enum irq_types
> KVM: s390: clear_io_irq() requests are not expected for adapter
> interrupts
>
> Tony Krowiak (1):
> KVM: s390: SIE considerations for AP Queue virtualization
>
> Documentation/virtual/kvm/devices/s390_flic.txt | 3 ++
> arch/s390/include/asm/kvm_host.h | 25 +++++++++++--
> arch/s390/kvm/interrupt.c | 26 +++++++++++--
> arch/s390/kvm/vsie.c | 50 +++++++++----------------
> include/linux/kvm_host.h | 1 +
> virt/kvm/kvm_main.c | 4 +-
> 6 files changed, 67 insertions(+), 42 deletions(-)
>
prev parent reply other threads:[~2017-11-08 11:10 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
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 ` Cornelia Huck [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=20171108121053.172fa481.cohuck@redhat.com \
--to=cohuck@redhat.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).