From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762054AbdJRHJl (ORCPT ); Wed, 18 Oct 2017 03:09:41 -0400 Received: from bombadil.infradead.org ([65.50.211.133]:40050 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752707AbdJRHJg (ORCPT ); Wed, 18 Oct 2017 03:09:36 -0400 Date: Wed, 18 Oct 2017 00:09:36 -0700 From: Christoph Hellwig To: Zhang Yi Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, pbonzini@redhat.com, rkrcmar@redhat.com Subject: Re: [PATCH RFC 00/10] Intel EPT-Based Sub-page Write Protection Support. Message-ID: <20171018070936.GA10808@infradead.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > We introduced 2 ioctls to let user application to set/get subpage write protection bitmap per gfn, each gfn corresponds to a bitmap. > The user application, qemu, or some other security control daemon. will set the protection bitmap via this ioctl. > the API defined as: > struct kvm_subpage { > __u64 base_gfn; > __u64 npages; > /* sub-page write-access bitmap array */ > __u32 access_map[SUBPAGE_MAX_BITMAP]; > }sp; > kvm_vm_ioctl(s, KVM_SUBPAGES_SET_ACCESS, &sp) > kvm_vm_ioctl(s, KVM_SUBPAGES_GET_ACCESS, &sp) What is the use case for this feature?