public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Isaku Yamahata <isaku.yamahata@gmail.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: isaku.yamahata@intel.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, isaku.yamahata@gmail.com,
	Paolo Bonzini <pbonzini@redhat.com>,
	erdemaktas@google.com, Sean Christopherson <seanjc@google.com>,
	Sagi Shahar <sagis@google.com>
Subject: Re: [RFC PATCH 13/13] KVM: x86: remove struct kvm_arch.tdp_max_page_level
Date: Thu, 11 Aug 2022 15:56:42 -0700	[thread overview]
Message-ID: <20220811225642.GA826621@ls.amr.corp.intel.com> (raw)
In-Reply-To: <e275d842-d115-d1d2-a4c2-07ddd057ece1@intel.com>

On Mon, Aug 08, 2022 at 01:40:53PM +0800,
Xiaoyao Li <xiaoyao.li@intel.com> wrote:

> On 8/8/2022 6:18 AM, isaku.yamahata@intel.com wrote:
> > From: Xiaoyao Li <xiaoyao.li@intel.com>
> > 
> > Now that everything is there to support large page for TD guest.  Remove
> > tdp_max_page_level from struct kvm_arch that limits the page size.
> 
> Isaku, we cannot do this to remove tdp_max_page_level. Instead, we need
> assign it as PG_LEVEL_2M, because TDX currently only supports AUG'ing a
> 4K/2M page, 1G is not supported yet.

I went too further. I'll fix it, thanks.
-- 
Isaku Yamahata <isaku.yamahata@gmail.com>

      reply	other threads:[~2022-08-11 22:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07 22:18 [RFC PATCH 00/13] KVM TDX: TDP MMU: large page support isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 01/13] KVM: Update lpage info when private/shared memory are mixed isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 02/13] KVM: TDP_MMU: Go to next level if smaller private mapping exists isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 03/13] KVM: TDX: Pass page level to cache flush before TDX SEAMCALL isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 04/13] KVM: TDX: Pass KVM page level to tdh_mem_page_add() and tdh_mem_page_aug() isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 05/13] KVM: TDX: Pass size to tdx_measure_page() isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 06/13] KVM: TDX: Pass size to reclaim_page() isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 07/13] KVM: TDX: Update tdx_sept_{set,drop}_private_spte() to support large page isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 08/13] KVM: MMU: Introduce level info in PFERR code isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 09/13] KVM: TDX: Pin pages via get_page() right before ADD/AUG'ed to TDs isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 10/13] KVM: MMU: Pass desired page level in err code for page fault handler isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 11/13] KVM: TDP_MMU: Split the large page when zap leaf isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 12/13] KVM: TDX: Split a large page when 4KB page within it converted to shared isaku.yamahata
2022-08-07 22:18 ` [RFC PATCH 13/13] KVM: x86: remove struct kvm_arch.tdp_max_page_level isaku.yamahata
2022-08-08  5:40   ` Xiaoyao Li
2022-08-11 22:56     ` Isaku Yamahata [this message]

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=20220811225642.GA826621@ls.amr.corp.intel.com \
    --to=isaku.yamahata@gmail.com \
    --cc=erdemaktas@google.com \
    --cc=isaku.yamahata@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sagis@google.com \
    --cc=seanjc@google.com \
    --cc=xiaoyao.li@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