public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Florian Weimer <fweimer@redhat.com>, gdb@sourceware.org
Cc: Dmitry Belyavskiy <dbelyavs@redhat.com>
Subject: Re: Hardware watchpoints on GNU/Linux AArch64
Date: Thu, 5 Jan 2023 14:17:56 +0000	[thread overview]
Message-ID: <2cb0ccd4-35a7-a216-383a-18d255c985cb@arm.com> (raw)
In-Reply-To: <87tu18naqq.fsf@oldenburg.str.redhat.com>

Hi,

On 1/2/23 16:48, 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.
> 
> 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
> 

Apologies, I was out for a few days during end of year. Hardware watchpoints should work
on AArch64/Linux. They should also work on system QEMU (though there might be differences in behavior).

I'm not sure about KVM though.

      parent reply	other threads:[~2023-01-05 14:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-02 16:48 Florian Weimer
2023-01-02 17:08 ` Andreas Schwab
2023-01-02 17:22   ` Florian Weimer
2023-01-02 17:28 ` Andrew Pinski
2023-01-02 17:39   ` Andrew Pinski
2023-01-02 18:10     ` Andrew Pinski
2023-01-02 17:44   ` Florian Weimer
2023-01-02 17:59     ` Florian Weimer
2023-01-05 14:17 ` Luis Machado [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2cb0ccd4-35a7-a216-383a-18d255c985cb@arm.com \
    --to=luis.machado@arm.com \
    --cc=dbelyavs@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).