qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Chris Wright <chrisw@redhat.com>, Avi Kivity <avi@redhat.com>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: KVM call agenda for Jan 26
Date: Tue, 26 Jan 2010 08:59:02 -0600	[thread overview]
Message-ID: <4B5F0336.7030204@codemonkey.ws> (raw)
In-Reply-To: <2D8DB108-5885-4156-AC83-D9E91075861B@suse.de>

On 01/26/2010 08:50 AM, Alexander Graf wrote:
> On 26.01.2010, at 15:47, Avi Kivity wrote:
>
>    
>> On 01/26/2010 04:42 PM, Alexander Graf wrote:
>>      
>>>        
>>>> That's /proc/cpuinfo, we should just extend it, maybe that's what Alex meant, but I'd like to see something more capable.
>>>>
>>>>          
>>> I think we're all looking at different use-cases.
>>>
>>> First and frontmost the one type of user I'm concerned with in this case is a mortal end-user who doesn't know that much about virtualization details and doesn't care what NPT is. He just wants to have a VM running and wants to know how well it'll work.
>>>
>>>        
>> It really depends on what he does with it.  3D gaming? might have a different experience from the always exciting kernel builds.
>>      
> Well, we can give an estimation (based on previous measurements) for certain subsystems. Like I proposed in the original mail, we can actually give users information about virtual CPU speed.
>    

The problem with making an unqualified statement about something like 
"virtual CPU speed" is that if a user runs a random benchmark, and gets 
less than XX%, they'll consider it a bug and be unhappy.

I'm very reluctant to take anything in QEMU that makes promises about 
virtualization performance.  It's a bad idea IMHO.

> With SPICE hopefully merged one day we also could give some estimates on 3D performance.
>    

Spice doesn't support 3D today.

Regards,

Anthony Liguori

> Alex

  reply	other threads:[~2010-01-26 14:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26  6:49 [Qemu-devel] KVM call agenda for Jan 26 Chris Wright
2010-01-26  9:09 ` [Qemu-devel] " Alexander Graf
2010-01-26 13:11   ` Anthony Liguori
2010-01-26 13:17     ` Avi Kivity
2010-01-26 13:18     ` Alexander Graf
2010-01-26 13:24       ` Avi Kivity
2010-01-26 13:33         ` Daniel P. Berrange
2010-01-26 13:37           ` Alexander Graf
2010-01-26 13:45           ` Avi Kivity
2010-01-26 14:13         ` Anthony Liguori
2010-01-26 14:15           ` Avi Kivity
2010-01-26 14:22             ` Anthony Liguori
2010-01-26 14:26               ` Avi Kivity
2010-01-26 14:32                 ` Anthony Liguori
2010-01-26 14:37                   ` Avi Kivity
2010-01-26 14:42                     ` Alexander Graf
2010-01-26 14:47                       ` Avi Kivity
2010-01-26 14:50                         ` Alexander Graf
2010-01-26 14:59                           ` Anthony Liguori [this message]
2010-01-26 14:42                     ` Anthony Liguori
2010-01-26 14:44                       ` 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=4B5F0336.7030204@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --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 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).