From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f73.google.com (mail-pj1-f73.google.com [209.85.216.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E92059445 for ; Thu, 20 Apr 2023 20:21:30 +0000 (UTC) Received: by mail-pj1-f73.google.com with SMTP id 98e67ed59e1d1-2476a718feeso1186931a91.2 for ; Thu, 20 Apr 2023 13:21:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1682022090; x=1684614090; h=content-transfer-encoding:cc:to:from:subject:message-id:references :mime-version:in-reply-to:date:from:to:cc:subject:date:message-id :reply-to; bh=mpTOoqFwr6PXx8ZhPhp2F5vKR6FTzxj9fbkenjMTw+I=; b=ayMsf68dO1AJVJrABTkUhl1NMkj9wzJIuYm23qPHqGOJfv8Tzmr/MMZxooBdbFWuv6 cTmzvZGQL22AByne/8vqNIb7Ula7gng50G2+VKpqMx484CV6DQsedQ06XTaeu+DQM49b Xv9bZenL7yQF4ga4/MTIH59v2WCdxiBmdnXbayZvn5qNdcPSs6tpTkKYHX2oOZ/dvVZJ 7iBN8GopMbKfBq0gxr0rs7bCE35mGMrwZMp+IWcuRhn8r0n6FUEqG0/jssdTgwXjPBGo QXUjX+PVWO6OKOdititLEBWM39bjy4BtfGL6XjtBawa9+EgUy4H8fBEsjKUgS+1l2k/k uAwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682022090; x=1684614090; h=content-transfer-encoding:cc:to:from:subject:message-id:references :mime-version:in-reply-to:date:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=mpTOoqFwr6PXx8ZhPhp2F5vKR6FTzxj9fbkenjMTw+I=; b=Sd8tOsAQMaTILWb8+EgtiI+vxUUxVCrRY6jmFXibCDWaPrQc8GXzFKuADtpQrjskll l7e0lY4bR6QZIBlyrS2/RuPTHX6xvZeiik7BJeApe0Zuk6siJhWnQ4a78R+nDeull/vT HZQJEzKbsATLGe8UN/HPoGo5dH3l26uasFl/AZoknnDMTqVQ+VA4DPMfjj0dGOXxCJN/ qNx4IrJs1pzOb8/1rYwTYjFbvDbLcbRNH5SzzTaXrD0XVqs+UZ0/7Et1+9rNZS549irc T/t3i3cZk69Cwvq8igVRkI5pn3S/5q5F4FWCkNk3bgb812NVUFwKcJO5GEm3v61iCPGr H+rw== X-Gm-Message-State: AAQBX9cUevLNwjW2uZLCZ5/4e+tT+9EDbj0+jYSd9lFIQHcaFRRU64gQ 1HxTA8TywL34MrdzxqVn9lU+L6J5saI= X-Google-Smtp-Source: AKy350bOw0CcGSD5HxBsCHP7eQv+pVq4+ffvtFW6Bs0RrLmmQY0i686r1Bx3KLV/2OwqstA5HB5kaL3ma/k= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:90a:470b:b0:247:e66:1d90 with SMTP id h11-20020a17090a470b00b002470e661d90mr728232pjg.6.1682022090286; Thu, 20 Apr 2023 13:21:30 -0700 (PDT) Date: Thu, 20 Apr 2023 13:21:28 -0700 In-Reply-To: Precedence: bulk X-Mailing-List: linux-coco@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 References: <20230419221716.3603068-1-atishp@rivosinc.com> Message-ID: Subject: Re: [RFC 00/48] RISC-V CoVE support From: Sean Christopherson To: Atish Kumar Patra Cc: linux-kernel@vger.kernel.org, Alexandre Ghiti , Andrew Jones , Andrew Morton , Anup Patel , Atish Patra , "=?iso-8859-1?Q?Bj=F6rn_T=F6pel?=" , Suzuki K Poulose , Will Deacon , Marc Zyngier , linux-coco@lists.linux.dev, Dylan Reid , abrestic@rivosinc.com, Samuel Ortiz , Christoph Hellwig , Conor Dooley , Greg Kroah-Hartman , Guo Ren , Heiko Stuebner , Jiri Slaby , kvm-riscv@lists.infradead.org, kvm@vger.kernel.org, linux-mm@kvack.org, linux-riscv@lists.infradead.org, Mayuresh Chitale , Palmer Dabbelt , Paolo Bonzini , Paul Walmsley , Rajnesh Kanwal , Uladzislau Rezki Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Fri, Apr 21, 2023, Atish Kumar Patra wrote: > On Thu, Apr 20, 2023 at 10:00=E2=80=AFPM Sean Christopherson wrote: > > > > On Wed, Apr 19, 2023, Atish Patra wrote: > > > 2. Lazy gstage page allocation vs upfront allocation with page pool. > > > Currently, all gstage mappings happen at runtime during the fault. Th= is is expensive > > > as we need to convert that page to confidential memory as well. A pag= e pool framework > > > may be a better choice which can hold all the confidential pages whic= h can be > > > pre-allocated upfront. A generic page pool infrastructure may benefit= other CC solutions ? > > > > I'm sorry, what? Do y'all really not pay any attention to what is happ= ening > > outside of the RISC-V world? > > > > We, where "we" is KVM x86 and ARM, with folks contributing from 5+ comp= anines, > > have been working on this problem for going on three *years*. And that= 's just > > from the first public posting[1], there have been discussions about how= to approach > > this for even longer. There have been multiple related presentations a= t KVM Forum, > > something like 4 or 5 just at KVM Forum 2022 alone. > > >=20 > I did mention about that in the 1st item in the TODO list. My apologies, I completely missed the todo list. > Thanks for your suggestion. It seems we should just directly move to > restrictedmem asap. Yes please, for the sake of everyone involved. It will likely save you fro= m running into the same pitfalls that x86 and ARM already encountered, and th= e more eyeballs and use cases on whatever restrictemem ends up being called, the b= etter. Thanks!