From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id OOt2FVR53mOQ0SkAWB0awg (envelope-from ) for ; Sat, 04 Feb 2023 10:27:16 -0500 Received: by simark.ca (Postfix, from userid 112) id 538F21E128; Sat, 4 Feb 2023 10:27:16 -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=EFkfHECj; 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=-8.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, URIBL_BLOCKED autolearn=unavailable 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 105111E0D3 for ; Sat, 4 Feb 2023 10:27:16 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 2105F3858431 for ; Sat, 4 Feb 2023 15:27:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2105F3858431 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1675524435; bh=ZvmonPSSy6hV3O739VZmvLfXmPCjpXHDc1yoOIQsXhc=; h=References:To:Cc:Subject:In-reply-to:Date:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=EFkfHECjzFSvt7KqxUFWok1DE6wxTfddmMf8KyeOy9DsTlkzyDsmhF+RwS2KrYlhn 6l83IRXf9rPzno/H8ys5E3cxs6PkPJl0ZWf5Bq91p1gfIob9oOd44GGMhmz90uyoRH 2WqpuvyEZAGXk85p9T+BQLVv4iMcSeicfImnLmaA= Received: from mail-oo1-xc2b.google.com (mail-oo1-xc2b.google.com [IPv6:2607:f8b0:4864:20::c2b]) by sourceware.org (Postfix) with ESMTPS id 490B83858C52 for ; Sat, 4 Feb 2023 15:26:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 490B83858C52 Received: by mail-oo1-xc2b.google.com with SMTP id z25-20020a4ad1b9000000b00517affa07c0so764832oor.7 for ; Sat, 04 Feb 2023 07:26:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:message-id:date:in-reply-to:subject:cc:to:from :user-agent:references:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=ZvmonPSSy6hV3O739VZmvLfXmPCjpXHDc1yoOIQsXhc=; b=iIU66AmhEuS85TJHQiQkOQ+JHtlEE5qVNnZAIaonQ5BMh0IAeanYsQdwbdOEkJxDRJ IvuHUKIfi3XXIpUUhb+jcURSjnAK2r7ER4IjV+z0RpYhDlYVX5vrFISsWC9ezJQMehBi BkeHlAMRhw4x2KZtQuLqk2d32Ociqq7S1FcF3f4zQjiUJ2PqMEdcgIGpghI/Zf+r3t/Z pO+H+5k8b4lzrGdBRTbWzkuH4gRFlDe1hroswwxb3+rsP900dYeBK50sS932MY2Oh0ax DlkCbeHPStW33VQ0SgNSsbm3W6Tcw1NS2E3fIs7mw0xpyjSbop0YOgzs2oAYTh+qmK5r PNcA== X-Gm-Message-State: AO0yUKVRhIBx5qApUo+rBHHpfy5Xbsqmneb2ujzZ9mX6PnC92xo+B+RK M/6MTFN2PFa7f5GweRxw1rX7hw== X-Google-Smtp-Source: AK7set/VhgP88/0WcpZoKPN3X/H39yg9oXnNkhroewsm1AyjID4C+xlMlECF6NMyWAraAYZb7PPUdw== X-Received: by 2002:a4a:49ca:0:b0:51a:7265:5055 with SMTP id z193-20020a4a49ca000000b0051a72655055mr787207ooa.0.1675524414523; Sat, 04 Feb 2023 07:26:54 -0800 (PST) Received: from localhost ([189.100.172.221]) by smtp.gmail.com with ESMTPSA id v8-20020a4aa408000000b005178a98b6d2sm2121529ool.30.2023.02.04.07.26.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 04 Feb 2023 07:26:54 -0800 (PST) References: <20230130044518.3322695-1-thiago.bauermann@linaro.org> <20230130044518.3322695-5-thiago.bauermann@linaro.org> <87pmattzjw.fsf@redhat.com> <7970ac03-1123-d5f6-7b17-808832d43be6@simark.ca> <9a85e2fe-078a-e2ee-7e49-53fe0ceef492@arm.com> <87y1pgaib6.fsf@linaro.org> <871qn79zqk.fsf@linaro.org> User-agent: mu4e 1.8.13; emacs 28.2 To: Luis Machado Cc: Simon Marchi , Andrew Burgess , Thiago Jung Bauermann via Gdb-patches Subject: Re: [PATCH v3 4/8] gdbserver/linux-aarch64: When thread stops, update its target description In-reply-to: Date: Sat, 04 Feb 2023 15:26:50 +0000 Message-ID: <87h6w1moxx.fsf@linaro.org> MIME-Version: 1.0 Content-Type: text/plain 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: Thiago Jung Bauermann via Gdb-patches Reply-To: Thiago Jung Bauermann Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" Luis Machado writes: > On 2/3/23 03:47, Thiago Jung Bauermann wrote: >> Simon Marchi writes: >>> On 2/1/23 21:54, Thiago Jung Bauermann wrote: >>>> Luis Machado writes: >>>>> Moving towards thread-specific target descriptions/gdbarch would >>>>> be a positive thing given the SVE precedent. The process-wide >>>>> target description/gdbarch no longer reflects the correct settings >>>>> for each thread on AArch64's with SVE support. >>>> >>>> In the first version of these patches I removed the process-wide target >>>> description and moved it to thread_info, but it was a big patch that >>>> touched many targets. I can bring it back if you think it's worth it. >>> >>> At least for the register description, if we decide it's now a >>> per-thread thing, what does it mean to have a process-wide description >>> anyway? I think it would make sense to get rid of it, that could help >>> confirm our model works (and it would remove the chance of using the >>> wrong tdesc by mistake for a thread that has its own tdesc). It's >>> probably something that can be done incrementally though. >> >> Would it be done incrementally by keeping process_info->tdesc but >> changing each target in turn to use thread_info->tdesc and ignore the >> process_info one? > > Given only AArch64 has this requirement at the moment, it may be > easier to leave the process-wide tdesc up until the point we can > safely/easily switch to thread-specific ones. > > After that, AArch64 will have potentially distinct thread tdescs while > other architectures will have threads sharing the same tdesc. Ok, sounds good. Thanks for the clarification! -- Thiago