From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>,
Yang Weijiang <weijiang.yang@intel.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
jmattson@google.com, yu.c.zhang@linux.intel.com,
alazar@bitdefender.com, edwin.zhai@intel.com
Subject: Re: [RESEND PATCH v10 06/10] vmx: spp: Set up SPP paging table at vmentry/vmexit
Date: Tue, 21 Jan 2020 15:01:46 +0100 [thread overview]
Message-ID: <80977d05-405e-826a-3d13-1757427f246b@redhat.com> (raw)
In-Reply-To: <20200110175537.GF21485@linux.intel.com>
On 10/01/20 18:55, Sean Christopherson wrote:
> Unless there is a *very* good reason for these shenanigans, spp.c needs
> to built via the Makefile like any other source. If this is justified
> for whatever reason, then that justification needs to be very clearly
> stated in the changelog.
Well, this #include is the reason why I moved mmu.c to mmu/spp.c. It
shouldn't be hard to create a mmu_internal.h header for things that have
to be shared between mmu.c and spp.c, but I'm okay with having the
#include "spp.c" for now and cleaning it up later. The spp.c file,
albeit ugly, provides hints as to what to put in that header; without it
it's a pointless exercise.
Note that there isn't anything really VMX specific even in the few vmx_*
functions of spp.c. My suggestion is just to rename them to kvm_mmu_*.
Paolo
next prev parent reply other threads:[~2020-01-21 14:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 6:13 [RESEND PATCH v10 00/10] Enable Sub-Page Write Protection Support Yang Weijiang
2020-01-02 6:13 ` [RESEND PATCH v10 01/10] Documentation: Add EPT based Subpage Protection and related APIs Yang Weijiang
2020-01-02 6:13 ` [RESEND PATCH v10 02/10] vmx: spp: Add control flags for Sub-Page Protection(SPP) Yang Weijiang
2020-01-10 16:58 ` Sean Christopherson
2020-01-13 5:44 ` Yang Weijiang
2020-01-02 6:13 ` [RESEND PATCH v10 03/10] mmu: spp: Add SPP Table setup functions Yang Weijiang
2020-01-10 17:26 ` Sean Christopherson
2020-01-13 6:00 ` Yang Weijiang
2020-01-10 17:40 ` Sean Christopherson
2020-01-13 6:04 ` Yang Weijiang
2020-01-02 6:13 ` [RESEND PATCH v10 04/10] mmu: spp: Add functions to operate SPP access bitmap Yang Weijiang
2020-01-10 17:38 ` Sean Christopherson
2020-01-13 6:15 ` Yang Weijiang
2020-01-02 6:13 ` [RESEND PATCH v10 05/10] x86: spp: Introduce user-space SPP IOCTLs Yang Weijiang
2020-01-10 18:10 ` Sean Christopherson
2020-01-13 8:21 ` Yang Weijiang
2020-01-02 6:13 ` [RESEND PATCH v10 06/10] vmx: spp: Set up SPP paging table at vmentry/vmexit Yang Weijiang
2020-01-10 17:55 ` Sean Christopherson
2020-01-13 6:50 ` Yang Weijiang
2020-01-21 14:01 ` Paolo Bonzini [this message]
2020-01-10 18:04 ` Sean Christopherson
2020-01-13 8:10 ` Yang Weijiang
2020-01-13 17:33 ` Sean Christopherson
2020-01-13 18:55 ` Adalbert Lazăr
2020-01-13 21:47 ` Sean Christopherson
2020-01-14 3:08 ` Yang Weijiang
2020-01-14 18:58 ` Sean Christopherson
2020-01-15 1:36 ` Yang Weijiang
2020-01-21 14:14 ` Paolo Bonzini
2020-01-02 6:13 ` [RESEND PATCH v10 07/10] mmu: spp: Enable Lazy mode SPP protection Yang Weijiang
2020-01-02 6:13 ` [RESEND PATCH v10 08/10] mmu: spp: Handle SPP protected pages when VM memory changes Yang Weijiang
2020-01-02 6:13 ` [RESEND PATCH v10 09/10] x86: spp: Add SPP protection check in emulation Yang Weijiang
2020-01-02 6:13 ` [RESEND PATCH v10 10/10] kvm: selftests: selftest for Sub-Page protection Yang Weijiang
-- strict thread matches above, loose matches on Subject: below --
2020-01-02 5:18 [RESEND PATCH v10 00/10] Enable Sub-Page Write Protection Support Yang Weijiang
2020-01-02 5:19 ` [RESEND PATCH v10 06/10] vmx: spp: Set up SPP paging table at vmentry/vmexit Yang Weijiang
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=80977d05-405e-826a-3d13-1757427f246b@redhat.com \
--to=pbonzini@redhat.com \
--cc=alazar@bitdefender.com \
--cc=edwin.zhai@intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=weijiang.yang@intel.com \
--cc=yu.c.zhang@linux.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).