Re: [PATCH v4 12/12] KVM: Expose KVM_MEM_PRIVATE

2022-02-24 Thread Chao Peng
On Wed, Feb 23, 2022 at 07:32:37PM +0100, Maciej S. Szmigiero wrote: > On 23.02.2022 13:00, Chao Peng wrote: > > On Tue, Feb 22, 2022 at 02:16:46AM +0100, Maciej S. Szmigiero wrote: > > > On 17.02.2022 14:45, Chao Peng wrote: > > > > On Tue, Jan 25, 2022 at 09:20:39PM +0100, Maciej S. Szmigiero

Re: [PATCH v4 12/12] KVM: Expose KVM_MEM_PRIVATE

2022-02-23 Thread Maciej S. Szmigiero
On 23.02.2022 13:00, Chao Peng wrote: On Tue, Feb 22, 2022 at 02:16:46AM +0100, Maciej S. Szmigiero wrote: On 17.02.2022 14:45, Chao Peng wrote: On Tue, Jan 25, 2022 at 09:20:39PM +0100, Maciej S. Szmigiero wrote: On 18.01.2022 14:21, Chao Peng wrote: KVM_MEM_PRIVATE is not exposed by

Re: [PATCH v4 12/12] KVM: Expose KVM_MEM_PRIVATE

2022-02-23 Thread Chao Peng
On Tue, Feb 22, 2022 at 02:16:46AM +0100, Maciej S. Szmigiero wrote: > On 17.02.2022 14:45, Chao Peng wrote: > > On Tue, Jan 25, 2022 at 09:20:39PM +0100, Maciej S. Szmigiero wrote: > > > On 18.01.2022 14:21, Chao Peng wrote: > > > > KVM_MEM_PRIVATE is not exposed by default but architecture code

Re: [PATCH v4 12/12] KVM: Expose KVM_MEM_PRIVATE

2022-02-21 Thread Maciej S. Szmigiero
On 17.02.2022 14:45, Chao Peng wrote: On Tue, Jan 25, 2022 at 09:20:39PM +0100, Maciej S. Szmigiero wrote: On 18.01.2022 14:21, Chao Peng wrote: KVM_MEM_PRIVATE is not exposed by default but architecture code can turn on it by implementing kvm_arch_private_memory_supported(). Also private

Re: [PATCH v4 12/12] KVM: Expose KVM_MEM_PRIVATE

2022-02-17 Thread Chao Peng
On Tue, Jan 25, 2022 at 09:20:39PM +0100, Maciej S. Szmigiero wrote: > On 18.01.2022 14:21, Chao Peng wrote: > > KVM_MEM_PRIVATE is not exposed by default but architecture code can turn > > on it by implementing kvm_arch_private_memory_supported(). > > > > Also private memslot cannot be movable

Re: [PATCH v4 12/12] KVM: Expose KVM_MEM_PRIVATE

2022-01-25 Thread Maciej S. Szmigiero
On 18.01.2022 14:21, Chao Peng wrote: KVM_MEM_PRIVATE is not exposed by default but architecture code can turn on it by implementing kvm_arch_private_memory_supported(). Also private memslot cannot be movable and the same file+offset can not be mapped into different GFNs. Signed-off-by: Yu

[PATCH v4 12/12] KVM: Expose KVM_MEM_PRIVATE

2022-01-18 Thread Chao Peng
KVM_MEM_PRIVATE is not exposed by default but architecture code can turn on it by implementing kvm_arch_private_memory_supported(). Also private memslot cannot be movable and the same file+offset can not be mapped into different GFNs. Signed-off-by: Yu Zhang Signed-off-by: Chao Peng ---