public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
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: Mon, 20 Sep 2010 09:40:07 +0200	[thread overview]
Message-ID: <20100920074002.GF3008@redhat.com> (raw)
In-Reply-To: <20100919181933.GG15338@8bytes.org>

On Sun, Sep 19, 2010 at 08:19:33PM +0200, Joerg Roedel wrote:
> On Sun, Sep 19, 2010 at 07:50:27PM +0200, Gleb Natapov wrote:
> > On Sun, Sep 19, 2010 at 07:29:41PM +0200, Joerg Roedel wrote:
> > > 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 :-)
> > Yes. Trying to make async page fault work with nested svm :) It was hard
> > to fix with reproducible test case. I am not dreaming to fix it just by
> > code review.
> 
> Interesting. Hope this was the only problem and you have it working now?
> 
Yes. Now my test case works.

--
			Gleb.

      reply	other threads:[~2010-09-20  7:40 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
2010-09-19 17:50   ` Gleb Natapov
2010-09-19 18:19     ` Joerg Roedel
2010-09-20  7:40       ` Gleb Natapov [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=20100920074002.GF3008@redhat.com \
    --to=gleb@redhat.com \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=joerg.roedel@amd.com \
    --cc=joro@8bytes.org \
    --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