mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "tip-bot2 for Zhenyu Wang" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Zhenyu Wang <zhenyuw@linux.intel.com>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: perf/core] perf/x86/intel/uncore: Use D0:F0 as a default device
Date: Wed, 07 Aug 2024 10:51:37 -0000	[thread overview]
Message-ID: <172302789705.2215.10644876568703251327.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20240731141353.759643-5-kan.liang@linux.intel.com>

The following commit has been merged into the perf/core branch of tip:

Commit-ID:     aaad0e2aa50723969f96b690f72e2f4aefa433f2
Gitweb:        https://git.kernel.org/tip/aaad0e2aa50723969f96b690f72e2f4aefa433f2
Author:        Zhenyu Wang <zhenyuw@linux.intel.com>
AuthorDate:    Wed, 31 Jul 2024 07:13:53 -07:00
Committer:     Peter Zijlstra <peterz@infradead.org>
CommitterDate: Mon, 05 Aug 2024 16:54:46 +02:00

perf/x86/intel/uncore: Use D0:F0 as a default device

Some uncore PMON registers are located in the MMIO space of the Host
Bridge and DRAM Controller device, which is located at D0:F0 for
Tiger Lake and later client generation.

Use D0:F0 as a default device. So it doesn't need to keep adding the
complete Device ID list for each generation anymore.

Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
Link: https://lore.kernel.org/r/20240731141353.759643-5-kan.liang@linux.intel.com
---
 arch/x86/events/intel/uncore_snb.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/arch/x86/events/intel/uncore_snb.c b/arch/x86/events/intel/uncore_snb.c
index f7402bd..3934e1e 100644
--- a/arch/x86/events/intel/uncore_snb.c
+++ b/arch/x86/events/intel/uncore_snb.c
@@ -1504,6 +1504,10 @@ static struct pci_dev *tgl_uncore_get_mc_dev(void)
 		ids++;
 	}
 
+	/* Just try to grab 00:00.0 device */
+	if (!mc_dev)
+		mc_dev = pci_get_domain_bus_and_slot(0, 0, PCI_DEVFN(0, 0));
+
 	return mc_dev;
 }
 

  reply	other threads:[~2024-08-07 10:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 14:13 [PATCH 1/5] perf/x86/intel/uncore: Add Arrow Lake support kan.liang
2024-07-31 14:13 ` [PATCH 2/5] perf/x86/intel/uncore: Factor out common MMIO init and ops functions kan.liang
2024-08-07 10:51   ` [tip: perf/core] " tip-bot2 for Kan Liang
2024-07-31 14:13 ` [PATCH 3/5] perf/x86/intel/uncore: Add Lunar Lake support kan.liang
2024-08-07 10:51   ` [tip: perf/core] " tip-bot2 for Kan Liang
2024-07-31 14:13 ` [PATCH 4/5] perf/x86/intel/uncore: Add LNL uncore iMC freerunning support kan.liang
2024-08-07 10:51   ` [tip: perf/core] " tip-bot2 for Zhenyu Wang
2024-07-31 14:13 ` [PATCH 5/5] perf/x86/intel/uncore: Use D0:F0 as a default device kan.liang
2024-08-07 10:51   ` tip-bot2 for Zhenyu Wang [this message]
2024-08-07 10:51 ` [tip: perf/core] perf/x86/intel/uncore: Add Arrow Lake support tip-bot2 for Kan Liang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=172302789705.2215.10644876568703251327.tip-bot2@tip-bot2 \
    --to=tip-bot2@linutronix.de \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=x86@kernel.org \
    --cc=zhenyuw@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®