All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Joerg Roedel <joerg.roedel-5C7GfCeVMHo@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Markus Rechberger
	<markus.rechberger-5C7GfCeVMHo@public.gmane.org>,
	Joerg Roedel <jroedel-Ug2OvFXVNAT2eFz/2MeuCQ@public.gmane.org>
Subject: Re: [PATCH] x86: emulate read/write access to cr8
Date: Thu, 06 Dec 2007 19:38:32 +0200	[thread overview]
Message-ID: <47583398.1080303@qumranet.com> (raw)
In-Reply-To: <1196952412156-git-send-email-joerg.roedel-5C7GfCeVMHo@public.gmane.org>

Joerg Roedel wrote:
> From: Joerg Roedel <jroedel-Ug2OvFXVNAT2eFz/2MeuCQ@public.gmane.org>
>
> This patch adds code to emulate the access to the cr8 register to the x86
> instruction emulator in kvm.
>
>   

I wrote a unit test for 'mov cr8', and it passes!

Seems we aren't trapping cr8 access at all for svm.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

  parent reply	other threads:[~2007-12-06 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 14:46 [PATCH] x86: emulate read/write access to cr8 Joerg Roedel
     [not found] ` <1196952412156-git-send-email-joerg.roedel-5C7GfCeVMHo@public.gmane.org>
2007-12-06 15:34   ` Avi Kivity
2007-12-06 17:38   ` Avi Kivity [this message]
     [not found]     ` <47583398.1080303-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-06 17:51       ` Avi Kivity
     [not found]         ` <475836B5.5070505-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-06 19:04           ` Joerg Roedel

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=47583398.1080303@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=joerg.roedel-5C7GfCeVMHo@public.gmane.org \
    --cc=jroedel-Ug2OvFXVNAT2eFz/2MeuCQ@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=markus.rechberger-5C7GfCeVMHo@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.