linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Edson Seabra <edson.seabra@cyclades.com>,
	linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: BDI and 85xx
Date: Mon, 7 Nov 2005 12:17:46 -0500	[thread overview]
Message-ID: <a4ca39fa7ebdefb0aed21af16f5d20c4@embeddededge.com> (raw)
In-Reply-To: <20051107112424.GE15522@logos.cnet>


On Nov 7, 2005, at 6:24 AM, Marcelo Tosatti wrote:

> Edson had to patch this in to get BDI to work on 85xx with 2.6.14.

How about we just change MSR_KERNEL and MSR_USER
in the include file #define instead of all of this run-time code?
Or, change the code so it preserves DE in general, so we don't
need a special kernel configuration just for the BDI?

The original reason I did the BDI_SWITCH was due to the
overhead of tracking user PTE switches in the context switch
code.  I don't like the way this has been overloaded to mean
"BDI general operation."  We should be able to attach a BDI2000
to any kernel configuration and always get kernel debugging
capability.  The BDI_SWITCH was to enable the extra feature
(with some overhead) of debugging into user applications,
it never should have affected any kernel debug operation.

It's unfortunate that Book-E is such a PITA for debuggers,
but let's please find a better way of using these features.
Separate kernel configurations to enable hardware
debugging isn't acceptable.

Thanks.

	-- Dan

      reply	other threads:[~2005-11-07 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07 11:24 BDI and 85xx Marcelo Tosatti
2005-11-07 17:17 ` Dan Malek [this message]

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=a4ca39fa7ebdefb0aed21af16f5d20c4@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=edson.seabra@cyclades.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=marcelo.tosatti@cyclades.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).