From: Gerd Hoffmann <kraxel@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: "Kamble, Nitin A" <nitin.a.kamble@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: thread/core siblings info for guests
Date: Mon, 06 Oct 2008 12:23:16 +0200 [thread overview]
Message-ID: <48E9E714.1030601@redhat.com> (raw)
In-Reply-To: <48E88C62.9030103@redhat.com>
Avi Kivity wrote:
>
> Not that I know of. Indeed finer control over cpuid is needed. We need
> to support at least three modes:
>
> - default: expose some machine that is likely to be widely supported
> - host: expose as much of the host cpu as we can
> - managed: management application controls everything
qemu has an array with predefined cpu types, selectable via -cpu <name>.
IMHO it would be a good idea to reuse that, especially with the
upstream merge in mind ...
cheers,
Gerd
next prev parent reply other threads:[~2008-10-06 10:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 20:35 thread/core siblings info for guests Kamble, Nitin A
2008-10-05 9:44 ` Avi Kivity
2008-10-06 10:23 ` Gerd Hoffmann [this message]
2008-10-06 18:01 ` Kamble, Nitin A
2008-10-06 20:54 ` Chris Wright
2008-10-17 22:45 ` Nitin A Kamble
2008-10-18 0:18 ` Alexander Graf
2008-10-20 16:46 ` Kamble, Nitin A
2008-10-19 9:29 ` Avi Kivity
2008-10-20 18:37 ` Nitin A Kamble
2008-10-21 8:52 ` Avi Kivity
2008-10-31 16:47 ` Nitin A Kamble
2008-11-04 14:59 ` Avi Kivity
2008-11-04 19:02 ` Nitin A Kamble
2008-11-05 6:38 ` Avi Kivity
2008-11-05 23:37 ` [Patch 1] " Nitin A Kamble
2008-11-06 13:10 ` Avi Kivity
2008-11-05 23:56 ` [patch 2] " Nitin A Kamble
2008-11-06 13:18 ` Avi Kivity
2008-11-06 0:25 ` [Patch 3] " Nitin A Kamble
2008-11-06 13:20 ` Avi Kivity
2008-11-06 18:01 ` Kamble, Nitin A
2008-11-16 13:26 ` Avi Kivity
2008-11-18 0:09 ` Nitin A Kamble
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=48E9E714.1030601@redhat.com \
--to=kraxel@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nitin.a.kamble@intel.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 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.