On Thu, 2010-01-21 at 15:47 +1300, Michael Neuling wrote:
> > powerpc: Extended ptrace interface
> > +static long ppc_set_hwdebug(struct task_struct *child,
> > + struct ppc_hw_breakpoint *bp_info)
> > +{
> > + /*
> > + * We currently support one data breakpoint
> > + */
> > + if (((bp_info->trigger_type & PPC_BREAKPOINT_TRIGGER_RW) == 0) ||
> > + ((bp_info->trigger_type & ~PPC_BREAKPOINT_TRIGGER_RW) != 0) ||
> > + (bp_info->trigger_type != PPC_BREAKPOINT_TRIGGER_WRITE) ||
> > + (bp_info->addr_mode != PPC_BREAKPOINT_MODE_EXACT) ||
> > + (bp_info->condition_mode != PPC_BREAKPOINT_CONDITION_NONE))
> > + return -EINVAL;
> > +
> > + if (child->thread.dabr)
> > + return -ENOSPC;
> > +
> > + if ((unsigned long)bp_info->addr >= TASK_SIZE)
> > + return -EIO;
> > +
> > + child->thread.dabr = (unsigned long)bp_info->addr;
> > +#ifdef CONFIG_BOOKE
>
> Do we want to add these CONFIG_BOOKE into a ppc_md call, so different
> CPU typs can have different setups? I could see other CPUs might need
> to do different stuff here and we end up in #ifdef chaos
Actually, I don't think we need that level of indirection just now. If
there's ever a need for more ifdef's then ok, but the BookE debug
facility is somewhat architected so I wouldn't expect that much new
stuff.
Cheers,
Ben.
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
