All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	KVM <kvm@vger.kernel.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Alexander Graf <agraf@suse.de>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Jens Freimann <jfrei@linux.vnet.ibm.com>,
	linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [GIT PULLv2] KVM: s390: Features and fixes for 4.1 (kvm/next)
Date: Thu, 02 Apr 2015 20:55:19 +0200	[thread overview]
Message-ID: <551D9097.604@redhat.com> (raw)
In-Reply-To: <1427830595-12641-1-git-send-email-borntraeger@de.ibm.com>



On 31/03/2015 21:36, Christian Borntraeger wrote:
> Paolo, Marcelo,
> 
> here is the updated pull request for s390 (tag was updated)
> 
> The changes reflect the comments from Heiko Carstens and Paolo Bonzini,
> (diff as followup mail)
> 
> The following changes since commit 18280d8b4bcd4a2b174ee3cd748166c6190acacb:
> 
>   KVM: s390: represent SIMD cap in kvm facility (2015-03-17 16:33:14 +0100)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git  tags/kvm-s390-next-20150331
> 
> for you to fetch changes up to 816c7667ea97c61884e014cfeedaede5b67b0e58:
> 
>   KVM: s390: migrate vcpu interrupt state (2015-03-31 21:07:31 +0200)
> 
> ----------------------------------------------------------------
> Features and fixes for 4.1 (kvm/next)
> 
> 1. Assorted changes
> 1.1 allow more feature bits for the guest
> 1.2 Store breaking event address on program interrupts
> 
> 2. Interrupt handling rework
> 2.1 Fix copy_to_user while holding a spinlock (cc stable)
> 2.2 Rework floating interrupts to follow the priorities
> 2.3 Allow to inject all local interrupts via new ioctl
> 2.4 allow to get/set the full local irq state, e.g. for migration
>     and introspection
> 
> ----------------------------------------------------------------
> Christian Borntraeger (1):
>       KVM: s390: enable more features that need no hypervisor changes
> 
> David Hildenbrand (2):
>       KVM: s390: store the breaking-event address on pgm interrupts
>       KVM: s390: cpu timer irq priority
> 
> Jens Freimann (5):
>       KVM: s390: fix get_all_floating_irqs
>       KVM: s390: deliver floating interrupts in order of priority
>       KVM: s390: add ioctl to inject local interrupts
>       KVM: s390: refactor vcpu injection function
>       KVM: s390: migrate vcpu interrupt state
> 
>  Documentation/virtual/kvm/api.txt               |  117 +++
>  Documentation/virtual/kvm/devices/s390_flic.txt |    3 +
>  arch/s390/include/asm/kvm_host.h                |   30 +-
>  arch/s390/kvm/interrupt.c                       | 1073 ++++++++++++++---------
>  arch/s390/kvm/kvm-s390.c                        |   54 +-
>  arch/s390/kvm/kvm-s390.h                        |    6 +-
>  arch/s390/kvm/priv.c                            |    9 +-
>  include/uapi/linux/kvm.h                        |   14 +
>  virt/kvm/kvm_main.c                             |    2 +-
>  9 files changed, 906 insertions(+), 402 deletions(-)
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Pulled, thanks.

Paolo

      parent reply	other threads:[~2015-04-02 18:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 19:36 [GIT PULLv2] KVM: s390: Features and fixes for 4.1 (kvm/next) Christian Borntraeger
2015-03-31 19:36 ` [PULL diff] diff to previous pull request Christian Borntraeger
2015-04-02 18:55 ` Paolo Bonzini [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=551D9097.604@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mtosatti@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.