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 16C8DC001DB for ; Sun, 13 Aug 2023 15:04:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231450AbjHMPEj (ORCPT ); Sun, 13 Aug 2023 11:04:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55522 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231171AbjHMPEh (ORCPT ); Sun, 13 Aug 2023 11:04:37 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DF6B0E6A for ; Sun, 13 Aug 2023 08:04:39 -0700 (PDT) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1691939078; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=67wOu/askamgNgaMWz6ATjabCYrlBnc8iy9pPrPhRdo=; b=LuysFXg8c6hn5z/HyX9NbSVhXxREo1k0rcN1T+5U9kWNn1DIS0GEVOH6927u5nTMzvY/QV a9Hw8eNg5beK02pP+sKRW2+an5WVBhMC6toRNqjLZ5+/zdKl+ze47z8OUyUy7d3PbYqO4N z9t5DZqbLXd/bIWM63CPxoANWKT5pmtbQy4qUc7O4evAwOPeObNwfnbxJoq3Y+Za6ZjMMu GmJW3Az/a0Wgk0kMDZu9/gp7tp65IU1qOt6ElSQzcFu3clYv0biJ7OdBY+Ao2Oobh92QTs 7BUdd5zpRalunEtNiClceEh3P6dPOYw/pfx1Vmxyc7LHXrbI52Vd82Tj+7ibKg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1691939078; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=67wOu/askamgNgaMWz6ATjabCYrlBnc8iy9pPrPhRdo=; b=vFjSwj+RyWyOIfMIFNHtlga/WqwgJIlxBTvo2edjssPF9NWzlKwQMC+/4hcNNw+6LVXEVC 3Fqk49Buml2IP3DQ== To: "Zhang, Rui" , "linux-kernel@vger.kernel.org" Cc: "Gross, Jurgen" , "mikelley@microsoft.com" , "arjan@linux.intel.com" , "x86@kernel.org" , "thomas.lendacky@amd.com" , "ray.huang@amd.com" , "andrew.cooper3@citrix.com" , "Sivanich, Dimitri" , "wei.liu@kernel.org" Subject: Re: [patch V3 27/40] x86/cpu: Provide a sane leaf 0xb/0x1f parser In-Reply-To: <87350ogh7j.ffs@tglx> References: <20230802101635.459108805@linutronix.de> <20230802101934.258937135@linutronix.de> <8e5bbbc91ff9f74244efe916a4113999abc52213.camel@intel.com> <87350ogh7j.ffs@tglx> Date: Sun, 13 Aug 2023 17:04:37 +0200 Message-ID: <87ttt3f0fu.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Aug 12 2023 at 22:04, Thomas Gleixner wrote: > On Sat, Aug 12 2023 at 08:21, Rui Zhang wrote: >> With this, we can guarantee that all the available topology information >> are always valid, even when running on future platforms. > > I know that it can be made work, but is it worth the extra effort? I > don't think so. So I thought more about it. For intermediate levels, i.e. something which is squeezed between two existing levels, this works by some definition of works. I.e. the example where we have UBER_TILE between TILE and DIE, then we'd set and propagate the UBER_TILE entry into the DIE slot and then overwrite it again, if there is a DIE entry too. Where it becomes interesting is when the unknown level is past DIEGRP, e.g. DIEGRP_CONGLOMORATE then we'd need to overwrite the DIEGRP level, right? It can be done, but I don't know whether it buys us much for the purely theoretical case of new levels added. Thanks, tglx