Message ID | 20230112200105.733466-1-kan.liang@linux.intel.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:4e01:0:0:0:0:0 with SMTP id p1csp4083016wrt; Thu, 12 Jan 2023 12:12:28 -0800 (PST) X-Google-Smtp-Source: AMrXdXtLRNxLR+r0u4ZTI4UVgEEZS7JV42dS4ZXzdiZoQ7aIa9k88F0TiKCLMhrHYVc832mY1o8Z X-Received: by 2002:a05:6402:449a:b0:47d:88f3:1165 with SMTP id er26-20020a056402449a00b0047d88f31165mr74542379edb.12.1673554348643; Thu, 12 Jan 2023 12:12:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673554348; cv=none; d=google.com; s=arc-20160816; b=v1D7RubhzxT88MROxZZXoD+7acBlwR8xEiRGtQQFc6mN6PkHeoo3fKyIUesMgltBUu +HobX5ak6iebhOc/vRaUs7xv7WOku85t2tMnSJgJ9vfPhenRfyQGvpKzdpG6NoEHLG0N vWc//xIP8BItqGh35T9CuH3iMDz5wjP9yB3L6ncUmV0d2HUT/3XCY2CsvPWTJyn94wzq einsv4Zh45jPX+L8C/a9rCKepMm5Eam+4XUcCGygr88ZUZTUHPn0XLoBTQv7Gqtwk0xl QDahSJutU95BPIpev3SzL5pf020RTDfpFoKSfbjqtC75ZtQBb1M+KvhMQDvnBd2wbKXw yq7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=VaU7gUH8prwgX97NtYi17OdI/y7serxbcbwpUf80Tn8=; b=mVveVOHphqm/TuT3VAj7SSjSHpxM5W6sqD2pSg533Ba5J2ei8ie1R9gxyt3RTA7sem CPZr000tlYhCMkUcnHEld2bU1z6yLkubwnxhDVKGnVsAh3BEMp8IrvBO5/7uHaX6VpAU NyIctwUyFImbgudMnQQNnRxYS4dtDKkBm6HS3stfFjmT34ucf0Pfd8KtyHSjvWLdJOYr mjofe/eXQtAVS7USBolIK/CQjI6y0GrcvZU+hRL3Bqg+V25+ZpwgtZ/VQVp0gydt0fwx nEzsRczuIhR/aJDr9qH2gFWqcVXmz48Ww7XzNjRU9OTizXEV0vbIoCDeg+uy6A1pKp6p +8lA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=TYwqzNh5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id n13-20020a05640205cd00b0048024f3aec4si9876863edx.617.2023.01.12.12.12.03; Thu, 12 Jan 2023 12:12:28 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=TYwqzNh5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233877AbjALUHs (ORCPT <rfc822;zhuangel570@gmail.com> + 99 others); Thu, 12 Jan 2023 15:07:48 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49934 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241657AbjALUEf (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Thu, 12 Jan 2023 15:04:35 -0500 Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 66FF519C29 for <linux-kernel@vger.kernel.org>; Thu, 12 Jan 2023 12:01:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1673553715; x=1705089715; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=CRC1QpMRvg+SgNUKD7+JhmJV8K8WczePzSImvqnWffY=; b=TYwqzNh5Qc+JbAbvYCeqFsW9H613MyoS+lYRHJsyB8hxTlHeF8pPbp1x WjLAHIpvhq9DMJXM1ozLdihakSBpPMuFQ6dIGMshD9EaEVXq9lyI3thWD kWNyiC0BtbbV9lUO4d+Sj1IkUjNREM53KB318FPOiFivhomWxcjXpj68B 14/bHo3fdPnHAyGAhQ7Lo/T5dPChb9IPznGR40t6l4RlP4leXJCmcO35i NRV/VcWZX3LSslSVTsjFz4xax7e1FxP6mjMw7Ezc9JsHIhtF9JHDwlP3v yVw0Wpui87IXZ7FGgNsj9QdnKr7FB6Cd61Oul9hW/G6gWklqMz7pK2Ho6 g==; X-IronPort-AV: E=McAfee;i="6500,9779,10588"; a="325867090" X-IronPort-AV: E=Sophos;i="5.97,211,1669104000"; d="scan'208";a="325867090" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Jan 2023 12:01:29 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10588"; a="657959922" X-IronPort-AV: E=Sophos;i="5.97,211,1669104000"; d="scan'208";a="657959922" Received: from kanliang-dev.jf.intel.com ([10.165.154.102]) by orsmga002.jf.intel.com with ESMTP; 12 Jan 2023 12:01:29 -0800 From: kan.liang@linux.intel.com To: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org Cc: steve.wahl@hpe.com, alexander.antonov@linux.intel.com, ak@linux.intel.com, eranian@google.com, namhyung@kernel.org, Kan Liang <kan.liang@linux.intel.com> Subject: [PATCH RESEND 0/5] Fix UPI uncore issue on SPR Date: Thu, 12 Jan 2023 12:01:00 -0800 Message-Id: <20230112200105.733466-1-kan.liang@linux.intel.com> X-Mailer: git-send-email 2.35.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1754848925050096547?= X-GMAIL-MSGID: =?utf-8?q?1754848925050096547?= |
Series |
Fix UPI uncore issue on SPR
|
|
Message
Liang, Kan
Jan. 12, 2023, 8:01 p.m. UTC
From: Kan Liang <kan.liang@linux.intel.com>
The discovery table of UPI on SPR MCC is broken. The patch series is
to mitigate the issue by providing a hardcode pre-defined table.
The broken discovery table can trigger a kernel warning message, which
is overkilled. The patch series also refine the error handling code.
Kan Liang (5):
perf/x86/uncore: Factor out uncore_device_to_die()
perf/x86/uncore: Fix potential NULL pointer in uncore_get_alias_name
perf/x86/uncore: Ignore broken units in discovery table
perf/x86/uncore: Add a quirk for UPI on SPR
perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
arch/x86/events/intel/uncore.c | 34 ++++-
arch/x86/events/intel/uncore.h | 4 +
arch/x86/events/intel/uncore_discovery.c | 60 ++++++---
arch/x86/events/intel/uncore_discovery.h | 14 +-
arch/x86/events/intel/uncore_snbep.c | 158 ++++++++++++++++++-----
5 files changed, 210 insertions(+), 60 deletions(-)
Comments
Hi Peter & Ingo, Gentle Ping. Please let me know if you have any comments on the patch set. Thanks Kan On 2023-01-12 3:01 p.m., kan.liang@linux.intel.com wrote: > From: Kan Liang <kan.liang@linux.intel.com> > > The discovery table of UPI on SPR MCC is broken. The patch series is > to mitigate the issue by providing a hardcode pre-defined table. > > The broken discovery table can trigger a kernel warning message, which > is overkilled. The patch series also refine the error handling code. > > Kan Liang (5): > perf/x86/uncore: Factor out uncore_device_to_die() > perf/x86/uncore: Fix potential NULL pointer in uncore_get_alias_name > perf/x86/uncore: Ignore broken units in discovery table > perf/x86/uncore: Add a quirk for UPI on SPR > perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table > > arch/x86/events/intel/uncore.c | 34 ++++- > arch/x86/events/intel/uncore.h | 4 + > arch/x86/events/intel/uncore_discovery.c | 60 ++++++--- > arch/x86/events/intel/uncore_discovery.h | 14 +- > arch/x86/events/intel/uncore_snbep.c | 158 ++++++++++++++++++----- > 5 files changed, 210 insertions(+), 60 deletions(-) >
On Thu, 19 Jan 2023, Liang, Kan wrote: > Hi Peter & Ingo, > > Gentle Ping. Please let me know if you have any comments on the patch set. > > Thanks > Kan > > On 2023-01-12 3:01 p.m., kan.liang@linux.intel.com wrote: > > From: Kan Liang <kan.liang@linux.intel.com> > > > > The discovery table of UPI on SPR MCC is broken. The patch series is > > to mitigate the issue by providing a hardcode pre-defined table. > > > > The broken discovery table can trigger a kernel warning message, which > > is overkilled. The patch series also refine the error handling code. > > > > Kan Liang (5): > > perf/x86/uncore: Factor out uncore_device_to_die() > > perf/x86/uncore: Fix potential NULL pointer in uncore_get_alias_name > > perf/x86/uncore: Ignore broken units in discovery table > > perf/x86/uncore: Add a quirk for UPI on SPR > > perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table For the series, Tested-by: Michael Petlan <mpetlan@redhat.com> > > > > arch/x86/events/intel/uncore.c | 34 ++++- > > arch/x86/events/intel/uncore.h | 4 + > > arch/x86/events/intel/uncore_discovery.c | 60 ++++++--- > > arch/x86/events/intel/uncore_discovery.h | 14 +- > > arch/x86/events/intel/uncore_snbep.c | 158 ++++++++++++++++++----- > > 5 files changed, 210 insertions(+), 60 deletions(-) > > > >
Hello all, gentle ping #2... How does it look with the patchset acceptance? Is everything OK? Does it need any additional testing/etc.? When could the patches be expected to land in Linus' tree? Is it within v6.2 scope? Thank you. Michael On Thu, 19 Jan 2023, Liang, Kan wrote: > Hi Peter & Ingo, > > Gentle Ping. Please let me know if you have any comments on the patch set. > > Thanks > Kan > > On 2023-01-12 3:01 p.m., kan.liang@linux.intel.com wrote: > > From: Kan Liang <kan.liang@linux.intel.com> > > > > The discovery table of UPI on SPR MCC is broken. The patch series is > > to mitigate the issue by providing a hardcode pre-defined table. > > > > The broken discovery table can trigger a kernel warning message, which > > is overkilled. The patch series also refine the error handling code. > > > > Kan Liang (5): > > perf/x86/uncore: Factor out uncore_device_to_die() > > perf/x86/uncore: Fix potential NULL pointer in uncore_get_alias_name > > perf/x86/uncore: Ignore broken units in discovery table > > perf/x86/uncore: Add a quirk for UPI on SPR > > perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table > > > > arch/x86/events/intel/uncore.c | 34 ++++- > > arch/x86/events/intel/uncore.h | 4 + > > arch/x86/events/intel/uncore_discovery.c | 60 ++++++--- > > arch/x86/events/intel/uncore_discovery.h | 14 +- > > arch/x86/events/intel/uncore_snbep.c | 158 ++++++++++++++++++----- > > 5 files changed, 210 insertions(+), 60 deletions(-) > > > >
I reviewed this patch series, applied it to a kernel tree, and tested it on two larger (12+ socket) systems, did not notice any adverse affects. So I believe it's appropriate to add both of these tags: Tested-by: Steve Wahl <steve.wahl@hpe.com> Reviewed-by: Steve Wahl <steve.wahl@hpe.com> --> Steve On Thu, Jan 12, 2023 at 12:01:00PM -0800, kan.liang@linux.intel.com wrote: > From: Kan Liang <kan.liang@linux.intel.com> > > The discovery table of UPI on SPR MCC is broken. The patch series is > to mitigate the issue by providing a hardcode pre-defined table. > > The broken discovery table can trigger a kernel warning message, which > is overkilled. The patch series also refine the error handling code. > > Kan Liang (5): > perf/x86/uncore: Factor out uncore_device_to_die() > perf/x86/uncore: Fix potential NULL pointer in uncore_get_alias_name > perf/x86/uncore: Ignore broken units in discovery table > perf/x86/uncore: Add a quirk for UPI on SPR > perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table > > arch/x86/events/intel/uncore.c | 34 ++++- > arch/x86/events/intel/uncore.h | 4 + > arch/x86/events/intel/uncore_discovery.c | 60 ++++++--- > arch/x86/events/intel/uncore_discovery.h | 14 +- > arch/x86/events/intel/uncore_snbep.c | 158 ++++++++++++++++++----- > 5 files changed, 210 insertions(+), 60 deletions(-) > > -- > 2.35.1 >