Question about DBCR0 initialization for 440

[Grant Likely]

Hey John

We just discussed this on IRC.  Go ahead and generate a patch to
unconditionally turn on DBCR0[IDM] in head_44x.S.  Don't even bother
wrapping it in an #ifdef CONFIG_somthing block.  It should be safe,
but we'll throw it into -next and see if anyone complains.  If it does
cause problems, then it can be reworked to something a wee bit more
conservative.

g.

On Fri, Apr 17, 2009 at 11:22 AM, Josh Boyer <jwboyer at linux.vnet.ibm.com> wrote:
> On Fri, Apr 17, 2009 at 11:46 AM, John Linn <John.Linn at xilinx.com> wrote:
>> Josh, any thoughts on putting this into head_44x.S?
>
> The code in the fsl file looks like the right solution.  I do have an
> odd question though, in that it's hard for the
> kernel to really know if something like a BDI is running.  Namely,
> that config option doesn't cover RiscWatch in an obvious manner.
>
> I also wonder if it's possible to have a host system be setting those
> registers in a guest KVM system so the guest could be debugged with
> gdb...  Hollis, any idea on that?
>
> josh
>



-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.