From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Amit Shah <amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] KVM: is_long_mode should check for EFER_LMA
Date: Sun, 04 Nov 2007 09:17:32 +0200 [thread overview]
Message-ID: <472D720C.2080307@qumranet.com> (raw)
In-Reply-To: <200711030242.02001.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Amit Shah wrote:
> >From bfed574c93b36a19e2976ddcaae7939dd6c6fc41 Mon Sep 17 00:00:00 2001
> From: Amit Shah <amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
> Date: Sat, 3 Nov 2007 02:38:00 +0530
> Subject: [PATCH] KVM: is_long_mode should check for EFER_LMA
>
> is_long_mode currently checks the LongModeEnable bit in
> EFER instead of the LongModeActive bit. This should work
> for most cases, but for some broken implementations that
> set the LME bit before enabling PAE in CR4 to enter long
> mode.
>
> This is noticed on a solaris guest on an AMD host (but might
> not be specific to AMD).
>
>
Patch looks good and obviously correct to me. But:
- why do you say 'broken implementations'? do you mean 'broken
guests'? I think that behavior is as specified.
- what guest action triggered the failure? (e.g. mov cr4, or what?)
- please supply a patch to the testsuite that adds a regression test for
this issue.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
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-11-04 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 21:12 [PATCH] KVM: is_long_mode should check for EFER_LMA Amit Shah
[not found] ` <200711030242.02001.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-04 7:17 ` Avi Kivity [this message]
[not found] ` <472D720C.2080307-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-04 13:23 ` Amit Shah
[not found] ` <200711041853.27579.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-04 13:41 ` Avi Kivity
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=472D720C.2080307@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=amit.shah-atKUWr5tajBWk0Htik3J/w@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 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.