From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id c867MF5YYWm1fTcAWB0awg (envelope-from ) for ; Fri, 09 Jan 2026 14:34:54 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simark.ca; s=mail; t=1767987294; bh=L6u9OCvtlj+Kk3DedFE6Q28NwC1C0UOuahMAghOZXyQ=; h=Date:Subject:To:References:From:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=seieN4V9zt0VLRlg99k4wp2oboAAt1l34ZDDzRN4kKcayJrKlw4T5WLpbz4DNHx9M 2QyOc8y76n0ITd466m/pGuhCh4KUMirw7HxQXWCALU8B68uTg8DM3cPA5fykMgObx2 qA0HkeCkFgdunUrgVbXxLA3Dp26BsVPVTkZ85Qo0= Received: by simark.ca (Postfix, from userid 112) id 9B5721E0B6; Fri, 09 Jan 2026 14:34:54 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_VALIDITY_CERTIFIED_BLOCKED, RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED autolearn=ham autolearn_force=no version=4.0.1 Authentication-Results: simark.ca; dkim=pass (1024-bit key; unprotected) header.d=simark.ca header.i=@simark.ca header.a=rsa-sha256 header.s=mail header.b=qd6yo43R; dkim-atps=neutral Received: from vm01.sourceware.org (vm01.sourceware.org [38.145.34.32]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 1001E1E08D for ; Fri, 09 Jan 2026 14:34:54 -0500 (EST) Received: from vm01.sourceware.org (localhost [127.0.0.1]) by sourceware.org (Postfix) with ESMTP id 9DFA54BA2E23 for ; Fri, 9 Jan 2026 19:34:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9DFA54BA2E23 Authentication-Results: sourceware.org; dkim=pass (1024-bit key, unprotected) header.d=simark.ca header.i=@simark.ca header.a=rsa-sha256 header.s=mail header.b=qd6yo43R Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id 2B6234BA2E04 for ; Fri, 9 Jan 2026 19:34:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2B6234BA2E04 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=simark.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=simark.ca ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 2B6234BA2E04 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=158.69.221.121 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1767987269; cv=none; b=lEGLDw45nCvouaZ6E6gzdxqbLcE51E+tMVwCQRmF2AXzZ8JAs7XDwLqFI+mbpI32pHwyEib9CeOQ4H4tQVRLQj4mL7szQ370DnvKwGI8zlXdSLd0wlxezymTvUFZqbARPh0OCRx1TzDBHqPYFk4oDw0yu6/DZToxtHmf2D2VbgU= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1767987269; c=relaxed/simple; bh=L6u9OCvtlj+Kk3DedFE6Q28NwC1C0UOuahMAghOZXyQ=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=trxvgVR7SNLPcM0v/wXwkj5vijgjW1WX/sZvQswxXKLBwI0ptFj20O3CvxBV5S3vPg0pPwtpZqYFnTTaS/U836HKPvkPXv0LkezFsE2yY9LHYJ7SLumg8zpyxayrw8XivymEQeDooWRSk/T9akBa02KhheVlnduMJuBYMMmUgxo= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2B6234BA2E04 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simark.ca; s=mail; t=1767987268; bh=L6u9OCvtlj+Kk3DedFE6Q28NwC1C0UOuahMAghOZXyQ=; h=Date:Subject:To:References:From:In-Reply-To:From; b=qd6yo43R3BIEAVBFg3wUpEzpRbDE+e/5/PLUmK8s/UWQNHG1M2oi4QlHSzvzSVwmp h49ff0cmdJFKOxZFNge/ohKtFw0AcH/wd3nbfwVH01PMI2WmPCeKLwt1HfQctSO/qi yW5Y1aOrqOKhMN1fwErqlNxYJaNfdLoOFXgZZbDA= Received: by simark.ca (Postfix) id 8C9531E08D; Fri, 09 Jan 2026 14:34:28 -0500 (EST) Message-ID: <7d6bbfca-28d2-4fcc-af6b-f51119fe978c@simark.ca> Date: Fri, 9 Jan 2026 14:34:28 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v3 05/44] gdb, gdbserver, gdbsupport: add 'device' tag to XML target description To: "Aktemur, Tankut Baris" , "gdb-patches@sourceware.org" , "Metzger, Markus T" References: <20250801-upstream-intelgt-mvp-v3-0-59ce0f87075b@intel.com> <20250801-upstream-intelgt-mvp-v3-5-59ce0f87075b@intel.com> <83d2ce00-2c75-4037-a61c-401a4839aecb@simark.ca> Content-Language: fr From: Simon Marchi In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces~public-inbox=simark.ca@sourceware.org On 1/9/26 2:12 PM, Aktemur, Tankut Baris wrote: >> In our downstream debugger, we have an "info devices" command that lists >> the properties of the devices as obtained from this XML information. >> vendor_id and target_id are necessary, like you say, so that the target >> description can validate it supports that device and can do device- >> specific >> work, if necessary. Other information is there for informing the user >> in the >> "info devices" command. The pci_slot is useful, because if the system >> has >> multiple identical devices, pci_slot becomes the only distinguishing >> property. >> Although it is not a built-in property of the device (like number of >> cores), >> it is still physical&static -- you wouldn’t/couldn't change the pci_slot >> of a device during the debug session. In that sense, it's a bit in the >> grey >> area. >> >> Is pci_slot the only field that concerns you? We can remove it from the >> patch >> and consider later. > > Just pinging for this question. I think that pci_slot is the only one, yes. I view a target description or a gdbarch as describing a "class" of computation unit (CPU/GPU/whatever), not one specific instance of it. If you add pci_slot, then the target description / gdbarch now describes one specific instance, instead of the whole class. That's why I tend to think that "devices" should perhaps be a concept of its own. Two identical devices would share ("point to") the same target description. We just need to agree on what a target description fundamentally is, I haven't thought about it more than that. Simon