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 17:16:56 +0000 [thread overview]
Message-ID: <C70CDB88.18933%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <b17e1025-3387-42f6-bbd4-88d75f697ee6@default>
On 27/10/2009 17:03, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:
> Frankly, I'm not very thrilled with the hack-y pvcpuid
> requirement anyway. It seemed a nice architected interface
> if cpuid would work, but would be too easy for a well-intentioned
> app developer to use cpuid instead of pvcpuid and make
> incorrect assumptions that would result in app breakage.
What's hacky about it? It'll probably get used in any 'solution' in some
way, e.g., to probe for wacky new userland hypercall interfaces. It's our
standard interface to probe for features and information direct from the
hypervisor.
-- Keir
next prev parent reply other threads:[~2009-10-27 17:16 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
2009-10-27 17:03 ` Dan Magenheimer
2009-10-27 17:16 ` Keir Fraser [this message]
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=C70CDB88.18933%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.