From: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
To: kvm@vger.kernel.org
Cc: borntraeger@de.ibm.com, pbonzini@redhat.com,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/1]
Date: Mon, 10 Jul 2017 11:20:43 +0200 [thread overview]
Message-ID: <1499678444-21879-1-git-send-email-imbrenda@linux.vnet.ibm.com> (raw)
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.
v2 -> v3:
* added EVENT
* shortened the names of the other variables
v1 -> v2:
* added KVM_VM_PID and KVM_VM_STATS_PATH
* some cleanup, the patch should look nicer now
* rebased on 4.12
*** BLURB HERE ***
Claudio Imbrenda (1):
KVM: trigger uevents when starting or stopping a VM
virt/kvm/kvm_main.c | 59 +++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 59 insertions(+)
--
2.7.4
next reply other threads:[~2017-07-10 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 9:20 Claudio Imbrenda [this message]
2017-07-10 9:20 ` [PATCH v3 1/1] KVM: trigger uevents when starting or stopping a VM Claudio Imbrenda
2017-07-10 9:40 ` David Hildenbrand
2017-07-10 11:53 ` Claudio Imbrenda
2017-07-10 11:54 ` Paolo Bonzini
2026-01-05 4:58 [[PATCH v2] 1/1] kprobes: retry pending optprobe after freeing blocker Masami Hiramatsu
2026-01-15 2:38 ` [PATCH v3 0/1] hongao
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=1499678444-21879-1-git-send-email-imbrenda@linux.vnet.ibm.com \
--to=imbrenda@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®