From: Vipin Sharma <vipinsh@google.com>
To: Sean Christopherson <seanjc@google.com>
Cc: pbonzini@redhat.com, dmatlack@google.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] KVM: x86/mmu: Track TDP MMU NX huge pages separately
Date: Tue, 3 Sep 2024 13:26:46 -0700 [thread overview]
Message-ID: <20240903202646.GA423248.vipinsh@google.com> (raw)
In-Reply-To: <ZtDXQ6oeQrb8LxkX@google.com>
On 2024-08-29 13:18:27, Sean Christopherson wrote:
> On Thu, Aug 29, 2024, Vipin Sharma wrote:
> > @@ -871,8 +871,17 @@ void track_possible_nx_huge_page(struct kvm *kvm, struct kvm_mmu_page *sp)
> > return;
> >
> > ++kvm->stat.nx_lpage_splits;
> > - list_add_tail(&sp->possible_nx_huge_page_link,
> > - &kvm->arch.possible_nx_huge_pages);
> > + if (is_tdp_mmu_page(sp)) {
> > +#ifdef CONFIG_X86_64
> > + ++kvm->arch.tdp_mmu_possible_nx_huge_pages_count;
> > + list_add_tail(&sp->possible_nx_huge_page_link,
> > + &kvm->arch.tdp_mmu_possible_nx_huge_pages);
> > +#endif
>
> Pass in the count+list, that way there's no #ifdef and no weird questions for
> what happens if the impossible happens (is_tdp_mmu_page() on 32-bit KVM).
>
> void track_possible_nx_huge_page(struct kvm *kvm, struct kvm_mmu_page *sp,
> u64 *nr_pages, struct list_head *pages)
> {
> /*
> * If it's possible to replace the shadow page with an NX huge page,
> * i.e. if the shadow page is the only thing currently preventing KVM
> * from using a huge page, add the shadow page to the list of "to be
> * zapped for NX recovery" pages. Note, the shadow page can already be
> * on the list if KVM is reusing an existing shadow page, i.e. if KVM
> * links a shadow page at multiple points.
> */
> if (!list_empty(&sp->possible_nx_huge_page_link))
> return;
>
> ++kvm->stat.nx_lpage_splits;
> ++(*nr_pages);
> list_add_tail(&sp->possible_nx_huge_page_link, pages);
> }
>
Sounds good, I was not sure if passing pointers and incrementing count
via pointer will be accepted.
next prev parent reply other threads:[~2024-09-03 20:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 19:11 [PATCH v2 0/4] KVM: x86/mmu: Run NX huge page recovery under MMU read lock Vipin Sharma
2024-08-29 19:11 ` [PATCH v2 1/4] KVM: x86/mmu: Track TDP MMU NX huge pages separately Vipin Sharma
2024-08-29 20:18 ` Sean Christopherson
2024-09-03 20:26 ` Vipin Sharma [this message]
2024-08-29 19:11 ` [PATCH v2 2/4] KVM: x86/mmu: Extract out TDP MMU NX huge page recovery code Vipin Sharma
2024-08-29 19:11 ` [PATCH v2 3/4] KVM: x86/mmu: Rearrange locks and to_zap count for NX huge page recovery Vipin Sharma
2024-08-29 19:11 ` [PATCH v2 4/4] KVM: x86/mmu: Recover TDP MMU NX huge pages using MMU read lock Vipin Sharma
2024-08-29 20:06 ` Sean Christopherson
2024-09-03 20:23 ` Vipin Sharma
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=20240903202646.GA423248.vipinsh@google.com \
--to=vipinsh@google.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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