From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id TX3gN0oes2PqJg4AWB0awg (envelope-from ) for ; Mon, 02 Jan 2023 13:11:22 -0500 Received: by simark.ca (Postfix, from userid 112) id DA3F81E222; Mon, 2 Jan 2023 13:11:22 -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=w+CiqBjx; 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=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 86F241E112 for ; Mon, 2 Jan 2023 13:11:22 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 5646B3858434 for ; Mon, 2 Jan 2023 18:11:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5646B3858434 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1672683081; bh=tSuyFgPbDU3RP4XdJ9JBAX9wJHhjH+isnye+U7yjh3w=; h=References:In-Reply-To:Date:Subject:To:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=w+CiqBjx6sWq0NmTVRq8aFpN4u+oHu23ERQ2CWa1o9yr1mBC0JY0pCYhajJKaNZn6 quG+/ytGy+gc1+lwQIBKtkNa94d8WpfID3nXGfP/FpD4u3XCtkbX/pP49yo0fOGG09 HZnR7L/ewJ8kx/oMQtVaMzw2l7z3xygeXIgf1shs= Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) by sourceware.org (Postfix) with ESMTPS id B2CC83858D32 for ; Mon, 2 Jan 2023 18:10:49 +0000 (GMT) Received: by mail-pg1-x531.google.com with SMTP id f3so18731967pgc.2 for ; Mon, 02 Jan 2023 10:10:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tSuyFgPbDU3RP4XdJ9JBAX9wJHhjH+isnye+U7yjh3w=; b=wgckL3MZ4+GEI99fb53TsSW2dbktzbGTXOAdPpfie8IYcqzkpH/I1TsJRp5ANvDHkn axHLhUoxeqNUGCB7esJbswWeUK18MG1Lv8P6fx63T/mMUCWYUxfQc0gq9fjkhtxfgvtM wZKSMuEBM7tAGPH6ZXyr3CJx8z+CaBRjgkt9oVpNJtvX3hZIMtRhuxnhkL94ZWJ2Jxpe TchFWcTXNyR5NGnyerMWEXYfNQRme70bpgJpfwoDgmBoDYN4SKvAvT1zCuLwvhN6FfOM F15W3p8gIPdan+7zJ1j2TYjGA10MvhOcQX93UiEGhDnLuYwib7QLej7u6fXHIlZ1Fnis VQww== X-Gm-Message-State: AFqh2kpJhrBdT5iCWMvxHp6TMRAJ0BKUUFq9WVvCf6kzaIW5tUcSlmL7 dN72WyM/EWYcm9BFlso/wZZDiWWkzIlm6bZ607bEVCccQCA= X-Google-Smtp-Source: AMrXdXskGmsreOBFX3kzxV6LliAlYT3J+W5yUkWwhGxLobpkYOSYkHAogXqcK/pJctGlucjXBGS5MWEnPJg3T192HR4= X-Received: by 2002:a63:751:0:b0:434:7885:6ade with SMTP id 78-20020a630751000000b0043478856ademr2877287pgh.243.1672683048544; Mon, 02 Jan 2023 10:10:48 -0800 (PST) MIME-Version: 1.0 References: <87tu18naqq.fsf@oldenburg.str.redhat.com> In-Reply-To: Date: Mon, 2 Jan 2023 10:10:35 -0800 Message-ID: Subject: Re: Hardware watchpoints on GNU/Linux AArch64 To: Florian Weimer Cc: gdb@sourceware.org, Dmitry Belyavskiy Content-Type: text/plain; charset="UTF-8" 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: Andrew Pinski via Gdb Reply-To: Andrew Pinski Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" On Mon, Jan 2, 2023 at 9:39 AM Andrew Pinski wrote: > > On Mon, Jan 2, 2023 at 9:28 AM Andrew Pinski wrote: > > > > On Mon, Jan 2, 2023 at 8:49 AM Florian Weimer via Gdb > > wrote: > > > > > > 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. > > > > This shows up when the ptrace either fails or ptrace returns an > > unknown value for AARCH64_DEBUG_ARCH value. > > In the boot log there should be a message saying how many HW > > breakpoint and watchpoints there are and what version of the debug > > arch is there. > > The supported values for debug arch are: > > #define AARCH64_DEBUG_ARCH_V8 0x6 > > #define AARCH64_DEBUG_ARCH_V8_1 0x7 > > #define AARCH64_DEBUG_ARCH_V8_2 0x8 > > #define AARCH64_DEBUG_ARCH_V8_4 0x9 > > > > I don't know of any other values that can be reported, especially for > > Neoverse-N1 (which should be 8_2). Neoverse-N2 is 8_4. > > The kernel fills in that field with ptrace via: > u8 debug_monitors_arch(void) > { > return cpuid_feature_extract_unsigned_field(read_sanitised_ftr_reg(SYS_ID_AA64DFR0_EL1), > ID_AA64DFR0_EL1_DebugVer_SHIFT); > } > > So either kvm/qemu is setting that EL1 (system) register incorrectly > or the KVM Invocation didn't turn on HW breakpoints. Or KVM does not > support HW breakpoints yet. Looking KVM sources (arch/arm64/kvm/sys_regs.c) inside the kernel we see: /* Limit debug to ARMv8.0 */ val &= ~ARM64_FEATURE_MASK(ID_AA64DFR0_EL1_DebugVer); val |= FIELD_PREP(ARM64_FEATURE_MASK(ID_AA64DFR0_EL1_DebugVer), 6); Which was added by 94893fc9ad8cd for 5.12 unless this changed post Linux 6.0 . So a value of 6 should be good to go. Thanks, Andrew Pinski > > Thanks, > Andrew > > > > > > Thanks, > > Andrew Pinski > > > > > > > > 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 > > >