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]

To: Chao Peng <chao.p.peng@xxxxxxxxxxxxxxx>
Subject: Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
From: Xiaoyao Li <xiaoyao.li@xxxxxxxxx>
Date: Tue, 13 Dec 2022 20:04:14 +0800
Cc: kvm@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-arch@xxxxxxxxxxxxxxx, linux-api@xxxxxxxxxxxxxxx, linux-doc@xxxxxxxxxxxxxxx, qemu-devel@xxxxxxxxxx, 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: <20221208113003.GE1304936@chaop.bj.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/8/2022 7:30 PM, Chao Peng wrote:

On Thu, Dec 08, 2022 at 04:37:03PM +0800, Xiaoyao Li wrote:

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 why HAVE_KVM_RESTRICTED_MEM is
needed.


The reason is we want KVM further controls the feature enabling. An
opt-in CONFIG_RESTRICTEDMEM can cause problem if user sets that for
unsupported architectures.

HAVE_KVM_RESTRICTED_MEM is not used in this patch. It's better tointroduce it in the patch that actually uses it.

Here is the original discussion:
https://lore.kernel.org/all/YkJLFu98hZOvTSrL@xxxxxxxxxx/

Thanks,
Chao

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
- Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  - From: Xiaoyao Li
- Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory
  - From: Chao Peng

Prev by Date: [PATCH] mnt_idmapping: move ima-only helpers to ima
Next by Date: [PATCH] copy_file_range.2: Fix wrong kernel version information
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] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]