From: Yan Zhao <yan.y.zhao@intel.com>
To: liulongfang <liulongfang@huawei.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<kvm@vger.kernel.org>, <pbonzini@redhat.com>, <seanjc@google.com>,
<mike.kravetz@oracle.com>, <apopple@nvidia.com>, <jgg@nvidia.com>,
<rppt@kernel.org>, <akpm@linux-foundation.org>,
<kevin.tian@intel.com>
Subject: Re: [RFC PATCH 3/3] KVM: x86/mmu: skip zap maybe-dma-pinned pages for NUMA migration
Date: Mon, 4 Sep 2023 15:03:51 +0800 [thread overview]
Message-ID: <ZPWBVxs77rtDWfvx@yzhao56-desk.sh.intel.com> (raw)
In-Reply-To: <a14ced20-9d4b-cc76-dcba-c14164e84aa1@huawei.com>
> I have a question. The numa id of the cpu can be reconfigured in the VM.
Are you talking about vNUMA and the numa balancing in guest?
> Will the page table migration operations initiated by the numa balance in the
> VM and the numa balance in the host conflict with each other after this setting?
There's no page table migration in host. Only page table is modified and
page is migrated in a single host.
Live migration also doesn't copy the secondary page tables (i.e.
EPT/NPT) to the target. Instead, it's rebuilt in the target side.
So, I don't quite understand your question here.
prev parent reply other threads:[~2023-09-04 7:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 7:13 [RFC PATCH 0/3] Reduce NUMA balance caused TLB-shootdowns in a VM Yan Zhao
2023-08-08 7:14 ` [RFC PATCH 1/3] mm/mmu_notifier: introduce a new mmu notifier flag MMU_NOTIFIER_RANGE_NUMA Yan Zhao
2023-08-08 7:15 ` [RFC PATCH 2/3] mm: don't set PROT_NONE to maybe-dma-pinned pages for NUMA-migrate purpose Yan Zhao
2023-08-08 7:17 ` [RFC PATCH 3/3] KVM: x86/mmu: skip zap maybe-dma-pinned pages for NUMA migration Yan Zhao
2023-08-08 12:32 ` Jason Gunthorpe
2023-08-08 14:26 ` Sean Christopherson
2023-08-08 14:32 ` Jason Gunthorpe
2023-08-08 23:56 ` Sean Christopherson
2023-08-09 0:11 ` Yan Zhao
2023-08-09 11:59 ` Jason Gunthorpe
2023-08-10 9:08 ` Yan Zhao
2023-08-09 5:06 ` Yan Zhao
2023-08-09 2:58 ` Yan Zhao
2023-08-09 0:29 ` Yan Zhao
2023-08-26 6:39 ` liulongfang
2023-09-04 7:03 ` Yan Zhao [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=ZPWBVxs77rtDWfvx@yzhao56-desk.sh.intel.com \
--to=yan.y.zhao@intel.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liulongfang@huawei.com \
--cc=mike.kravetz@oracle.com \
--cc=pbonzini@redhat.com \
--cc=rppt@kernel.org \
--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