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 4445DC636CD for ; Fri, 10 Feb 2023 04:40:20 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id C59766B00EA; Thu, 9 Feb 2023 23:40:19 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id C097E6B00EB; Thu, 9 Feb 2023 23:40:19 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id AD1296B00EC; Thu, 9 Feb 2023 23:40:19 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0017.hostedemail.com [216.40.44.17]) by kanga.kvack.org (Postfix) with ESMTP id 937B66B00EA for ; Thu, 9 Feb 2023 23:40:19 -0500 (EST) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id 6D6621612E7 for ; Fri, 10 Feb 2023 04:40:19 +0000 (UTC) X-FDA: 80450130558.11.403F315 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by imf02.hostedemail.com (Postfix) with ESMTP id E837880006 for ; Fri, 10 Feb 2023 04:40:15 +0000 (UTC) Authentication-Results: imf02.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=eyDgCs8Y; dmarc=pass (policy=none) header.from=intel.com; spf=pass (imf02.hostedemail.com: domain of dave.hansen@intel.com designates 192.55.52.93 as permitted sender) smtp.mailfrom=dave.hansen@intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1676004016; h=from:from:sender: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:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=QDPKLSPZUFVeGy/rd0eTquJpVNZ0v64kymPfgjFnu68=; b=8P4OJy5HkzOdfKUBJCdijh8SfjTxWmgJ4ksiQh9BVtHXBotK/O9Fpw5fo3DvkWgPeb5ITI UH4y4wfMTCMa/hkTUnuI4rj51PknBFstCBT6v1EmD9GCx9MQeSb1yaCVUFc9mfVPOF+HIZ DgFpF0vheWn+6RtIm6gzjhDHnOZT2Z0= ARC-Authentication-Results: i=1; imf02.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=eyDgCs8Y; dmarc=pass (policy=none) header.from=intel.com; spf=pass (imf02.hostedemail.com: domain of dave.hansen@intel.com designates 192.55.52.93 as permitted sender) smtp.mailfrom=dave.hansen@intel.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1676004016; a=rsa-sha256; cv=none; b=z5X/cIk1yNiDtSE5olhyf6N55vQjll9lPQ8t/zMOD0MO/vLtvMQ1vPUNmvLlVQqV4vifND SpqQw22rb7mzqA4q5m3d36vp+UC+3adp4E2Myu7SC8GPZfd1mJLVv548v603Oxn0B4idEd 9vzQRZjIq+7vbf5V8smIP38xYR0WBuQ= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1676004016; x=1707540016; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=7nMwTcP+iq7uKvjjcoMQMMMq/DesyLZuMxTSuuEj5+M=; b=eyDgCs8YKN8RN+eyGbIoznC3ynXcGa906mlUtdt4vQL9yFc+IU+YeQe+ p4iec16ZTJ0plMpFJAEjao4M4bCKGl2nRxgPvvaip9jJhsz6hwQT55SCY naQXkv0EfnucpH8Jol6tbK6Q5HuNAeDjgZryySBo3KEzSRWmphXZNxBvy Q66zqMC945A3Zx0FDyw7en5HTV4hKQLYfdMjbI2PlX2j8NnihNN8hlSqf GF++DQBuHZaIFq9xXELeJfHUQ3wtnorAuZP7ZWVokBi2H6lk86A05Fenw w+0fZrkxbb/n5LdUAK6FAYFPadYNu1cdb4m3jqmJlHFqfAEgjr/LW6iJ3 Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10616"; a="328026922" X-IronPort-AV: E=Sophos;i="5.97,285,1669104000"; d="scan'208";a="328026922" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Feb 2023 20:40:12 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10616"; a="667926623" X-IronPort-AV: E=Sophos;i="5.97,285,1669104000"; d="scan'208";a="667926623" Received: from cmontgom-mobl.amr.corp.intel.com (HELO [10.209.41.234]) ([10.209.41.234]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Feb 2023 20:40:11 -0800 Message-ID: Date: Thu, 9 Feb 2023 20:40:09 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [RFC PATCH 0/5] Memory access profiler(IBS) driven NUMA balancing Content-Language: en-US To: Bharata B Rao , Peter Zijlstra Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, mgorman@suse.de, mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org, akpm@linux-foundation.org, luto@kernel.org, tglx@linutronix.de, yue.li@memverge.com, Ravikumar.Bangoria@amd.com, ying.huang@intel.com References: <20230208073533.715-1-bharata@amd.com> <4808d3fa-bb68-d4c8-681f-0b2770d78041@intel.com> <369bef08-92cc-9b55-823f-1fe780532967@amd.com> <9848226e-2574-b8e0-4fb4-316957f57fb5@intel.com> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspam-User: X-Rspamd-Server: rspam02 X-Rspamd-Queue-Id: E837880006 X-Stat-Signature: s4k4g9sd1cxap3x8k8uw4ack65ds3xpg X-HE-Tag: 1676004015-917361 X-HE-Meta: U2FsdGVkX19oOVUA3iONmcZg6odELwfDDzWjplggN9bUZpxLBVdWf7WGUyY8EgnMA9IuFG2kedCi3HURqIiofPmTX9QHAaEa69QBEgtIGp59hdimsCj0aUsiuN9zUVE3JcAdFH40k4U4kWWxnKkTGGZCLh/djSxGTrQH7j48SgKNY3pMADx/QZOmpi4owQb9qBB1sqHgJbeDJ0b9wHFeI/gFlyuc46fOt+Ta6dgLX98vD/ia9/Tzyuen0tjRs1LjSKI5xQ+VNlNA43kfkghSNWhYxLSp4bIvdT+ju8b959AY8/oNzHIWnGkVMi+HV0XRyofH8+o/FHmPVD77tVd1gnwtSdnL4PtgsTTQiC7HZ04RsOjoH1HJ/85J8i92FwT31Wi4k1MrOISXcj9Yxs0yV7uNeTlBlFKvjmBhSeu3hRuQRv0lB7/elaV9KGZpNy8/u20Z/H4glhJfyOwtxxDKC3uVFhnFyjE22RDBjB5ASRbV2U8ZhCSFcVGLsCHgEjuLh976ONAc1dva1U6ZnKRY57Ju3lQEsp/EoLyg43ffForHVDkffkOm6sAYMj8jBFjrhv22r/5En7kaW9fcUCeHEvnWRMp3thkA8DJ51TANiMeOWFLRJQD3XS5rS96+wajR+x5UFuZmoX5F9ctc7aRif3DaBUDDKi9J8kdeHeAXbJTYn2N6zX4w2KXxiHIZ1/Tt3BVYGPwU+7kR9Qk4jrFoXYX4WIrYPgruKhgH4b7lD2tAk0byC+YEJPpWQReywL4p1BQnLcYAo0t9C11yGwfPq1K/ezzhHWB0nLCz1bTPVKqN52LrpRAWPDteoXgfD4ctNZ6SX1mdC/dyTWvcUAPHh2mRMPzrR7CJ73+d+KjxO8+PTUq4cpHhIiBK4CLnoIowQZfBAsYgP8V3MHCQ9lPKENidoSIjLy2NmCjCXtb980Mjf7t5Azm1o56oPz2i8qMtwTDDPR2pnGZwaFBqoII irHw2fER U0At0JHWP9wPSqaisvH8bFxr324kSw5gOO1EX/oKnsF+ZO+ZthJ0VYau+CqTHJ8/ATL+dtKC2TsxR2qyOrLd/F4GEzBvVzDl8iuAY+0Pqt/V41Ay2HE6WUW0EkArp8Nuom/EDOYWFT8MB+Ma74wP4Whr5SuEF+s4cIR8B0GBw/LHMf1wf1BDTwxSlmeveHp9VEGdH/dbgdd1PxGSg/PGYPxT675NioNU+qGZn+hTlg5nXm9w/N3RsrmpWN0FDl8RdSs025rHz66V7QTLlnD5yj2dKvaSxzLtg9Pj0 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 2/9/23 20:28, Bharata B Rao wrote: > On 2/9/2023 7:58 PM, Dave Hansen wrote: >> On 2/8/23 22:04, Bharata B Rao wrote: >>>> First, IIRC, Intel PEBS at the time only gave guest virtual addresses in >>>> the PEBS records. They had to be translated back to host addresses to >>>> be usable. That was extra expensive. >>> Just to be clear, I am using IBS in host only and it can give both virtual >>> and physical address. >> Could you talk a little bit about how IBS might get used for NUMA >> balancing guest memory? > IBS can work for guest, but will not provide physical address. Also > the support for virtualized IBS isn't upstream yet. > > However I am not sure how effective or useful NUMA balancing within a guest > is, as the actual physical addresses are transparent to the guest. > > Additionally when using IBS in host, it is possible to prevent collection > of samples from secure guests by using the PreventHostIBS feature. > (https://lore.kernel.org/linux-perf-users/20230206060545.628502-1-manali.shukla@amd.com/T/#) I was wondering specifically about how a host might use IBS to balance guest memory transparently to the guest. Now how a guest might use IBS to balance its own memory.