All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Xen Dev <xen-devel@lists.xensource.com>
Subject: Re: para virt cpuid?
Date: Tue, 7 Jun 2005 13:06:36 -0400	[thread overview]
Message-ID: <20050607170636.GD16344@redhat.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D2820DE@liverpoolst.ad.cl.cam.ac.uk>

On Tue, Jun 07, 2005 at 12:15:17PM +0100, Ian Pratt wrote:
 > > looking at TODO list, i see this stuff: "para virt cpuid
 > > (/proc/cpuinfo) allow hiding from domains via domain config"
 > > 
 > > I dont understand what it is. Anybody here could explain this to me? 
 > 
 > Unfortunately, its not possible to trap the cpuid instruction on
 > standard x86. Which makes it hard to 'hide' certain processor features
 > from applications and libraries (since we're hacking the kernel we can
 > get around this inside the kernel).
 > 
 > You may wish to hide certain features from user applications such that
 > you can migrate the VM to a different host without worrying whether it
 > has that feature or not (e.g. migrating from an SSE2 host to one that
 > doesn't have it).
 > 
 > Some applications decide whether they can use a CPU feature by reading
 > from /proc/cpuinfo, in which case we could hide features under the
 > control of the domain's config. Unfortunately, I fear many (most?)
 > application libraries probably just go at the cpuid instruction
 > directly.

Either that, or they parse /dev/cpu/N/cpuid, which is again, trappable by
the kernel if we so desired. Any apps that do cpuid instruction calls
itself is likely broken anyway on SMP machines, unless it also plays
games with the scheduler affinity calls.

		Dave

  reply	other threads:[~2005-06-07 17:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 11:15 para virt cpuid? Ian Pratt
2005-06-07 17:06 ` Dave Jones [this message]
2005-06-08  6:07 ` Jan Schneider
  -- strict thread matches above, loose matches on Subject: below --
2005-06-07 10:47 aq

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=20050607170636.GD16344@redhat.com \
    --to=davej@redhat.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.