From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id rHj4Hi9X4mOgRiwAWB0awg (envelope-from ) for ; Tue, 07 Feb 2023 08:50:39 -0500 Received: by simark.ca (Postfix, from userid 112) id 70E641E15D; Tue, 7 Feb 2023 08:50:39 -0500 (EST) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=OoWY5n+m; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_MED,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 0852F1E0D3 for ; Tue, 7 Feb 2023 08:50:39 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 1BDC33858C83 for ; Tue, 7 Feb 2023 13:50:37 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1BDC33858C83 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1675777837; bh=AMh5Faevo2g4R+KtA5NsjhGFS0CiZIiLixRzs2f5UiI=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=OoWY5n+m06VOQg63a+imKLPYUXPBkkU4xStlU+l2oEgHAMk54qKUdUuwu8RC8JFJo WGQWu7F74jw2DrJmhmE37HadNhQbu8gOIYlqn0PNjw/SGFVDG7xm5V7FCdFnoLjm5L p/h+0ypfuV4MzmvlevnxK1oAN/9/B3q2DXV2Mi+4= Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id 60CF1385840C for ; Tue, 7 Feb 2023 13:49:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 60CF1385840C Received: from [10.0.0.11] (unknown [217.28.27.60]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id EE92D1E0D3; Tue, 7 Feb 2023 08:49:47 -0500 (EST) Message-ID: <0da46219-6777-165e-92b6-d3df984d284c@simark.ca> Date: Tue, 7 Feb 2023 08:49:47 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [PATCH v3 0/8] gdbserver improvements for AArch64 SVE support To: Pedro Alves , Thiago Jung Bauermann , gdb-patches@sourceware.org References: <20230130044518.3322695-1-thiago.bauermann@linaro.org> <28bdd610-982d-aebb-ebc7-17b6d5fd80ed@palves.net> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Simon Marchi via Gdb-patches Reply-To: Simon Marchi Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" >> Tangentially, I'm wondering if querying qXfer:features:read (mostly >> fetching "target.xml" is going to become thread-sensitive. In other >> words, if GDB set the general thread to a thread with vq == A, gets >> target.xml, then sets the general thread to a thread with vq == B, then >> gets target.xml, is it going to get two different target descriptions? >> I think that it would make sense to do so *. > > I am not so sure about that making sense. > > As target.xml is documented as the main tdesc, it would continue that way, > with "main" meaning the tdesc that the initial thread has when the process > is first started. My interpretation of the work "main" here was "top-level". At least, I suppose that's what the original author meant, because I suppose it was written assuming there's a single target description "tree" per process. So there wouldn't need to be the need to differentiate "main" vs "secondary". Simon