Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "S?rgio Durigan J?nior" <sergiodj@linux.vnet.ibm.com>,
	        gdb-patches@sourceware.org,
	Luis Machado <luisgpm@linux.vnet.ibm.com>,
	        Matt Tyrlik <tyrlik@us.ibm.com>
Subject: Re: [PATCH 0/2] Support the new PPC476 processor
Date: Thu, 17 Dec 2009 14:19:00 -0000	[thread overview]
Message-ID: <200912171218.33964.bauerman@br.ibm.com> (raw)
In-Reply-To: <20091217044212.GB2788@adacore.com>

On Thu 17 Dec 2009 02:42:12 Joel Brobecker wrote:
> I'm very excited to see hardware-accelerated condition evaluation.
> I'll take a look at the patches for sure.

Great!

> Regarding the need for very recent kernel headers, it might be an issue.
> I assume the missing pieces are for the special kinds of watchpoints and
> breakpoints. Is there a way to disable just this code if the kernel
> is not recent enough?
 
We do intend that GDB keeps compiling and working as before when the kernel is 
not recent enough. But then none of the new features this patch adds will be 
available. The current ptrace interface for BookE debug registers
is an ugly hack, and GDB already does everything that can be done with it, 
namely support just one hardware watchpoint, and no hardware breakpoint.

That is because the current ptrace interface was designed for server Power 
processors, which only have one hardware watchpoint anyway.

By the way, the kernel patch implementing the new interface used by this
patch series is here:

http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-December/078805.html
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


  reply	other threads:[~2009-12-17 14:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 20:48 Sérgio Durigan Júnior
2009-12-17  4:42 ` Joel Brobecker
2009-12-17 14:19   ` Thiago Jung Bauermann [this message]
2009-12-17 16:15   ` Sérgio Durigan Júnior
2009-12-18 10:19 ` Eli Zaretskii
2009-12-20 12:33   ` Joel Brobecker
2009-12-30  3:13   ` Thiago Jung Bauermann
2009-12-30 20:43     ` Eli Zaretskii
2009-12-30 22:15     ` Daniel Jacobowitz
2009-12-31  4:05       ` Eli Zaretskii
2009-12-31 16:28         ` Daniel Jacobowitz
2009-12-31 16:50           ` Pedro Alves
2009-12-20 13:16 ` Joel Brobecker
2009-12-20 15:09   ` Sérgio Durigan Júnior
2009-12-20 18:24     ` Joel Brobecker
2009-12-21 12:54       ` Thiago Jung Bauermann

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=200912171218.33964.bauerman@br.ibm.com \
    --to=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.com \
    --cc=sergiodj@linux.vnet.ibm.com \
    --cc=tyrlik@us.ibm.com \
    /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