From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] pvcpuid: mask TSC invariant bit for various circumstances
Date: Tue, 27 Oct 2009 07:31:36 +0000 [thread overview]
Message-ID: <C70C5258.18728%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <e6b6bdb6-aa0d-4bb6-8f0e-6dfb5bc8290a@default>
On 27/10/2009 01:09, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:
>> This only affects PV domUs. I suggest patching pv_cpuid() to
>> catch dom0, and
>> then really all domUs should be handled by
>> xc_cpuid_apply_policy(), which
>> pushes CPUID info down to the hypervisor, as called from xend's
>> image.py:setCpuid(). The advantage of this is that the
>> hypervisor does not
>> need to be informed of the 'disable_migrate' flag at all -- it can be
>> assumed to be true for dom0 -- and it can be handled entirely
>> in the tools.
>> Hence I can get rid of the new domctl, which is nice.
>
> I'm not done using the disable_migrate flag yet though.
> This was just low-hanging fruit.
Okay. Well I nack this new patch anyway.
-- Keir
next prev parent reply other threads:[~2009-10-27 7:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 23:12 [PATCH] pvcpuid: mask TSC invariant bit for various circumstances Dan Magenheimer
2009-10-27 0:22 ` Keir Fraser
2009-10-27 1:09 ` Dan Magenheimer
2009-10-27 7:31 ` Keir Fraser [this message]
2009-10-27 17:03 ` Dan Magenheimer
2009-10-27 17:16 ` Keir Fraser
2009-10-27 20:40 ` Dan Magenheimer
2009-10-27 20:58 ` Keir Fraser
2009-10-27 22:03 ` Dan Magenheimer
2009-10-28 7:16 ` Keir Fraser
2009-10-28 16:27 ` Dan Magenheimer
2009-10-28 16:38 ` Jan Beulich
2009-10-28 16:50 ` Dan Magenheimer
2009-10-28 17:29 ` Keir Fraser
2009-10-29 22:07 ` Jeremy Fitzhardinge
2009-10-29 22:17 ` Dan Magenheimer
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=C70C5258.18728%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=xen-devel@lists.xensource.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.