All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kvm: sync registers?
Date: Fri, 07 Nov 2008 10:40:39 -0600	[thread overview]
Message-ID: <49146F87.1090909@codemonkey.ws> (raw)
In-Reply-To: <200811071631.54494.paul@codesourcery.com>

Paul Brook wrote:
> On Friday 07 November 2008, Anthony Liguori wrote:
>   
>> Gerd Hoffmann wrote:
>>     
>>>   Hi,
>>>
>>> How does kvm sync registers between kernel and qemu env?
>>> I see there are kvm_arch_{get,put}_registers() functions in
>>> target-i386/kvm.c, but grep doesn't find a single call of them?
>>>       
>> Right now, it doesn't.  We should probably sync registers in the same
>> places that kvm-userspace does (gdbstubs, vmport, etc.).
>>
>> I tried to always sync registers on every exit but this causes boot to
>> fail. The same is true of kvm-userspace though and I've been meaning to
>> dig into why this is.
>>     
>
> Maybe due to do with inconsistencies between the segment register contents and 
> the descriptor tables? I know I've written code that relies on this feature.
>   

VT/SVM actually allow you to get at the descriptor tables/cache and we 
save/restore them in KVM.  I only see this issue if I always 
save/restore registers so it leads me to think it's something more subtle.

Regards,

Anthony Liguori

> Paul
>   

  reply	other threads:[~2008-11-07 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07 10:22 [Qemu-devel] kvm: sync registers? Gerd Hoffmann
2008-11-07 14:03 ` Anthony Liguori
2008-11-07 15:57   ` Gerd Hoffmann
2008-11-07 16:25     ` Gerd Hoffmann
2008-11-07 16:31   ` Paul Brook
2008-11-07 16:40     ` Anthony Liguori [this message]
2008-11-09 14:30       ` Avi Kivity
2008-11-07 17:01     ` Gerd Hoffmann

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=49146F87.1090909@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.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.