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 755B8C77B7A for ; Fri, 19 May 2023 00:08:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229605AbjESAIU (ORCPT ); Thu, 18 May 2023 20:08:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51436 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229522AbjESAIT (ORCPT ); Thu, 18 May 2023 20:08:19 -0400 Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6459410C3; Thu, 18 May 2023 17:08:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1684454898; x=1715990898; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=mV/lqMYc8phJKknd1RZjyJiN6gwG6n5o6thTo+1S4vI=; b=YupcAuqexmVvQJTGctJjeOf8MLv4KkHIdfpHubVus39GRl7p4CppLMye CtvMrUO1qOUoT4dRpoU1v0YWMaTM0F5tjOkHDjPGbr3fCOBMr+JyGa38W TjiSRwuVIKWAb0+8/IJXMeQ3rzhm0FBdoU/c7Eh/pb9Pb75+ivVCFosBJ V8LzymGj0+ALyB36EQ4+o/q4Kf1+b+j5IgLgN96T6x22IW96SXWAxPa11 vzNaBlx8+jM3nRvGB9zjQvwBDpH60xoJTeS84h72MJZeBIDq82pyzaott nxQl0BYvT3vCK7IJ1LMACjOOpWhqAqXxg7W8E/l6iWqKktS6FmbGEYDZD Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10714"; a="415686638" X-IronPort-AV: E=Sophos;i="6.00,175,1681196400"; d="scan'208";a="415686638" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 May 2023 17:08:16 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10714"; a="702319747" X-IronPort-AV: E=Sophos;i="6.00,175,1681196400"; d="scan'208";a="702319747" Received: from mkim1-mobl.amr.corp.intel.com (HELO [10.209.118.171]) ([10.209.118.171]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 May 2023 17:08:16 -0700 Message-ID: <8dc725c8-613a-b51b-6cc1-80d2275ca130@intel.com> Date: Thu, 18 May 2023 17:08:16 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: [PATCH 1/2] x86/numa: Introduce numa_fill_memblks() Content-Language: en-US To: alison.schofield@intel.com, "Rafael J. Wysocki" , Len Brown , Dan Williams , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "H. Peter Anvin" , Andy Lutomirski , Peter Zijlstra , Andrew Morton , Jonathan Cameron , Dave Jiang Cc: x86@kernel.org, linux-cxl@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org References: From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-cxl@vger.kernel.org On 5/18/23 17:04, alison.schofield@intel.com wrote: > The initial use case is the ACPI driver that needs to extend > SRAT defined proximity domains to an entire CXL CFMWS Window[1]. Dumb question time: Why didn't the SRAT just cover this sucker in the first place? Are we fixing up a BIOS bug or is there a legitimate reason that the SRAT didn't cover it up front?