All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	"cornelia.huck@de.ibm.com" <cornelia.huck@de.ibm.com>,
	"Alex.Williamson@redhat.com" <Alex.Williamson@redhat.com>,
	"agraf@suse.de" <agraf@suse.de>,
	"gleb@kernel.org" <gleb@kernel.org>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	Marc Zyngier <Marc.Zyngier@arm.com>
Subject: Re: [PATCH v2 2/4] KVM: ARM: vgic: register kvm_device_ops dynamically
Date: Thu, 31 Jul 2014 14:25:12 +0100	[thread overview]
Message-ID: <20140731132511.GV26853@arm.com> (raw)
In-Reply-To: <20140731121015.GG11610@cbox>

Hi Christoffer,

On Thu, Jul 31, 2014 at 01:10:15PM +0100, Christoffer Dall wrote:
> On Tue, Jul 01, 2014 at 03:45:16PM +0100, Will Deacon wrote:
> > Now that we have a dynamic means to register kvm_device_ops, use that
> > for the ARM VGIC, instead of relying on the static table.
> > 
> > Cc: Gleb Natapov <gleb@kernel.org>
> > Cc: Paolo Bonzini <pbonzini@redhat.com>
> > Cc: Marc Zyngier <marc.zyngier@arm.com>
> > Cc: Christoffer Dall <christoffer.dall@linaro.org>
> > Signed-off-by: Will Deacon <will.deacon@arm.com>
> > ---
> >  include/linux/kvm_host.h |   1 -
> >  virt/kvm/arm/vgic.c      | 156 +++++++++++++++++++++++------------------------
> >  virt/kvm/kvm_main.c      |   4 --
> >  3 files changed, 78 insertions(+), 83 deletions(-)

[...]

> > +	if (ret) {
> > +		kvm_err("Cannot register vgic CPU notifier\n");
> > +		goto out_free_irq;
> > +	}
> > +
> > +	on_each_cpu(vgic_init_maintenance_interrupt, NULL, 1);
> > +
> > +	/* Callback into for arch code for setup */
> > +	vgic_arch_setup(vgic);
> 
> close to ridiculous nit: but I would add a newline here since the
> comment doesn't really apply to the kvm_register_device_ops, but please
> don't make another revision just for this.

I'll repost this after the merge window anyway, so there's plenty of room
for pedantic, cosmetic changes!

Thanks,

Will

  reply	other threads:[~2014-07-31 13:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 14:45 [PATCH v2 1/4] KVM: device: add simple registration mechanism for kvm_device_ops Will Deacon
2014-07-01 14:45 ` [PATCH v2 2/4] KVM: ARM: vgic: register kvm_device_ops dynamically Will Deacon
2014-07-09 16:05   ` Paolo Bonzini
2014-07-09 16:13     ` Marc Zyngier
2014-07-31 12:10   ` Christoffer Dall
2014-07-31 13:25     ` Will Deacon [this message]
2014-07-01 14:45 ` [PATCH v2 3/4] KVM: s390: register flic ops dynamically Will Deacon
2014-07-01 14:45 ` [PATCH v2 4/4] KVM: VFIO: register kvm_device_ops dynamically Will Deacon
2014-07-09 16:06   ` Paolo Bonzini
2014-07-09 16:19   ` Alex Williamson
2014-07-09 16:47     ` Will Deacon
2014-07-09 16:56       ` Alex Williamson
2014-07-09 16:56   ` Alex Williamson
2014-07-02  9:17 ` [PATCH v2 1/4] KVM: device: add simple registration mechanism for kvm_device_ops Cornelia Huck
2014-07-02  9:32   ` Will Deacon
2014-07-02 10:18     ` Cornelia Huck
2014-07-31 12:10 ` Christoffer Dall

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=20140731132511.GV26853@arm.com \
    --to=will.deacon@arm.com \
    --cc=Alex.Williamson@redhat.com \
    --cc=Marc.Zyngier@arm.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=pbonzini@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.