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 6EDD2C001E0 for ; Mon, 31 Jul 2023 13:47:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230132AbjGaNrK (ORCPT ); Mon, 31 Jul 2023 09:47:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40806 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229877AbjGaNrJ (ORCPT ); Mon, 31 Jul 2023 09:47:09 -0400 Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2CB161708; Mon, 31 Jul 2023 06:47:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1690811228; x=1722347228; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=nHF5W/WdqQq71KtethdkPzIq2ti8gzSk3md7KHrp0EI=; b=AZS3RVNUF987Fp/el6o6nuIeFVXyOmTx5Spgh761j5Y0GOzQddmDVnCG YYn1eM+KGyY7Cu9vTDAPX47mpa7nmXHwmkbj8dGBAnVfXs1z/QJLycTXE 97GlBK6fpA3iYOtA/4/8qof22vGiyuvgB/Cx57SpQESF21ilIqNgPFzNC FNSPJ6g47nWCRvurdTHcsdDAwj3fgDCwDUtMQeGgagS9caWX6OUM78WwB o6+69Flsh7ltuEFT3rpDOHxmRLnWHuC7IINs5Hoi/eFLbju6Jv4vFzDUB n9mMRSZU1H7HUvj//fRpfm7Jr8R9KxYul182Miiv6cYFpN61aOE6wzL0T Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10788"; a="435331032" X-IronPort-AV: E=Sophos;i="6.01,244,1684825200"; d="scan'208";a="435331032" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Jul 2023 06:47:07 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10788"; a="1058936280" X-IronPort-AV: E=Sophos;i="6.01,244,1684825200"; d="scan'208";a="1058936280" Received: from nikithas-mobl.amr.corp.intel.com (HELO [10.212.216.144]) ([10.212.216.144]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Jul 2023 06:47:06 -0700 Message-ID: Date: Mon, 31 Jul 2023 06:47:05 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: [patch v2 21/38] x86/cpu: Provide cpu_init/parse_topology() Content-Language: en-US To: "Michael Kelley (LINUX)" , Thomas Gleixner , LKML Cc: "x86@kernel.org" , Tom Lendacky , Andrew Cooper , "James E.J. Bottomley" , Dick Kennedy , James Smart , "Martin K. Petersen" , "linux-scsi@vger.kernel.org" , Guenter Roeck , "linux-hwmon@vger.kernel.org" , Jean Delvare , Huang Rui , Juergen Gross , Steve Wahl , Mike Travis , Dimitri Sivanich , Russ Anderson References: <20230728105650.565799744@linutronix.de> <20230728120930.839913695@linutronix.de> From: Arjan van de Ven In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-scsi@vger.kernel.org On 7/30/2023 9:05 PM, Michael Kelley (LINUX) wrote: > Does anyone have suggestions on a different way to handle > this that's better than the above diff? Other thoughts? how badly do you need xapic ? Meaning, can x2apic just be used instead always