All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: VMX: Conditionally reload debug register 6
Date: Tue, 01 Sep 2009 15:54:59 +0300	[thread overview]
Message-ID: <4A9D19A3.1000500@redhat.com> (raw)
In-Reply-To: <4A9D144B.1020807@siemens.com>

On 09/01/2009 03:32 PM, Jan Kiszka wrote:
> I'm worried about vm-exits that may take precedence over the #db trap.
> If we skip to save/restore dr6 for them, the value that the interception
> handler sees later on will be bogus. Or is this architecturally impossible?
>    

I think it's architectually impossible.  Debug traps take effect after 
the instruction executed, so if we made it to that point, nothing else 
can cause the vmexit.

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


      reply	other threads:[~2009-09-01 12:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01 11:40 [PATCH] KVM: VMX: Conditionally reload debug register 6 Avi Kivity
2009-09-01 11:43 ` Jan Kiszka
2009-09-01 11:53   ` Avi Kivity
2009-09-01 12:32     ` Jan Kiszka
2009-09-01 12:54       ` Avi Kivity [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=4A9D19A3.1000500@redhat.com \
    --to=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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.