kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm@vger.kernel.org, Hollis Blanchard <hollisb@us.ibm.com>,
	Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH 3/5] KVM: VMX: Ensure interruptibility when single-stepping
Date: Sun, 07 Dec 2008 12:05:06 +0200	[thread overview]
Message-ID: <493B9FD2.4080304@redhat.com> (raw)
In-Reply-To: <20081127114343.10901.62425.stgit@mchn012c.ww002.siemens.net>

Jan Kiszka wrote:
> When single-stepping, we have to ensure that the INT1 can make it
> through even if the guest itself is uninterruptible due to MOV SS or
> STI. VMENTRY will fail otherwise.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>
>  arch/x86/kvm/vmx.c |   10 ++++++++--
>  1 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index 3a422dc..8e83102 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -1010,6 +1010,7 @@ static void vmx_cache_reg(struct kvm_vcpu *vcpu, enum kvm_reg reg)
>  static int set_guest_debug(struct kvm_vcpu *vcpu, struct kvm_guest_debug *dbg)
>  {
>  	int old_debug = vcpu->guest_debug;
> +	u32 interruptibility;
>  	unsigned long flags;
>  
>  	vcpu->guest_debug = dbg->control;
> @@ -1017,9 +1018,14 @@ static int set_guest_debug(struct kvm_vcpu *vcpu, struct kvm_guest_debug *dbg)
>  		vcpu->guest_debug = 0;
>  
>  	flags = vmcs_readl(GUEST_RFLAGS);
> -	if (vcpu->guest_debug & KVM_GUESTDBG_SINGLESTEP)
> +	if (vcpu->guest_debug & KVM_GUESTDBG_SINGLESTEP) {
>  		flags |= X86_EFLAGS_TF | X86_EFLAGS_RF;
> -	else if (old_debug & KVM_GUESTDBG_SINGLESTEP)
> +		/* We must be interruptible when single-stepping */
> +		interruptibility = vmcs_read32(GUEST_INTERRUPTIBILITY_INFO);
> +		if (interruptibility & 3)
> +			vmcs_write32(GUEST_INTERRUPTIBILITY_INFO,
> +				     interruptibility & ~3);
>   

Could just write unconditionally - it's not like the write has any 
effect on speed.  vmcs_clear_bits() will do it cleanly.

But I'm worried about correctness.  Suppose we're singlestepping a sti; 
hlt sequence.  While we'll clear interruptibility, probably receive the 
debug trap (since that's a high priority exception), but then inject the 
interrupt before the hlt, hanging the guest.  So we probably need to 
restore interruptibility on exit.

This looks like a good candidate for a test case.

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


  reply	other threads:[~2008-12-07 10:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 11:43 [PATCH 0/5] KVM: Improved guest debugging / debug register emulation Jan Kiszka
2008-11-27 11:43 ` [PATCH 5/5] KVM: x86: Wire-up hardware breakpoints for guest debugging Jan Kiszka
2008-11-27 11:43 ` [PATCH 3/5] KVM: VMX: Ensure interruptibility when single-stepping Jan Kiszka
2008-12-07 10:05   ` Avi Kivity [this message]
2008-12-08  9:17     ` Jan Kiszka
2008-12-11 19:15     ` [PATCH] KVM: VMX: Allow single-stepping when interruptible Jan Kiszka
2008-11-27 11:43 ` [PATCH 4/5] KVM: x86: Virtualize debug registers Jan Kiszka
2008-11-27 11:43 ` [PATCH 2/5] KVM: New guest debug interface Jan Kiszka
2008-12-07  9:55   ` Avi Kivity
2008-12-08  9:13     ` Jan Kiszka
2008-12-08  9:34       ` Avi Kivity
2008-12-08  9:42         ` Jan Kiszka
2008-12-08 13:47         ` Jan Kiszka
2008-12-08 14:57           ` Avi Kivity
2008-12-08 15:17             ` Jan Kiszka
2008-12-10  8:48               ` Avi Kivity
2008-11-27 11:43 ` [PATCH 1/5] VMX: Support for injecting software exceptions Jan Kiszka
  -- strict thread matches above, loose matches on Subject: below --
2008-10-06  9:15 [PATCH 0/5] KVM: Fix and improve guest debugging and x86 debug registers Jan Kiszka
2008-10-06  9:15 ` [PATCH 3/5] KVM: VMX: Ensure interruptibility when single-stepping Jan Kiszka

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=493B9FD2.4080304@redhat.com \
    --to=avi@redhat.com \
    --cc=hollisb@us.ibm.com \
    --cc=jan.kiszka@siemens.com \
    --cc=joerg.roedel@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).