From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Jim Mattson <jmattson@google.com>
Cc: kvm@vger.kernel.org, P J P <ppandit@redhat.com>
Subject: Re: [PATCH 2/2] KVM: VMX: Use just one page for I/O permission bitmaps
Date: Tue, 5 Dec 2017 22:26:40 +0100 [thread overview]
Message-ID: <20171205212639.GD20099@flask> (raw)
In-Reply-To: <20171201182110.7143-2-jmattson@google.com>
2017-12-01 10:21-0800, Jim Mattson:
> Since we no longer allow any I/O ports to be passed through to the guest,
> we can use the same page for I/O bitmap A and I/O bitmap B.
I think we can disable the feature and save the second page as well:
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index e25c55ea2eb7..80859a7cdf6d 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -3624,7 +3624,7 @@ static __init int setup_vmcs_config(struct vmcs_config *vmcs_conf)
#endif
CPU_BASED_CR3_LOAD_EXITING |
CPU_BASED_CR3_STORE_EXITING |
- CPU_BASED_USE_IO_BITMAPS |
+ CPU_BASED_UNCOND_IO_EXITING |
CPU_BASED_MOV_DR_EXITING |
CPU_BASED_USE_TSC_OFFSETING |
CPU_BASED_INVLPG_EXITING |
next prev parent reply other threads:[~2017-12-05 21:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 18:21 [PATCH 1/2] KVM: VMX: remove I/O port 0x80 bypass on Intel hosts Jim Mattson
2017-12-01 18:21 ` [PATCH 2/2] KVM: VMX: Use just one page for I/O permission bitmaps Jim Mattson
2017-12-04 18:30 ` kbuild test robot
2017-12-04 18:34 ` Jim Mattson
2017-12-05 21:26 ` Radim Krčmář [this message]
2017-12-06 0:16 ` Jim Mattson
2017-12-06 11:17 ` Quan Xu
2017-12-06 18:19 ` Jim Mattson
2017-12-07 2:33 ` Quan Xu
2017-12-07 17:06 ` Radim Krčmář
2017-12-08 2:04 ` Quan Xu
2017-12-02 0:34 ` [PATCH 1/2] KVM: VMX: remove I/O port 0x80 bypass on Intel hosts Krish Sadhukhan
2017-12-04 12:44 ` Wanpeng Li
2017-12-04 17:10 ` Jim Mattson
2017-12-05 7:19 ` Wanpeng Li
2017-12-05 11:24 ` Quan Xu
2017-12-05 12:15 ` Wanpeng Li
2017-12-05 21:32 ` Radim Krčmář
2017-12-06 0:36 ` Jim Mattson
2017-12-06 1:38 ` Quan Xu
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=20171205212639.GD20099@flask \
--to=rkrcmar@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=ppandit@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