From: "Radim Krčmář" <rkrcmar@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Gleb Natapov <gleb@kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: [PATCH 0/3] kvm: APICv register write workaround
Date: Thu, 30 Oct 2014 15:06:44 +0100 [thread overview]
Message-ID: <1414678007-9377-1-git-send-email-rkrcmar@redhat.com> (raw)
APICv traps register writes, so we can't retrieve previous value, but
our code depends on detecting changes.
Apart from disabling APIC register virtualization, we can detect the
change by using extra memory. One value history is enough, but we still
don't want to keep it for every APIC register, for performance reasons.
This leaves us with either a new framework, or exceptions ...
The latter options fits KVM's path better [1,2].
And when we already mirror a part of registers, optimizing access is
acceptable [3]. (Squashed to keep bisecters happy.)
---
Radim Krčmář (3):
KVM: x86: detect SPIV changes under APICv
KVM: x86: detect LVTT changes under APICv
KVM: x86: optimize some accesses to LVTT and SPIV
arch/x86/kvm/lapic.c | 32 +++++++++++++++++---------------
arch/x86/kvm/lapic.h | 8 +++++---
2 files changed, 22 insertions(+), 18 deletions(-)
--
2.1.0
next reply other threads:[~2014-10-30 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 14:06 Radim Krčmář [this message]
2014-10-30 14:06 ` [PATCH 1/3] KVM: x86: detect SPIV changes under APICv Radim Krčmář
2014-10-30 14:06 ` [PATCH 2/3] KVM: x86: detect LVTT " Radim Krčmář
2014-10-30 14:06 ` [PATCH 3/3] KVM: x86: optimize some accesses to LVTT and SPIV Radim Krčmář
2014-10-31 15:06 ` [PATCH 0/3] kvm: APICv register write workaround Paolo Bonzini
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=1414678007-9377-1-git-send-email-rkrcmar@redhat.com \
--to=rkrcmar@redhat.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.