public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Tom Rini <trini@kernel.crashing.org>,
	"Amit S. Kale" <akale@users.sourceforge.net>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: kgdb: fix kgdbeth compilation and make it init late enough
Date: Tue, 02 Mar 2004 17:05:52 -0800	[thread overview]
Message-ID: <40452F70.1070706@mvista.com> (raw)
In-Reply-To: <20040302223326.GF1225@elf.ucw.cz>

Pavel Machek wrote:
> Hi!
> 
> 
>>>CONFIG_NO_KGDB_CPUS can not be found anywhere in the patches => its
>>>probably not needd any more.
>>
>>I don't know if we can do that.  There's some funky locking stuff done
>>on SMP, which for some reason can't be done to NR_CPUS (or, no one has
>>tried doing that).
> 
> 
> There seems to be KGDB_MAX_NO_CPUS, but as 8250 patch does not check
> it, I believe that eth has no business checking it either.

I have not seen this one before.  It must be from Amit's patch base.

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


      reply	other threads:[~2004-03-03  1:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02 11:25 kgdb: fix kgdbeth compilation and make it init late enough Pavel Machek
2004-03-02 15:32 ` Tom Rini
2004-03-02 22:28   ` Pavel Machek
2004-03-02 22:43     ` Tom Rini
2004-03-03  1:04       ` George Anzinger
2004-03-02 22:33   ` Pavel Machek
2004-03-03  1:05     ` George Anzinger [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=40452F70.1070706@mvista.com \
    --to=george@mvista.com \
    --cc=akale@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=trini@kernel.crashing.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