qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Glauber Costa <glommer@gmail.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH] introduce kvm64 CPU
Date: Sun, 23 Aug 2009 12:03:27 +0300	[thread overview]
Message-ID: <4A9105DF.4090504@redhat.com> (raw)
In-Reply-To: <4A8F1765.6060306@amd.com>

On 08/22/2009 12:53 AM, Andre Przywara wrote:
>>> I think this is best left to management software, which has more 
>>> information
>>> about the migration pool.
>> I believe what we want is an automatic tool that will connect to a
>> list of machines,and determine which qemu cpu type we should use.
>
> > Doesn't sound like black magic...
> I already have such a basic tool. It uses ssh (with pubkey) to connect 
> to the target machine, then uses dd on /dev/cpu/0/cpuid to get the 
> CPUID info. This requires cpuid.ko to be loaded and the permissions on 
> the device file to be sufficient (the appropriate udev patch is 
> already upstream). It then computes the least common denominator bits 
> from several machines.
> Were you thinking of that approach or do you want to include this host 
> CPUID functionality into QEMU (somehow embedded in the migration 
> handler)?

When qemu is involved it is already far too late.  This node needs to be 
classified when it is added to the cluster.

But maybe we can integrate it into 'qemu -capabilities', if and when 
that is added.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-08-23  9:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20 21:34 [Qemu-devel] [PATCH] introduce kvm64 CPU Andre Przywara
2009-08-21 13:33 ` [Qemu-devel] " Jamie Lokier
2009-08-21 14:23   ` Andre Przywara
2009-08-22  1:45     ` Jamie Lokier
2009-08-21 15:41 ` Avi Kivity
2009-08-21 16:01   ` Glauber Costa
2009-08-21 21:53     ` Andre Przywara
2009-08-23  9:03       ` Avi Kivity [this message]
2009-08-23 13:20       ` Amit Shah
2009-08-21 21:59   ` Andre Przywara
2009-08-23  9:05     ` Avi Kivity
2009-08-23 12:47       ` Jamie Lokier
2009-08-22  1:03   ` Jamie Lokier

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=4A9105DF.4090504@redhat.com \
    --to=avi@redhat.com \
    --cc=andre.przywara@amd.com \
    --cc=glommer@gmail.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).