From: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
To: Gregory Haskins <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [kvm-commits] KVM: VMX: Use shadow TPR/cr8 for 64-bits guests
Date: Thu, 23 Aug 2007 14:51:10 +0200 [thread overview]
Message-ID: <20070823125110.GS2642@bingen.suse.de> (raw)
In-Reply-To: <1187867427.4111.45.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
> I remember when I added something similar to the lapic series that both
> of my C2D systems (Merom + Woodcrest) reported that they didn't support
> the feature in the HW. Since those were fairly new, which ones *do*
> support this (out of curiosity), or is there a microcode update floating
> around out there ;).
It's only supported in Penryn (upcomming 45nm Core2 shrink) AFAIK
Intel made a press release about this recently.
-Andi
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-23 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070823074616.8D45A250D36@il.qumranet.com>
[not found] ` <20070823074616.8D45A250D36-LjA0eNSCdXrQnzwC+xcbyw@public.gmane.org>
2007-08-23 11:10 ` [kvm-commits] KVM: VMX: Use shadow TPR/cr8 for 64-bits guests Gregory Haskins
[not found] ` <1187867427.4111.45.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-08-23 12:51 ` Andi Kleen [this message]
[not found] ` <20070823125110.GS2642-KvMlXPVkKihbpigZmTR7Iw@public.gmane.org>
2007-08-24 13:16 ` [kvm-commits] KVM: VMX: Use shadow TPR/cr8 for64-bits guests Dong, Eddie
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=20070823125110.GS2642@bingen.suse.de \
--to=ak-l3a5bk7wagm@public.gmane.org \
--cc=ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox