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 09DE3C61DA4 for ; Thu, 9 Feb 2023 15:02:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230388AbjBIPCC (ORCPT ); Thu, 9 Feb 2023 10:02:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46024 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230175AbjBIPB5 (ORCPT ); Thu, 9 Feb 2023 10:01:57 -0500 Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 58439A0 for ; Thu, 9 Feb 2023 07:01:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1675954913; x=1707490913; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=/+xWAVVPl6YOh/i5Jh/m3nRXHie4D7DLrU2F06Zxyyg=; b=c5vAAKmufmBhEphQI3f/Z937JGRT3Ta6SMzzm5s1gZHTpPNbet9zhtjh h9+37EVZ5y+M6ZBSObT8ACrTl077QAz2bdPvMV3P0Jgb72So7sOlKdr3k nO0m3nmGsOuwUrVrH0gTXhF6sz5jArccqB8Ec3YEilNjs04huPdfae/va 1wHqXAv+0Bwt4/duB2qXtqMwdpEGS5ugeGEH0m83VoBpeSq7KOQFHZa3h pHReLzjErjIzamRaK1BeMlTidcSbGFOcFmrzBGSZucxBxjpcF0/W45te1 AJa7UN7MprwQmkamyYMYrA25GwL10uxlCTaryCAsVTaX/qQZi+gy5FqIi A==; X-IronPort-AV: E=McAfee;i="6500,9779,10615"; a="331420885" X-IronPort-AV: E=Sophos;i="5.97,283,1669104000"; d="scan'208";a="331420885" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Feb 2023 06:28:10 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10615"; a="791610358" X-IronPort-AV: E=Sophos;i="5.97,283,1669104000"; d="scan'208";a="791610358" Received: from davidsan-mobl3.amr.corp.intel.com (HELO [10.209.22.211]) ([10.209.22.211]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Feb 2023 06:28:09 -0800 Message-ID: <9848226e-2574-b8e0-4fb4-316957f57fb5@intel.com> Date: Thu, 9 Feb 2023 06:28:08 -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> From: Dave Hansen In-Reply-To: <369bef08-92cc-9b55-823f-1fe780532967@amd.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?