Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753340AbdGJJlA (ORCPT ); Mon, 10 Jul 2017 05:41:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56226 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751674AbdGJJk6 (ORCPT ); Mon, 10 Jul 2017 05:40:58 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 18B1FC0587F0 Authentication-Results: ext-mx08.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx08.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=david@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 18B1FC0587F0 Subject: Re: [PATCH v3 1/1] KVM: trigger uevents when starting or stopping a VM To: Claudio Imbrenda , kvm@vger.kernel.org Cc: borntraeger@de.ibm.com, pbonzini@redhat.com, linux-kernel@vger.kernel.org References: <1499678444-21879-1-git-send-email-imbrenda@linux.vnet.ibm.com> <1499678444-21879-2-git-send-email-imbrenda@linux.vnet.ibm.com> From: David Hildenbrand Organization: Red Hat GmbH Message-ID: <852e01e7-81f4-7fcb-dc55-80f4aed029c0@redhat.com> Date: Mon, 10 Jul 2017 11:40:55 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: <1499678444-21879-2-git-send-email-imbrenda@linux.vnet.ibm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Mon, 10 Jul 2017 09:40:58 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3726 Lines: 117 On 10.07.2017 11:20, Claudio Imbrenda wrote: Minor minor nit: The subject should state "creating or destroying a VM" > This patch adds a few lines to the KVM common code to fire a > KOBJ_CHANGE uevent whenever a KVM VM is created or destroyed. The event > carries five environment variables: > > CREATED indicates how many times a new VM has been created. It is > useful for example to trigger specific actions when the first > VM is started > COUNT indicates how many VMs are currently active. This can be used for > logging or monitoring purposes > PID has the pid of the KVM process that has been started or stopped. > This can be used to perform process-specific tuning. > STATS_PATH contains the path in debugfs to the directory with all the > runtime statistics for this VM. This is useful for performance > monitoring and profiling. > EVENT described the type of event, its value can be either "create" or > "destroy" > > Specific udev rules can be then set up in userspace to deal with the > creation or destruction of VMs as needed. > > Signed-off-by: Claudio Imbrenda > --- > virt/kvm/kvm_main.c | 59 +++++++++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 59 insertions(+) > > diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c > index f0fe9d0..7c39783 100644 > --- a/virt/kvm/kvm_main.c > +++ b/virt/kvm/kvm_main.c > @@ -130,6 +130,12 @@ EXPORT_SYMBOL_GPL(kvm_rebooting); > > static bool largepages_enabled = true; > > +#define KVM_EVENT_CREATE_VM 0 > +#define KVM_EVENT_DESTROY_VM 1 > +static void kvm_uevent_notify_change(unsigned int type, struct kvm *kvm); > +static unsigned long long kvm_createvm_count; > +static unsigned long long kvm_active_vms; > + > bool kvm_is_reserved_pfn(kvm_pfn_t pfn) > { > if (pfn_valid(pfn)) > @@ -728,6 +734,7 @@ static void kvm_destroy_vm(struct kvm *kvm) > int i; > struct mm_struct *mm = kvm->mm; > > + kvm_uevent_notify_change(KVM_EVENT_DESTROY_VM, kvm); > kvm_destroy_vm_debugfs(kvm); > kvm_arch_sync_events(kvm); > spin_lock(&kvm_lock); > @@ -3196,6 +3203,7 @@ static int kvm_dev_ioctl_create_vm(unsigned long type) > fput(file); > return -ENOMEM; > } > + kvm_uevent_notify_change(KVM_EVENT_CREATE_VM, kvm); > > fd_install(r, file); > return r; > @@ -3848,6 +3856,57 @@ static const struct file_operations *stat_fops[] = { > [KVM_STAT_VM] = &vm_stat_fops, > }; > > +static void kvm_uevent_notify_change(unsigned int type, struct kvm *kvm) > +{ > + char cbuf[32], abuf[32], pidbuf[32], evbuf[16]; do we really need that much space for a pid? > + const char pathvar[11] = "STATS_PATH="; > + char *ptr[6] = {cbuf, abuf, pidbuf, NULL, NULL, NULL}; > + char *tmp, *pathbuf; > + unsigned long long created, active; > + int idx = 3; > + > + if (!kvm_dev.this_device || !kvm || !kvm->debugfs_dentry) > + return; > + > + spin_lock(&kvm_lock); > + if (type == KVM_EVENT_CREATE_VM) { > + kvm_createvm_count++; > + kvm_active_vms++; > + } else if (type == KVM_EVENT_DESTROY_VM) { > + kvm_active_vms--; > + } > + created = kvm_createvm_count; > + active = kvm_active_vms; > + spin_unlock(&kvm_lock); > + > + pathbuf = kmalloc(PATH_MAX, GFP_KERNEL); > + if (pathbuf) { > + tmp = dentry_path_raw(kvm->debugfs_dentry, > + pathbuf + sizeof(pathvar), > + PATH_MAX - sizeof(pathvar)); > + if (!IS_ERR(tmp)) { > + memcpy(tmp - sizeof(pathvar), pathvar, sizeof(pathvar)); > + ptr[idx++] = tmp - sizeof(pathvar); > + } > + } > + snprintf(cbuf, sizeof(cbuf), "CREATED=%llu", created); Did you think about using struct kobj_uevent_env / add_uevent_var()? But most probably the problem here is special handling for dentry_path_raw(). -- Thanks, David