From: Joerg Roedel <joro@8bytes.org>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, avi@redhat.com, mtosatti@redhat.com,
joerg.roedel@amd.com, agraf@suse.de
Subject: Re: [PATCH] SVM: do not generate "external interrupt exit" if other exit is pending
Date: Sun, 19 Sep 2010 19:29:41 +0200 [thread overview]
Message-ID: <20100919172941.GF15338@8bytes.org> (raw)
In-Reply-To: <20100919164127.GC3008@redhat.com>
On Sun, Sep 19, 2010 at 06:41:27PM +0200, Gleb Natapov wrote:
> Nested SVM checks for external interrupt after injecting nested exception.
> In case there is external interrupt pending the code generates "external
> interrupt exit" and overwrites previous exit info. If previously injected
> exception already generated exit it will be lost.
Right. Have you seen specific mismehavior due to this problem? I am just
curious how you found this :-)
And another question, can you put the reason for this "if(...) return"
into an comment before the statement? The whole svm-emulation thing is
complicated enough so that we should document it well in the code :-)
Joerg
>
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> index 43f5558..1a1f86b 100644
> --- a/arch/x86/kvm/svm.c
> +++ b/arch/x86/kvm/svm.c
> @@ -1707,6 +1707,9 @@ static inline bool nested_svm_intr(struct vcpu_svm *svm)
> if (!(svm->vcpu.arch.hflags & HF_HIF_MASK))
> return false;
>
> + if (svm->nested.exit_required)
> + return false;
> +
> svm->vmcb->control.exit_code = SVM_EXIT_INTR;
> svm->vmcb->control.exit_info_1 = 0;
> svm->vmcb->control.exit_info_2 = 0;
> --
> Gleb.
next prev parent reply other threads:[~2010-09-19 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 16:41 [PATCH] SVM: do not generate "external interrupt exit" if other exit is pending Gleb Natapov
2010-09-19 17:29 ` Joerg Roedel [this message]
2010-09-19 17:50 ` Gleb Natapov
2010-09-19 18:19 ` Joerg Roedel
2010-09-20 7:40 ` Gleb Natapov
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=20100919172941.GF15338@8bytes.org \
--to=joro@8bytes.org \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=joerg.roedel@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox