From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoffer Dall Subject: Re: [PATCH v2 1/4] KVM: device: add simple registration mechanism for kvm_device_ops Date: Thu, 31 Jul 2014 14:10:22 +0200 Message-ID: <20140731121022.GH11610@cbox> References: <1404225918-8903-1-git-send-email-will.deacon@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu, cornelia.huck@de.ibm.com, Alex.Williamson@redhat.com, agraf@suse.de, gleb@kernel.org, pbonzini@redhat.com, marc.zyngier@arm.com To: Will Deacon Return-path: Received: from mail-la0-f51.google.com ([209.85.215.51]:50807 "EHLO mail-la0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750782AbaGaMKX (ORCPT ); Thu, 31 Jul 2014 08:10:23 -0400 Received: by mail-la0-f51.google.com with SMTP id pn19so1973817lab.10 for ; Thu, 31 Jul 2014 05:10:22 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1404225918-8903-1-git-send-email-will.deacon@arm.com> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Jul 01, 2014 at 03:45:15PM +0100, Will Deacon wrote: > kvm_ioctl_create_device currently has knowledge of all the device types > and their associated ops. This is fairly inflexible when adding support > for new in-kernel device emulations, so move what we currently have out > into a table, which can support dynamic registration of ops by new > drivers for virtual hardware. > > I didn't try to port all current drivers over, as it's not always clear > which initialisation hook the ops should be registered from. > > Cc: Cornelia Huck > Cc: Alex Williamson > Cc: Alex Graf > Cc: Gleb Natapov > Cc: Paolo Bonzini > Cc: Marc Zyngier > Cc: Christoffer Dall > Signed-off-by: Will Deacon > --- > Reviewed-by: Christoffer Dall