Re: [PATCH] vfio: Split virqfd into a separate module for vfio bus drivers

DULE_AUTHOR("Alex Williamson "); > MODULE_DESCRIPTION("IRQFD support for VFIO bus drivers"); > > ;) I don't do smileys. Perhaps that's why I never know what to think when someone uses them. Anyhow, sure, my comment is extremely trivial, but I do think I shoul

Re: [PATCH] vfio: Split virqfd into a separate module for vfio bus drivers

ivers" > +MODULE_VERSION(DRIVER_VERSION); > +MODULE_LICENSE("GPL v2"); > +MODULE_AUTHOR(DRIVER_AUTHOR); > +MODULE_DESCRIPTION(DRIVER_DESC); Why bother with those three defines? They're all used just once, aren't they? Paul Bolle -- To unsubscribe from

Re: [PATCH v3 0/2] x86/arm64: add xenconfig

On Tue, 2015-02-10 at 14:21 -0800, David Rientjes wrote: > We need an update to the MAINTAINERS file if "Yann E. MORIN" > isn't the active Kconfig maintainer anymore. Yes, we do. Michal, what update would you suggest? Thanks, Paul Bolle -- To unsubscribe from thi

Re: [PATCH v3 0/2] x86/arm64: add xenconfig

nfig > >> > > >> > Who could these changes go through? > >> > >> I would be OK with taking it in the Xen tree, but I would feel more > >> comfortable doing that if you had an ack from Yann Morin (CC'ed). > > > > *Poke* > > Hey Yann, wondering if you had any feedback. Thanks. Yann has disappeared a year ago. Michal now, informally, keeps an eye on kconfig related patches. Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: KVM: HAVE_KVM_ARCH_DIRTY_LOG_PROTECT?

On Thu, 2015-01-22 at 14:57 +0100, Paolo Bonzini wrote: > On 22/01/2015 10:19, Paul Bolle wrote: > > Your commit ba0513b5b8ff ("KVM: Add generic support for dirty page > > logging") is included in today's linux-next (ie, next-20150122). I > > noticed becaus

KVM: CONFIG_LOCK_DEP and CONFIG_LOCK_DETECTOR?

IG_LOCK_DEP and CONFIG_LOCK_DETECTOR. It seems CONFIG_LOCKDEP and CONFIG_LOCKUP_DETECTOR should be used instead. Is a trivial patch to fix these typos queued somewhere? Thanks, Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to major

KVM: HAVE_KVM_ARCH_DIRTY_LOG_PROTECT?

OG_PROTECT. But nothing in linux-next uses that symbol. Why was it added? Thanks, Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH v4 03/25] virtio-pci: move freeze/restore to virtio core

tification (used to match it with a driver). > * @config: the configuration ops for this device. Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[PATCH] [next-20140923] KVM: Remove KVM_VFIO

There are no checks for CONFIG_KVM_VFIO and nothing depends on KVM_VFIO. Setting KVM_VFIO has no effect. Remove that Kconfig symbol. Signed-off-by: Paul Bolle --- I choose not to mention commit 80ce1639727e ("KVM: VFIO: register kvm_device_ops dynamically") as references to linux-ne

KVM: remove Kconfig symbol KVM_VFIO?

ree queued somewhere? If not, should I submit a trivial patch that does that? Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[PATCH] kvm: vfio: silence GCC warning

oid __user *argp = (void __user *)arg; ^ Silence this warning by casting arg to unsigned long. argp's current type, "void __user *", is always casted to "int32_t __user *". So its type might as well be changed to "int32_t __user *". Sig