From: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] lmsw sets lower 16 bits of cr0, not just lower 4
Date: Thu, 02 Aug 2007 09:32:23 +1000 [thread overview]
Message-ID: <1186011143.6131.130.camel@localhost.localdomain> (raw)
In-Reply-To: <46B0D4A8.7040001-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Wed, 2007-08-01 at 21:44 +0300, Avi Kivity wrote:
> Rusty Russell wrote:
> > According to my Intel manual, although lmsw only causes an exit when
> > trying to set the bottom 4 bits, it is supposed to set the bottom 16
> > bits of cr0.
> >
> >
>
> Well, _my_ Intel manual (2A) says:
>
> > Loads the source operand into the machine status word, bits 0 through
> > 15 of register CR0. The
> > source operand can be a 16-bit general-purpose register or a memory
> > location. Only the low-
> > order 4 bits of the source operand (which contains the PE, MP, EM, and
> > TS flags) are loaded
Damn, I should have kept reading.
Sorry for the noise!
Rusty.
-------------------------------------------------------------------------
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/
prev parent reply other threads:[~2007-08-01 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 0:31 [PATCH] lmsw sets lower 16 bits of cr0, not just lower 4 Rusty Russell
[not found] ` <1185928308.6131.116.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-08-01 18:44 ` Avi Kivity
[not found] ` <46B0D4A8.7040001-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-01 23:32 ` Rusty Russell [this message]
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=1186011143.6131.130.camel@localhost.localdomain \
--to=rusty-8n+1lvoiyb80n/f98k4iww@public.gmane.org \
--cc=avi-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox