From: Neo Jia <cyclonusj@gmail.com>
To: Asias He <asias.hejun@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>,
Sasha Levin <levinsasha928@gmail.com>,
mingo@elte.hu, prasadjoshi124@gmail.com, gorcunov@gmail.com,
kvm@vger.kernel.org
Subject: Re: [PATCH] kvm tools: Add 'kvm memstat' command
Date: Thu, 18 Aug 2011 17:46:54 -0700 [thread overview]
Message-ID: <20110819004654.GA28702@gmail.com> (raw)
In-Reply-To: <4E49F9AE.9070401@gmail.com>
On Tue, Aug 16, 2011 at 01:01:34PM +0800, Asias He wrote:
> On 08/15/2011 08:06 PM, Pekka Enberg wrote:
> > On 8/15/11 3:02 PM, Sasha Levin wrote:
> >> On Mon, 2011-08-15 at 14:56 +0300, Pekka Enberg wrote:
> >>> On 8/15/11 2:53 PM, Sasha Levin wrote:
> >>>> This patch adds 'kvm memstat' command that allows retrieving memory
> >>>> statistics out of
> >>>> a running guest using the virtio-balloon stats vq interface.
> >>>>
> >>>> Signed-off-by: Sasha Levin<levinsasha928@gmail.com>
> >>> Shouldn't we just call this "kvm stat"? We can print out all statistics
> >>> by default and
> >>> add command line options like "--mem" to display individual stats?
> >> Do we have any other statistics to print out at the moment?
> >
> > Not right now but IIRC Asias talked about networking statistics. The
> > 'kvm memstat' feels too specific to justify a separate builtin as
> > opposed to an command line option in a 'kvm stat' command.
>
> Yes. the command I am proposing is 'kvm info'. We can have a lot of
> thing in 'kvm info', like register info, network info ,disk info. mem
> info. Actually, Pekka suggested to have kvm info for all the infos and
> if we are getting too much, we can split kvm info into sub command, like
> kvm info mem, kvm info reg.
Should we already have something similar from QEMU already such as register and
memory access?
Can we use this interface to write to guest physical address?
Thanks,
CJ
>
> --
> Best Regards,
> Asias He
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-08-19 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 11:53 [PATCH] kvm tools: Add 'kvm memstat' command Sasha Levin
2011-08-15 11:56 ` Pekka Enberg
2011-08-15 12:02 ` Sasha Levin
2011-08-15 12:06 ` Pekka Enberg
2011-08-16 5:01 ` Asias He
2011-08-19 0:46 ` Neo Jia [this message]
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=20110819004654.GA28702@gmail.com \
--to=cyclonusj@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.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