From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: John Linn <John.Linn@xilinx.com>
Cc: linuxppc-dev@ozlabs.org, hollisb@us.ibm.com,
Tirumala Reddy Marri <tmarri@amcc.com>
Subject: Re: Question about DBCR0 initialization for 440
Date: Fri, 17 Apr 2009 13:22:37 -0400 [thread overview]
Message-ID: <625fc13d0904171022u4d7d5d8cve0ccfb74cc31f554@mail.gmail.com> (raw)
In-Reply-To: <20090417154628.43F859D0055@mail178-wa4.bigfish.com>
On Fri, Apr 17, 2009 at 11:46 AM, John Linn <John.Linn@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
next prev parent reply other threads:[~2009-04-17 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 20:33 Question about DBCR0 initialization for 440 John Linn
2009-04-15 16:24 ` Tirumala Reddy Marri
2009-04-17 15:46 ` John Linn
2009-04-17 17:22 ` Josh Boyer [this message]
2009-04-17 18:07 ` Hollis Blanchard
2009-04-17 19:04 ` Benjamin Herrenschmidt
2009-04-17 19:10 ` Grant Likely
2009-04-17 20:30 ` John Linn
2009-04-17 20:35 ` Josh Boyer
2009-04-17 20:41 ` John Linn
2009-04-17 20:54 ` Josh Boyer
2009-04-17 20:50 ` Hollis Blanchard
2009-04-17 20:57 ` John Linn
2009-04-17 18:57 ` Grant Likely
2009-04-17 18:58 ` John Linn
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=625fc13d0904171022u4d7d5d8cve0ccfb74cc31f554@mail.gmail.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=John.Linn@xilinx.com \
--cc=hollisb@us.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=tmarri@amcc.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;
as well as URLs for NNTP newsgroup(s).