From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: [PATCH RFC 0/3] kvm add ioeventfd pf capability
Date: Sun, 30 Aug 2015 12:12:41 +0300 [thread overview]
Message-ID: <1440925898-23440-1-git-send-email-mst@redhat.com> (raw)
One of the reasons MMIO is slower than port IO is
because it requires a page table lookup.
For normal memory accesses, this is solved by using the TLB
cache - but MMIO entries are either not present or reserved
and so are never cached.
To fix, allow installing an ioeventfd on top of a read only
memory region, which allows the CPU to cache the translations.
Warning: svm patch is untested.
Michael S. Tsirkin (3):
vmx: allow ioeventfd for EPT violations
svm: allow ioeventfd for NPT page faults
kvm: add KVM_CAP_IOEVENTFD_PF capability
include/uapi/linux/kvm.h | 1 +
arch/x86/kvm/svm.c | 5 +++++
arch/x86/kvm/vmx.c | 5 +++++
arch/x86/kvm/x86.c | 1 +
Documentation/virtual/kvm/api.txt | 7 +++++++
5 files changed, 19 insertions(+)
--
MST
next reply other threads:[~2015-08-30 9:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 9:12 Michael S. Tsirkin [this message]
2015-08-30 9:12 ` [PATCH RFC 1/3] vmx: allow ioeventfd for EPT violations Michael S. Tsirkin
2015-08-31 2:53 ` Xiao Guangrong
2015-08-31 7:46 ` Michael S. Tsirkin
2015-08-31 8:32 ` Xiao Guangrong
2015-08-31 11:27 ` Michael S. Tsirkin
2015-08-31 13:23 ` Xiao Guangrong
2015-08-31 14:57 ` Michael S. Tsirkin
2015-09-01 3:37 ` Jason Wang
2015-09-01 4:36 ` Michael S. Tsirkin
2015-09-01 4:49 ` Jason Wang
2015-09-01 6:55 ` Michael S. Tsirkin
2015-08-30 9:12 ` [PATCH RFC 2/3] svm: allow ioeventfd for NPT page faults Michael S. Tsirkin
2015-08-30 9:12 ` [PATCH RFC 3/3] kvm: add KVM_CAP_IOEVENTFD_PF capability Michael S. Tsirkin
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=1440925898-23440-1-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome