From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [PATCHv2] KVM: prevent spurious exit to userspace during task switch emulation.
Date: Thu, 15 Apr 2010 13:10:23 +0300 [thread overview]
Message-ID: <4BC6E60F.5080306@redhat.com> (raw)
In-Reply-To: <20100415100905.GA4550@redhat.com>
On 04/15/2010 01:09 PM, Gleb Natapov wrote:
>
> If kvm_task_switch() fails code exits to userspace without specifying
> exit reason, so the previous exit reason is reused by userspace. Fix
> this by specifying exit reason correctly.
>
> ---
> Changelog:
> v1->v2:
> - report emulation error to userspace instead of ignoring it silently.
>
>
Yeah, better than logging to dmesg.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-04-15 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 10:09 [PATCHv2] KVM: prevent spurious exit to userspace during task switch emulation Gleb Natapov
2010-04-15 10:10 ` Avi Kivity [this message]
2010-04-15 17:20 ` Marcelo Tosatti
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=4BC6E60F.5080306@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.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