From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id xt/UASYLs2PBIg4AWB0awg (envelope-from ) for ; Mon, 02 Jan 2023 11:49:42 -0500 Received: by simark.ca (Postfix, from userid 112) id F0DA71E222; Mon, 2 Jan 2023 11:49:41 -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=OfYtvXsR; 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=-7.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.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 AB5C81E0D3 for ; Mon, 2 Jan 2023 11:49:41 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 19761385842C for ; Mon, 2 Jan 2023 16:49:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 19761385842C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1672678181; bh=0XgKfqMgbmuVmha6fB1+8Wn2G/gN+2lcgtEnKGza9mg=; h=To:Cc:Subject:Date:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:From:Reply-To:From; b=OfYtvXsRYuavRMK6Vr1Z+Zovp+cImhExe5/oM0paiX/zAa75YyuQUJaIQjaXBOHoS djMPXOlECr8aQMXI0pm5WZ0/vM8cILPdBW6qgbwI7PEr+WOpRln63DGvowF+lzgJ1z YV8xL9cZcivOrnXkupVl9b/ABliUx52FdoKaKnZU= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 01C3D3858D39 for ; Mon, 2 Jan 2023 16:49:14 +0000 (GMT) Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-42-lFNJaEOvP16xvFEYZQHRGA-1; Mon, 02 Jan 2023 11:48:39 -0500 X-MC-Unique: lFNJaEOvP16xvFEYZQHRGA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id A1AC41C02D2D for ; Mon, 2 Jan 2023 16:48:31 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.30]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1A4DB140EBF5; Mon, 2 Jan 2023 16:48:30 +0000 (UTC) To: gdb@sourceware.org Cc: Dmitry Belyavskiy Subject: Hardware watchpoints on GNU/Linux AArch64 Date: Mon, 02 Jan 2023 17:48:29 +0100 Message-ID: <87tu18naqq.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Florian Weimer via Gdb Reply-To: Florian Weimer Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" Running gdb-12.1-10.fc38.aarch64 kernel-6.2.0-0.rc1.20221230gitbff687b3dad6.15.fc38.aarch64 I do not seem to be able to use hardware watchpoints. GDB just logs warnings: warning: Unable to determine the number of hardware watchpoints available. warning: Unable to determine the number of hardware breakpoints available. I see AArch64-specific code in GDB, so this is a bit of a surprise to me. The machine uses virtualization: Architecture: aarch64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 3 On-line CPU(s) list: 0-2 Vendor ID: ARM BIOS Vendor ID: QEMU Model name: Neoverse-N1 BIOS Model name: virt-rhel8.6.0 CPU @ 2.0GHz BIOS CPU family: 1 Model: 1 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 3 Stepping: r3p1 BogoMIPS: 50.00 Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs Is this actually expected to work? Would we have more luck on a bare-metal system? Thanks, Florian