From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call agenda for Jan 26
Date: Tue, 26 Jan 2010 07:11:11 -0600 [thread overview]
Message-ID: <4B5EE9EF.6030904@codemonkey.ws> (raw)
In-Reply-To: <03EA8701-C607-4B87-A6C6-1DCD3E5DCAAC@suse.de>
On 01/26/2010 03:09 AM, Alexander Graf wrote:
> On 26.01.2010, at 07:49, Chris Wright wrote:
>
>
>> Please send in any agenda items you are interested in covering.
>>
> KVM Hardware Inquiry Tool
>
Avi beat you to it ;-) See vmxcap in the tree.
> One of the things I have on my todo list is a tool you can run on your machine that tells you which virtualization features it supports. Imaginary output of such a tool:
>
> --
>
> KVM Supported: yes
> NPT/EPT: yes
> Device Assignment: no
>
> Expected Virtual CPU Speed: 95%
>
I would suggest exercising caution in making such a broad performance
statement. It's never going to be that simple.
Regards,
Anthony Liguori
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call agenda for Jan 26
Date: Tue, 26 Jan 2010 07:11:11 -0600 [thread overview]
Message-ID: <4B5EE9EF.6030904@codemonkey.ws> (raw)
In-Reply-To: <03EA8701-C607-4B87-A6C6-1DCD3E5DCAAC@suse.de>
On 01/26/2010 03:09 AM, Alexander Graf wrote:
> On 26.01.2010, at 07:49, Chris Wright wrote:
>
>
>> Please send in any agenda items you are interested in covering.
>>
> KVM Hardware Inquiry Tool
>
Avi beat you to it ;-) See vmxcap in the tree.
> One of the things I have on my todo list is a tool you can run on your machine that tells you which virtualization features it supports. Imaginary output of such a tool:
>
> --
>
> KVM Supported: yes
> NPT/EPT: yes
> Device Assignment: no
>
> Expected Virtual CPU Speed: 95%
>
I would suggest exercising caution in making such a broad performance
statement. It's never going to be that simple.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-01-26 13:11 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 6:49 KVM call agenda for Jan 26 Chris Wright
2010-01-26 6:49 ` [Qemu-devel] " Chris Wright
2010-01-26 9:09 ` Alexander Graf
2010-01-26 9:09 ` [Qemu-devel] " Alexander Graf
2010-01-26 13:11 ` Anthony Liguori [this message]
2010-01-26 13:11 ` Anthony Liguori
2010-01-26 13:17 ` Avi Kivity
2010-01-26 13:17 ` [Qemu-devel] " Avi Kivity
2010-01-26 13:18 ` Alexander Graf
2010-01-26 13:18 ` [Qemu-devel] " Alexander Graf
2010-01-26 13:24 ` Avi Kivity
2010-01-26 13:24 ` [Qemu-devel] " Avi Kivity
2010-01-26 13:33 ` Daniel P. Berrange
2010-01-26 13:33 ` [Qemu-devel] " Daniel P. Berrange
2010-01-26 13:37 ` Alexander Graf
2010-01-26 13:37 ` [Qemu-devel] " Alexander Graf
2010-01-26 13:45 ` Avi Kivity
2010-01-26 13:45 ` [Qemu-devel] " Avi Kivity
2010-01-26 14:13 ` Anthony Liguori
2010-01-26 14:13 ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:15 ` Avi Kivity
2010-01-26 14:15 ` [Qemu-devel] " Avi Kivity
2010-01-26 14:22 ` Anthony Liguori
2010-01-26 14:22 ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:26 ` Avi Kivity
2010-01-26 14:26 ` [Qemu-devel] " Avi Kivity
2010-01-26 14:32 ` Anthony Liguori
2010-01-26 14:32 ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:37 ` Avi Kivity
2010-01-26 14:37 ` [Qemu-devel] " Avi Kivity
2010-01-26 14:42 ` Alexander Graf
2010-01-26 14:42 ` [Qemu-devel] " Alexander Graf
2010-01-26 14:47 ` Avi Kivity
2010-01-26 14:47 ` [Qemu-devel] " Avi Kivity
2010-01-26 14:50 ` Alexander Graf
2010-01-26 14:50 ` [Qemu-devel] " Alexander Graf
2010-01-26 14:59 ` Anthony Liguori
2010-01-26 14:59 ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:42 ` Anthony Liguori
2010-01-26 14:42 ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:44 ` Avi Kivity
2010-01-26 14:44 ` [Qemu-devel] " Avi Kivity
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=4B5EE9EF.6030904@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.