From: Avi Kivity <avi@redhat.com>
To: nitin.a.kamble@intel.com
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kraxel@redhat.com" <kraxel@redhat.com>,
"chrisw@sous-sol.org" <chrisw@sous-sol.org>
Subject: Re: thread/core siblings info for guests
Date: Tue, 21 Oct 2008 10:52:42 +0200 [thread overview]
Message-ID: <48FD985A.6070606@redhat.com> (raw)
In-Reply-To: <1224527821.15135.4.camel@lnitindesktop.sc.intel.com>
Nitin A Kamble wrote:
> Hi Avi,
> I do find that ioctl in the kvm kernel module code. and the qemu code
> can do the ioctl to get the cpuinfo bits. But seems like nobody is using
> this ioctl yet. What was the purpose of this code?
>
>
It's for -cpu host and for implementing greatest common denominator type
of calculations. Qemu doesn't use it yet.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-10-21 8:52 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
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 [this message]
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=48FD985A.6070606@redhat.com \
--to=avi@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=kraxel@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.