All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matteo <84kvm84@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: ms_sysenter_eip zero value
Date: Thu, 27 Jan 2011 14:01:34 +0100	[thread overview]
Message-ID: <4D416CAE.9010503@gmail.com> (raw)
In-Reply-To: <4D40045A.2010806@redhat.com>

On 01/26/2011 12:24 PM, Avi Kivity wrote:
> On 01/23/2011 01:25 PM, Matteo Signorini wrote:
>> Hi,
>>
>> I'm having some problems understanding the sysenter instruction.
>> As far as I know, in order to successfully call the sysenter 
>> instruction,
>> MSR_IA32_SYSENTER_CS and MSR_IA32_SYSENTER_EIP registers have to be
>> correctly set.
>>
>> So I printed the value of such registers while the VM was running but
>> the output is 0 for both.
>>
>> now:
>>
>> 1) I'm having this problem ONLY with the Intel CPU (vmx.c source code).
>> When I run the same code on an AMD CPU (svm.c source code)
>> MSR_IA32_SYSENTER_EIP and MSR_IA32_SYSENTER_CS contain nonzero values.
>>
>> 2) I am 100% sure the guest is not executing an int80 but a sysenter
>>
>> so there is something here I can't understand...
>> please help me solving this problem.
>
> How are you printing out the values? Maybe the problem is there?
>

arguably there is something I'm doing wrong but I don't think it's the  print format.

Let me explain what I'm doing. I have modified a little bit the  "cpu_dump_state" function called by the monitor's "do_info_registers"  function in order to print  an additional element and precisely the env->sysenter_cs/eip value.

Now, as stated before I don't think the problem is the format because if  I  use the same code on an AMD machine, the value printed during the VM  execution is a  non zero value so I'm wondering why this difference from amd and intel?

Matteo



      reply	other threads:[~2011-01-27 13:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-23 11:25 ms_sysenter_eip zero value Matteo Signorini
2011-01-26 11:24 ` Avi Kivity
2011-01-27 13:01   ` Matteo [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=4D416CAE.9010503@gmail.com \
    --to=84kvm84@gmail.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.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.