From: Avi Kivity <avi@redhat.com>
To: "Yang, Sheng" <sheng.yang@intel.com>, Chris Wright <chrisw@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Migration assigned device interrupts
Date: Thu, 01 Oct 2009 16:50:51 +0200 [thread overview]
Message-ID: <4AC4C1CB.9040903@redhat.com> (raw)
It occurs to me that we're handling assigned device interrupts
inefficiently: an interrupt is received on cpu A, injected, and wakes up
(or forces out of guest mode) a vcpu on cpu B. This involved an IPI and
bothers two cpus instead of one.
But we often known which vcpu will be woken up (DM_FIXED interupts) and
which cpu it runs on (vcpu->cpu, preempt notifiers) so we can migrate
the host interrupt to follow the vcpu it wakes. This should improve
latency and cpu utilization.
I'm not sure how to do this generically (with irqfd), so vhost-net can
benefit from it as well - migrate the vhost threads and the interrupts
that feed them too.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
reply other threads:[~2009-10-01 14:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4AC4C1CB.9040903@redhat.com \
--to=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=sheng.yang@intel.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;
as well as URLs for NNTP newsgroup(s).