From: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
akpm-3NddpPZAyC0@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] KVM: Improve interrupt response
Date: Tue, 2 Jan 2007 12:12:56 +0100 [thread overview]
Message-ID: <20070102111256.GA27541@elte.hu> (raw)
In-Reply-To: <20061231132232.A98E92500F7-LjA0eNSCdXrQnzwC+xcbyw@public.gmane.org>
* Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
> From: Dor Laor <dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
>
> The current interrupt injection mechanism might delay an interrupt
> under the following circumstances:
>
> - if injection fails because the guest is not interruptible (rflags.IF clear,
> or after a 'mov ss' or 'sti' instruction). Userspace can check rflags,
> but the other cases or not testable under the current API.
> - if injection fails because of a fault during delivery. This probably
> never happens under normal guests.
> - if injection fails due to a physical interrupt causing a vmexit so that
> it can be handled by the host.
>
> in all cases the guest proceeds without processing the interrupt,
> reducing the interactive feel and interrupt throughput of the guest.
>
> This patch fixes the situation by allowing userspace to request an
> exit when the 'interrupt window' opens, so that it can re-inject the
> interrupt at the right time. Guest interactivity is very visibly
> improved.
Andrew, i'd argue for this to be included in v2.6.20, because it's an
obvious bugfix. I've tested this patch and it's included in current -rt
and i saw no regressions.
Acked-by: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Ingo
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-01-02 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 13:22 [PATCH] KVM: Improve interrupt response Avi Kivity
[not found] ` <20061231132232.A98E92500F7-LjA0eNSCdXrQnzwC+xcbyw@public.gmane.org>
2007-01-02 11:12 ` Ingo Molnar [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=20070102111256.GA27541@elte.hu \
--to=mingo-x9un+bfzkdi@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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