qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	qemu-devel@nongnu.org
Cc: gleb@kernel.org, pbonzini@redhat.com, agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH v3 0/4] KVM: irqfds for s390
Date: Mon, 24 Mar 2014 09:46:25 +0100	[thread overview]
Message-ID: <532FF0E1.5000502@de.ibm.com> (raw)
In-Reply-To: <1395406341-14698-1-git-send-email-cornelia.huck@de.ibm.com>

On 21/03/14 13:52, Cornelia Huck wrote:
> Hi,
> 
> here's the next iteration of my patchset introducing irqfds for s390.
> 
> Changes from v2:
> - rebased against current kvm/queue
> - kvm common code lock fix is already in queue
> - move some changes that belonged in patch 2 from patch 3
> - add a limit for mapped pages to patch 2
> - collected some acks
> 
> Changes from v1:
> - rebased against current kvm/queue, bumping capability numbers
> - guest adapter interrupt support is already in the kvm tree
> 
> Again, find it on
> 

> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git kvms390-irqfd

Looks all good. 

Paolo,

I guess this will miss the next merge window,  but can you pull for kvm/queue
if you have no further comments?

Christian
> 
> Cornelia Huck (4):
>   KVM: Add per-vm capability enablement.
>   KVM: s390: adapter interrupt sources
>   KVM: s390: irq routing for adapter interrupts.
>   KVM: Bump KVM_MAX_IRQ_ROUTES for s390
> 
>  Documentation/virtual/kvm/api.txt               |   27 ++-
>  Documentation/virtual/kvm/devices/s390_flic.txt |   45 ++++
>  arch/s390/include/asm/kvm_host.h                |   32 +++
>  arch/s390/include/uapi/asm/kvm.h                |   22 ++
>  arch/s390/kvm/Kconfig                           |    2 +
>  arch/s390/kvm/Makefile                          |    2 +-
>  arch/s390/kvm/interrupt.c                       |  294 ++++++++++++++++++++++-
>  arch/s390/kvm/irq.h                             |   22 ++
>  arch/s390/kvm/kvm-s390.c                        |   42 ++++
>  arch/s390/kvm/kvm-s390.h                        |    2 +
>  include/linux/kvm_host.h                        |   13 +
>  include/uapi/linux/kvm.h                        |   16 ++
>  12 files changed, 511 insertions(+), 8 deletions(-)
>  create mode 100644 arch/s390/kvm/irq.h
> 

  parent reply	other threads:[~2014-03-24  8:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 12:52 [Qemu-devel] [PATCH v3 0/4] KVM: irqfds for s390 Cornelia Huck
2014-03-21 12:52 ` [Qemu-devel] [PATCH v3 1/4] KVM: Add per-vm capability enablement Cornelia Huck
2014-03-21 12:52 ` [Qemu-devel] [PATCH v3 2/4] KVM: s390: adapter interrupt sources Cornelia Huck
2014-03-21 12:52 ` [Qemu-devel] [PATCH v3 3/4] KVM: s390: irq routing for adapter interrupts Cornelia Huck
2014-03-21 12:52 ` [Qemu-devel] [PATCH v3 4/4] KVM: Bump KVM_MAX_IRQ_ROUTES for s390 Cornelia Huck
2014-03-24  8:46 ` Christian Borntraeger [this message]
2014-03-24 10:40   ` [Qemu-devel] [PATCH v3 0/4] KVM: irqfds " Paolo Bonzini

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=532FF0E1.5000502@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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).