All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Will Deacon <will.deacon@arm.com>,
	kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu
Cc: cornelia.huck@de.ibm.com, Alex.Williamson@redhat.com,
	agraf@suse.de, gleb@kernel.org, marc.zyngier@arm.com,
	christoffer.dall@linaro.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH v3 0/4] Make kvm_device_ops registration dynamic
Date: Tue, 16 Sep 2014 12:33:27 +0200	[thread overview]
Message-ID: <541811F7.7050602@redhat.com> (raw)
In-Reply-To: <1409650056-27065-1-git-send-email-will.deacon@arm.com>

Il 02/09/2014 11:27, Will Deacon ha scritto:
> The mpic, flic and xics are still not ported over, as I don't want to
> risk breaking those devices

Actually FLIC is ported. :)

> 
>  arch/s390/kvm/kvm-s390.c |   3 +-
>  arch/s390/kvm/kvm-s390.h |   1 +
>  include/linux/kvm_host.h |   4 +-
>  include/uapi/linux/kvm.h |  22 +++++--
>  virt/kvm/arm/vgic.c      | 157 ++++++++++++++++++++++++-----------------------
>  virt/kvm/kvm_main.c      |  57 +++++++++--------
>  virt/kvm/vfio.c          |  22 ++++---
>  7 files changed, 142 insertions(+), 124 deletions(-)
> 

Thanks, applying to kvm/queue.  Alex (Graf) and Paul, can you look at
MPIC and XICS?

Paolo

      parent reply	other threads:[~2014-09-16 10:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02  9:27 [PATCH v3 0/4] Make kvm_device_ops registration dynamic Will Deacon
2014-09-02  9:27 ` [PATCH v3 1/4] KVM: device: add simple registration mechanism for kvm_device_ops Will Deacon
2014-09-02  9:27 ` [PATCH v3 2/4] KVM: ARM: vgic: register kvm_device_ops dynamically Will Deacon
2014-09-02  9:27 ` [PATCH v3 3/4] KVM: s390: register flic ops dynamically Will Deacon
2014-09-02  9:27 ` [PATCH v3 4/4] KVM: VFIO: register kvm_device_ops dynamically Will Deacon
2014-09-11 17:12 ` [PATCH v3 0/4] Make kvm_device_ops registration dynamic Will Deacon
2014-09-16 10:33 ` 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=541811F7.7050602@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=Alex.Williamson@redhat.com \
    --cc=agraf@suse.de \
    --cc=christoffer.dall@linaro.org \
    --cc=cornelia.huck@de.ibm.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=marc.zyngier@arm.com \
    --cc=paulus@samba.org \
    --cc=will.deacon@arm.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.