From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
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 16:47:53 +0200 [thread overview]
Message-ID: <4B5F0099.9060909@redhat.com> (raw)
In-Reply-To: <27124E66-3A8C-4255-B1E1-B0889D6187AC@suse.de>
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.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Chris Wright <chrisw@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 16:47:53 +0200 [thread overview]
Message-ID: <4B5F0099.9060909@redhat.com> (raw)
In-Reply-To: <27124E66-3A8C-4255-B1E1-B0889D6187AC@suse.de>
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.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-01-26 14:47 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
2010-01-26 13:11 ` [Qemu-devel] " 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 [this message]
2010-01-26 14:47 ` 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=4B5F0099.9060909@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--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.