From: Janosch Frank <frankja@linux.vnet.ibm.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, dan.carpenter@oracle.com, borntraeger@de.ibm.com
Subject: Re: [PATCH 0/5] Improve KVM per VM monitoring
Date: Thu, 12 May 2016 10:34:03 +0200 [thread overview]
Message-ID: <57343FFB.1020207@linux.vnet.ibm.com> (raw)
In-Reply-To: <1459942312-15150-1-git-send-email-frankja@linux.vnet.ibm.com>
Ping
I have rebased version ready for a resend if wanted.
next prev parent reply other threads:[~2016-05-12 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 11:31 [PATCH 0/5] Improve KVM per VM monitoring Janosch Frank
2016-04-06 11:31 ` [PATCH 1/5] tools: Add kvm_stat vm monitor script Janosch Frank
2016-05-17 12:11 ` Paolo Bonzini
2016-04-06 11:31 ` [PATCH 2/5] MAINTAINERS: Add kvm tools Janosch Frank
2016-04-06 11:31 ` [PATCH 3/5] KVM: Create debugfs dir and stat files for each VM Janosch Frank
2016-04-06 11:31 ` [PATCH 4/5] tools: kvm_stat: Introduce pid monitoring Janosch Frank
2016-04-06 11:31 ` [PATCH 5/5] tools: kvm_stat: Add documentation Janosch Frank
2016-05-12 8:34 ` Janosch Frank [this message]
2016-05-17 12:16 ` [PATCH 0/5] Improve KVM per VM monitoring Paolo Bonzini
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=57343FFB.1020207@linux.vnet.ibm.com \
--to=frankja@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=dan.carpenter@oracle.com \
--cc=kvm@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;
as well as URLs for NNTP newsgroup(s).