From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>, Paul Mackerras <paulus@samba.org>
Subject: Re: [RFC] 4xx hardware watchpoint support
Date: Mon, 21 Jul 2008 13:36:33 -0300 [thread overview]
Message-ID: <1216658194.5727.36.camel@gargoyle> (raw)
In-Reply-To: <20080719093752.5aada45c@zod.rchland.ibm.com>
> This doesn't look right for how it's coded. This would be the
> CONFIG_4xx || CONFIG_BOOKE case, but CONFIG_4xx includes PowerPC 405.
> That has a different bit layout among the DBCR registers. Namely, on
> 405 you would be clearing the TDE and IAC1 events because the DAC
> events are in DBCR1, not DBCR0.
Maybe guarding the 405-specific parts in a separate "#if
defined(CONFIG_40x)" block will do?
Do you think it's worth to support this facility on 405's processors? If
so, i'll gladly work on a solution to it.
Regards,
Luis
next prev parent reply other threads:[~2008-07-21 16:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 17:39 [RFC] 4xx hardware watchpoint support Luis Machado
2008-05-21 21:16 ` Kumar Gala
2008-05-21 21:54 ` Luis Machado
2008-05-22 3:51 ` Paul Mackerras
2008-05-22 6:46 ` Roland McGrath
2008-05-23 18:12 ` Luis Machado
2008-05-27 21:34 ` Roland McGrath
2008-05-23 18:06 ` Luis Machado
2008-06-20 20:14 ` Luis Machado
2008-06-30 19:16 ` Luis Machado
2008-07-19 13:37 ` Josh Boyer
2008-07-21 16:36 ` Luis Machado [this message]
2008-07-21 17:05 ` Josh Boyer
2008-07-23 1:47 ` Luis Machado
2008-07-23 12:51 ` Kumar Gala
2008-07-23 14:23 ` Christoph Hellwig
2008-07-23 14:42 ` Luis Machado
2008-07-23 15:53 ` Josh Boyer
2008-07-23 16:10 ` Luis Machado
2008-07-25 4:00 ` Benjamin Herrenschmidt
2008-07-25 15:23 ` Kumar Gala
2008-07-25 19:38 ` Kumar Gala
2008-07-25 21:38 ` Benjamin Herrenschmidt
2008-07-25 23:08 ` Josh Boyer
2008-07-25 23:18 ` Benjamin Herrenschmidt
2008-07-25 21:37 ` Benjamin Herrenschmidt
2008-07-25 15:22 ` Kumar Gala
2008-07-23 16:26 ` Kumar Gala
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=1216658194.5727.36.camel@gargoyle \
--to=luisgpm@linux.vnet.ibm.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 NNTP newsgroup(s).