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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0B8EDCCA47F for ; Tue, 28 Jun 2022 01:15:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242954AbiF1BPh (ORCPT ); Mon, 27 Jun 2022 21:15:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41982 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242981AbiF1BP2 (ORCPT ); Mon, 27 Jun 2022 21:15:28 -0400 Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D367322B2E for ; Mon, 27 Jun 2022 18:15:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1656378927; x=1687914927; h=message-id:subject:from:to:cc:date:in-reply-to: references:content-transfer-encoding:mime-version; bh=g4aK040aBriUUhWE+Z8oUxYhPOJKeQMijUgvuZuOewk=; b=Re3KGsFhMzSJ+yZg5PQrx1jxHtQExEYkCpV7TZsFLborQbW/wpBGjesh xiAo2Drn2zIg0Ohk4yyUO9xJaVd4UCae4I0n5pojXz4jcLei+6oEht7RW 3GWVZFRv1b1PmV2Vc3og3J+mvrn16UlwTV/wRJR3hn4eYVli3JmilndMy AAAUXOIcuzLeGHn/+uyAoGEYdvfL8D0YyWS3GXVz0D1R0I8773jam5ebF QARWwQKyZExiqMwwqySh84rtOi7HRY3zJ4deS+6hhoYagOhxi1aAgSIjk H2S0Lj5NnJrcGr3I7OQt5uFFdx+M/Tr104qaUXPqaxd15rxYypxO5D0/O w==; X-IronPort-AV: E=McAfee;i="6400,9594,10391"; a="343291624" X-IronPort-AV: E=Sophos;i="5.92,227,1650956400"; d="scan'208";a="343291624" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Jun 2022 18:15:27 -0700 X-IronPort-AV: E=Sophos;i="5.92,227,1650956400"; d="scan'208";a="616997125" Received: from iiturbeo-mobl.amr.corp.intel.com (HELO khuang2-desk.gar.corp.intel.com) ([10.212.89.183]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Jun 2022 18:15:23 -0700 Message-ID: <6b84f9058ce5e60fdf3e4abd075a2b8f591ccffc.camel@intel.com> Subject: Re: [PATCH v8 4/5] x86/mm: Add noalias variants of set_memory_*crypted() functions From: Kai Huang To: Dave Hansen , "Kirill A. Shutemov" Cc: Kuppuswamy Sathyanarayanan , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H . Peter Anvin" , Tony Luck , Andi Kleen , Wander Lairson Costa , Isaku Yamahata , marcelo.cerri@canonical.com, tim.gardner@canonical.com, khalid.elmously@canonical.com, philip.cox@canonical.com, linux-kernel@vger.kernel.org Date: Tue, 28 Jun 2022 13:15:21 +1200 In-Reply-To: References: <20220609025220.2615197-1-sathyanarayanan.kuppuswamy@linux.intel.com> <20220609025220.2615197-5-sathyanarayanan.kuppuswamy@linux.intel.com> <20220627151257.fhynhvcnpk22kflw@black.fi.intel.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.2 (3.44.2-1.fc36) MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >=20 > I still don't like the idea of using the DMA API itself. But, maybe we > need some common infrastructure that the DMA API and this code use which > says, "get me some pages that I can safely make shared". Right. For instance any KVM PV feature would require shared memory, and DM= A API normally doesn't fit (taking 'struct kvm_steal_time' as example). Maybe we can reserve a CMA for this purpose. --=20 Thanks, -Kai