From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 871C5C77B62 for ; Fri, 24 Mar 2023 02:18:21 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 0FB636B0072; Thu, 23 Mar 2023 22:18:21 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 0AB6A6B0074; Thu, 23 Mar 2023 22:18:21 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id E97906B0075; Thu, 23 Mar 2023 22:18:20 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id D33F36B0072 for ; Thu, 23 Mar 2023 22:18:20 -0400 (EDT) Received: from smtpin07.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 95F58A0897 for ; Fri, 24 Mar 2023 02:18:20 +0000 (UTC) X-FDA: 80602182360.07.8C52988 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by imf12.hostedemail.com (Postfix) with ESMTP id D10834000E for ; Fri, 24 Mar 2023 02:18:17 +0000 (UTC) Authentication-Results: imf12.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=jFdm0dGr; spf=none (imf12.hostedemail.com: domain of chao.p.peng@linux.intel.com has no SPF policy when checking 192.55.52.120) smtp.mailfrom=chao.p.peng@linux.intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1679624298; h=from:from:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=YzEzGe7erPODTFkWAHbQv6lr7UdEjxxl2qTNAz9xyCs=; b=RsaWPz3qcuwDS88PL62ZB0BQmJFFaqQ6kCKrj5NbO9tj/jU3Jbcl6+PjTVNIz+MldgnjRw d+peFRXLxJTsJfCV8m9jQf64iI2kjdaGvHYZSj7g9LhmdvaO1YLISASbm3F0b/DBQ5wzZI lJSApjIKBAXPOx7K21BGWShZPpUVkOA= ARC-Authentication-Results: i=1; imf12.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=jFdm0dGr; spf=none (imf12.hostedemail.com: domain of chao.p.peng@linux.intel.com has no SPF policy when checking 192.55.52.120) smtp.mailfrom=chao.p.peng@linux.intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1679624298; a=rsa-sha256; cv=none; b=Lw/r9Njgi/5DCh8J/YkJ+xc9No1bUmao+p8SUBCYoMrVRhHwRvPnD38VKL3KRFYWVbDtfL RKyylJ30JP2+QVYpsmQumnuEP9p1zorxOUTHxL1pFvS2Irami7jd+9YXoSSrtBexoVc/mN ZM0M5jnYwRYBu6EIGLW8pDkQGp8iLx4= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1679624297; x=1711160297; h=date:from:to:cc:subject:message-id:reply-to:references: mime-version:in-reply-to; bh=M4FQzDrjs+QeI9XLnd+NfZpr2fRqKi1DscOllLq4wCk=; b=jFdm0dGrZIYK8lbJXMXVQNiPfNgY7gLuxiK82fsogDY8LbhBVqaFqSoC mRcPX3annEtNt3f4p5KFQ4M7/2nMHrcscWOEJQIOkBfiHLqF6wxGkufUF BKpO3aZz1cXTlrIAATab7CQ5MhxE38POw/L0fruOMomw+/9YQmu05XZeW DKvkfxPotehPtTpjAtvWgthQqAefhXAhHJ7B+gNdD+ztCLiR+rgfht3WC iGskGx/HYizMUMpItuQYfEqtuu9AKZBvJVQclX7V4t83ji4v6HstfKzw8 iGSz6BwAWcFqtveVV+1TBntU4Er6sWK+jxYFh3SUMHnkK4+ggSkLddugX A==; X-IronPort-AV: E=McAfee;i="6600,9927,10658"; a="338400955" X-IronPort-AV: E=Sophos;i="5.98,286,1673942400"; d="scan'208";a="338400955" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Mar 2023 19:18:15 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10658"; a="659886402" X-IronPort-AV: E=Sophos;i="5.98,286,1673942400"; d="scan'208";a="659886402" Received: from chaop.bj.intel.com (HELO localhost) ([10.240.192.105]) by orsmga006.jf.intel.com with ESMTP; 23 Mar 2023 19:18:04 -0700 Date: Fri, 24 Mar 2023 10:10:29 +0800 From: Chao Peng To: Isaku Yamahata Cc: Ackerley Tng , seanjc@google.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-arch@vger.kernel.org, linux-api@vger.kernel.org, linux-doc@vger.kernel.org, qemu-devel@nongnu.org, pbonzini@redhat.com, corbet@lwn.net, vkuznets@redhat.com, wanpengli@tencent.com, jmattson@google.com, joro@8bytes.org, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, arnd@arndb.de, naoya.horiguchi@nec.com, linmiaohe@huawei.com, x86@kernel.org, hpa@zytor.com, hughd@google.com, jlayton@kernel.org, bfields@fieldses.org, akpm@linux-foundation.org, shuah@kernel.org, rppt@kernel.org, steven.price@arm.com, mail@maciej.szmigiero.name, vbabka@suse.cz, vannapurve@google.com, yu.c.zhang@linux.intel.com, kirill.shutemov@linux.intel.com, luto@kernel.org, jun.nakajima@intel.com, dave.hansen@intel.com, ak@linux.intel.com, david@redhat.com, aarcange@redhat.com, ddutile@redhat.com, dhildenb@redhat.com, qperret@google.com, tabba@google.com, michael.roth@amd.com, mhocko@suse.com, wei.w.wang@intel.com Subject: Re: [PATCH v10 9/9] KVM: Enable and expose KVM_MEM_PRIVATE Message-ID: <20230324021029.GA2774613@chaop.bj.intel.com> Reply-To: Chao Peng References: <20230128140030.GB700688@chaop.bj.intel.com> <20230308074026.GA2183207@chaop.bj.intel.com> <20230323004131.GA214881@ls.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230323004131.GA214881@ls.amr.corp.intel.com> X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: D10834000E X-Stat-Signature: st7tzsa8seab4gbaq5ynnpmfu88t8mzj X-Rspam-User: X-HE-Tag: 1679624297-717636 X-HE-Meta: U2FsdGVkX1/c+YeOF4PK56moLzyQdeN7RXFTF6cPTcQ/GGYXJJNsBsOMrq9QuAfSCsa0vq2I2QQSQZhX+d8jdC2fAnJk8QRrlGnkRAZUMtOs2WRmA8VKfOSp39JEQHkPCxoaRDxV6LTPTLQwhw7Y9feeMkPUcnViTsVpPwCcBURJHzPaqF4EPOwaelhSaqqRcrwNokrdEisqzf1XQWyIyoJn6ekxIXLtTrfuI7hR32TOb13GowLQNVqOtGXTg9jnSrOqQXe5TMUV0sqXB3NDbwrH19pfCnCV0VHitZ6HQn0DqOnXWyF2HPuBSMZ+/8/MNFYngXnzrr4vs/YtWRzFk1Wb5el8EhM4r7rTItrxuf9fIUOFksQ+ByuH7ekbowVI8R6zRnkPwo5MLtH+Yf5Tcp2YpqIMapvqtJmfP+DxXmu5H6CRnlHTAkcCzy5PYthyZXrC6Ite38HAuxgzR7egB9hg7KOSD3DvjMrFs5A6BotSDB9oKvo5kh5xZ9n+e+Xi/uh3yqav3cmg2TsBzaNk/l813zG4G4FZm83LAyMEPdwxQd2/ljF5QoS7HpRysLWVSIonupPrsVcAC+mHwm/tnWqCXIY7DSTedcXWthiUlVSe4Nb5/6X2RzryG8ev9i+oLaLh2fwbGzM0//CYonDXTyDdhmTahbo9wPaekQiF8/B4x6EEwZ14whdAG5e+W/14AQ/szoaFn8Hy6+w292JqRBW8uGiN9Eg8xXHKucpmHQ2WCK9W37eMTqw6yUPPa+lvM4jwkEYo7cllMPoW500xIcwwhVWGT332sBqeWsRlR8vxShuLxUD+Y2rxabHNRjqiwsYX74zDWwTzONpI0PV9OFQQr61Kg8nsQRPdp0BOh44XWvoOxI8PHc573al6CmqBpT1NxSErgbMSWkT+rFshC0iAkwy675rgkDm0v06eXy+bIzqqxyktspPquw8mBi/tVwM8X2WhM41VcvG47FB D480eDo5 i+yGP9iNf7VrvSr0DaDZYzp/7h/osJJ9nepLFxeKd2AYHRML9zRfUYaqUFSw+sw8qjbnKEhXf4UDPtQ/p33iwMbPHgrcWzw8PqfOGUVvgfBomZauI7d51ojyYwtvGK+DIX4BynEhqgoCGfHW29SWf681X5jg4aVDUep3mztdyDrWtNgsqmFoldRhLxCcq3IQsfc917BLAWRn2HbQFr+coOFtgflfnOpK8k/tWJLJ+dEj7mpd+ruSOJfcfC6hzE1Gv9lhHeJ/3GeLuDCKsYSsW/kV8xYMi4J+tN1PV6aI5vDgNJ5ZWe8vAV2+R8cfa91ADv6RxG4uHWPSe8rTuEkWxXRGjAD46t59vDwC3nAwIdCBWt0IckGtz86r6wbvFmNv71S2fwP+pswVMUEz5EJjMrvx0lYz4lThEn1bfv8f2NHKcLpDDgSy4MAYzYfkZhR485jV7b9b5iRK+fFPGLFBuG17dp5wDUkLkWIgov/cthZTTQ0Lylwsjcnn93g== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed, Mar 22, 2023 at 05:41:31PM -0700, Isaku Yamahata wrote: > On Wed, Mar 08, 2023 at 03:40:26PM +0800, > Chao Peng wrote: > > > On Wed, Mar 08, 2023 at 12:13:24AM +0000, Ackerley Tng wrote: > > > Chao Peng writes: > > > > > > > On Sat, Jan 14, 2023 at 12:01:01AM +0000, Sean Christopherson wrote: > > > > > On Fri, Dec 02, 2022, Chao Peng wrote: > > > > ... > > > > > Strongly prefer to use similar logic to existing code that detects wraps: > > > > > > > > mem->restricted_offset + mem->memory_size < mem->restricted_offset > > > > > > > > This is also where I'd like to add the "gfn is aligned to offset" > > > > > check, though > > > > > my brain is too fried to figure that out right now. > > > > > > > Used count_trailing_zeros() for this TODO, unsure we have other better > > > > approach. > > > > > > > diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c > > > > index afc8c26fa652..fd34c5f7cd2f 100644 > > > > --- a/virt/kvm/kvm_main.c > > > > +++ b/virt/kvm/kvm_main.c > > > > @@ -56,6 +56,7 @@ > > > > #include > > > > #include > > > > #include > > > > +#include > > > > > > > #include "coalesced_mmio.h" > > > > #include "async_pf.h" > > > > @@ -2087,6 +2088,19 @@ static bool kvm_check_memslot_overlap(struct > > > > kvm_memslots *slots, int id, > > > > return false; > > > > } > > > > > > > +/* > > > > + * Return true when ALIGNMENT(offset) >= ALIGNMENT(gpa). > > > > + */ > > > > +static bool kvm_check_rmem_offset_alignment(u64 offset, u64 gpa) > > > > +{ > > > > + if (!offset) > > > > + return true; > > > > + if (!gpa) > > > > + return false; > > > > + > > > > + return !!(count_trailing_zeros(offset) >= count_trailing_zeros(gpa)); > > This check doesn't work expected. For example, offset = 2GB, gpa=4GB > this check fails. This case is expected to fail as Sean initially suggested[*]: I would rather reject memslot if the gfn has lesser alignment than the offset. I'm totally ok with this approach _if_ there's a use case. Until such a use case presents itself, I would rather be conservative from a uAPI perspective. I understand that we put tighter restriction on this but if you see such restriction is really a big issue for real usage, instead of a theoretical problem, then we can loosen the check here. But at that time below code is kind of x86 specific and may need improve. BTW, in latest code, I replaced count_trailing_zeros() with fls64(): return !!(fls64(offset) >= fls64(gpa)); [*] https://lore.kernel.org/all/Y8HldeHBrw+OOZVm@google.com/ Chao > I come up with the following. > > >From ec87e25082f0497431b732702fae82c6a05071bf Mon Sep 17 00:00:00 2001 > Message-Id: > From: Isaku Yamahata > Date: Wed, 22 Mar 2023 15:32:56 -0700 > Subject: [PATCH] KVM: Relax alignment check for restricted mem > > kvm_check_rmem_offset_alignment() only checks based on offset alignment > and GPA alignment. However, the actual alignment for offset depends > on architecture. For x86 case, it can be 1G, 2M or 4K. So even if > GPA is aligned for 1G+, only 1G-alignment is required for offset. > > Without this patch, gpa=4G, offset=2G results in failure of memory slot > creation. > > Fixes: edc8814b2c77 ("KVM: Require gfn be aligned with restricted offset") > Signed-off-by: Isaku Yamahata > --- > arch/x86/include/asm/kvm_host.h | 15 +++++++++++++++ > virt/kvm/kvm_main.c | 9 ++++++++- > 2 files changed, 23 insertions(+), 1 deletion(-) > > diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h > index 88e11dd3afde..03af44650f24 100644 > --- a/arch/x86/include/asm/kvm_host.h > +++ b/arch/x86/include/asm/kvm_host.h > @@ -16,6 +16,7 @@ > #include > #include > #include > +#include > > #include > #include > @@ -143,6 +144,20 @@ > #define KVM_HPAGE_MASK(x) (~(KVM_HPAGE_SIZE(x) - 1)) > #define KVM_PAGES_PER_HPAGE(x) (KVM_HPAGE_SIZE(x) / PAGE_SIZE) > > +#define kvm_arch_required_alignment kvm_arch_required_alignment > +static inline int kvm_arch_required_alignment(u64 gpa) > +{ > + int zeros = count_trailing_zeros(gpa); > + > + WARN_ON_ONCE(!PAGE_ALIGNED(gpa)); > + if (zeros >= KVM_HPAGE_SHIFT(PG_LEVEL_1G)) > + return KVM_HPAGE_SHIFT(PG_LEVEL_1G); > + else if (zeros >= KVM_HPAGE_SHIFT(PG_LEVEL_2M)) > + return KVM_HPAGE_SHIFT(PG_LEVEL_2M); > + > + return PAGE_SHIFT; > +} > + > #define KVM_MEMSLOT_PAGES_TO_MMU_PAGES_RATIO 50 > #define KVM_MIN_ALLOC_MMU_PAGES 64UL > #define KVM_MMU_HASH_SHIFT 12 > diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c > index c9c4eef457b0..f4ff96171d24 100644 > --- a/virt/kvm/kvm_main.c > +++ b/virt/kvm/kvm_main.c > @@ -2113,6 +2113,13 @@ static bool kvm_check_memslot_overlap(struct kvm_memslots *slots, int id, > return false; > } > > +#ifndef kvm_arch_required_alignment > +__weak int kvm_arch_required_alignment(u64 gpa) > +{ > + return PAGE_SHIFT > +} > +#endif > + > /* > * Return true when ALIGNMENT(offset) >= ALIGNMENT(gpa). > */ > @@ -2123,7 +2130,7 @@ static bool kvm_check_rmem_offset_alignment(u64 offset, u64 gpa) > if (!gpa) > return false; > > - return !!(count_trailing_zeros(offset) >= count_trailing_zeros(gpa)); > + return !!(count_trailing_zeros(offset) >= kvm_arch_required_alignment(gpa)); > } > > /* > -- > 2.25.1 > > > > -- > Isaku Yamahata