Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
From: Xiaoyao Li <xiaoyao.li@xxxxxxxxx>
Date: Thu, 8 Dec 2022 16:37:03 +0800
Cc: Paolo Bonzini <pbonzini@xxxxxxxxxx>, Jonathan Corbet <corbet@xxxxxxx>, Sean Christopherson <seanjc@xxxxxxxxxx>, Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>, Wanpeng Li <wanpengli@xxxxxxxxxxx>, Jim Mattson <jmattson@xxxxxxxxxx>, Joerg Roedel <joro@xxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, Arnd Bergmann <arnd@xxxxxxxx>, Naoya Horiguchi <naoya.horiguchi@xxxxxxx>, Miaohe Lin <linmiaohe@xxxxxxxxxx>, x86@xxxxxxxxxx, "H . Peter Anvin" <hpa@xxxxxxxxx>, Hugh Dickins <hughd@xxxxxxxxxx>, Jeff Layton <jlayton@xxxxxxxxxx>, "J . Bruce Fields" <bfields@xxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Shuah Khan <shuah@xxxxxxxxxx>, Mike Rapoport <rppt@xxxxxxxxxx>, Steven Price <steven.price@xxxxxxx>, "Maciej S . Szmigiero" <mail@xxxxxxxxxxxxxxxxxxxxx>, Vlastimil Babka <vbabka@xxxxxxx>, Vishal Annapurve <vannapurve@xxxxxxxxxx>, Yu Zhang <yu.c.zhang@xxxxxxxxxxxxxxx>, "Kirill A . Shutemov" <kirill.shutemov@xxxxxxxxxxxxxxx>, luto@xxxxxxxxxx, jun.nakajima@xxxxxxxxx, dave.hansen@xxxxxxxxx, ak@xxxxxxxxxxxxxxx, david@xxxxxxxxxx, aarcange@xxxxxxxxxx, ddutile@xxxxxxxxxx, dhildenb@xxxxxxxxxx, Quentin Perret <qperret@xxxxxxxxxx>, tabba@xxxxxxxxxx, Michael Roth <michael.roth@xxxxxxx>, mhocko@xxxxxxxx, wei.w.wang@xxxxxxxxx
In-reply-to: <20221202061347.1070246-4-chao.p.peng@linux.intel.com>
References: <20221202061347.1070246-1-chao.p.peng@linux.intel.com> <20221202061347.1070246-4-chao.p.peng@linux.intel.com>
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.5.1

On 12/2/2022 2:13 PM, Chao Peng wrote:

..

Together with the change, a new config HAVE_KVM_RESTRICTED_MEM is added
and right now it is selected on X86_64 only.

From the patch implementation, I have no idea whyHAVE_KVM_RESTRICTED_MEM is needed.

Follow-Ups:
- Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  - From: Chao Peng

References:
- [PATCH v10 0/9] KVM: mm: fd-based approach for supporting KVM
  - From: Chao Peng
- [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  - From: Chao Peng

Prev by Date: RE: [PATCH] vfio/type1: Cleanup remaining vaddr removal/update fragments
Next by Date: [PATCH v13 4/7] s390x/cpu_topology: CPU topology migration
Previous by thread: Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
Next by thread: Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]