From: DDD <dongdong.deng@windriver.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Jason Wessel <jason.wessel@windriver.com>,
kgdb-bugreport@lists.sourceforge.net,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Kgdb-bugreport] [GIT PULL] kgdb regression fixes for 2.6.35-rc5
Date: Thu, 29 Jul 2010 10:49:50 +0800 [thread overview]
Message-ID: <4C50EC4E.6090004@windriver.com> (raw)
In-Reply-To: <20100729010607.GB13088@nowhere>
Frederic Weisbecker wrote:
> On Wed, Jul 28, 2010 at 07:14:42PM -0500, Jason Wessel wrote:
>> On 07/28/2010 04:26 PM, Linus Torvalds wrote:
>>> On Wed, Jul 28, 2010 at 2:17 PM, Frederic Weisbecker <fweisbec@gmail.com> wrote:
>>>> I'm sorry I spot it a bit late.
>>>> There is a little issue in this patch, irqs won't
>>>> be restored:
>>>>
>>>> @@ -588,9 +588,10 @@ int kgdb_ll_trap(int cmd, const char *str,
>>>> if (!kgdb_io_module_registered)
>>>> return NOTIFY_DONE;
>>>>
>>>> + local_irq_save(flags);
>>>> return __kgdb_notify(&args, cmd);
>>>> + local_irq_restore(flags);
>>>> }
>>> Yeah, that's obviously crap. I also wonder why __kgdb_notify messes up
>>> the flags to begin with.
>>>
>> This should not be needed as the irqs should already be off while in the overflow handler.
>
>
>
> Interrupts are not disabled in the debug exception handler.
Hi Frederic,
The debug was initialized as an intr gate, thus the interrupts have been
disabled in the debug exception handler. :-)
arch/x86/kernel/traps.c:
820 /* Set of traps needed for early debugging. */
821 void __init early_trap_init(void)
822 {
823 set_intr_gate_ist(1, &debug, DEBUG_STACK);
824 /* int3 can be called from all */
825 set_system_intr_gate_ist(3, &int3, DEBUG_STACK);
826 set_intr_gate(14, &page_fault);
827 load_idt(&idt_descr);
828 }
Thanks,
Dongdong
>
> I'm not sure what would be the state of dr6 if a nested debug exception
> would happen while do_debug() is interrupted.
>
> Perhaps the previous dr6 value is dropped. Intel manuals don't seem to say anything
> about that.
>
> Anyway that's a separate issue. The current patch fixes a regression and
> it looks good.
>
> Thanks.
>
>
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://p.sf.net/sfu/dev2dev-palm
> _______________________________________________
> Kgdb-bugreport mailing list
> Kgdb-bugreport@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
>
next prev parent reply other threads:[~2010-07-29 2:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 20:39 [GIT PULL] kgdb regression fixes for 2.6.35-rc5 Jason Wessel
2010-07-28 20:39 ` [PATCH] x86,kgdb: Fix hw breakpoint regression Jason Wessel
2010-07-28 21:17 ` [GIT PULL] kgdb regression fixes for 2.6.35-rc5 Frederic Weisbecker
2010-07-28 21:26 ` Linus Torvalds
2010-07-29 0:14 ` Jason Wessel
2010-07-29 1:06 ` Frederic Weisbecker
2010-07-29 2:49 ` DDD [this message]
2010-07-29 2:55 ` [Kgdb-bugreport] " Frederic Weisbecker
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=4C50EC4E.6090004@windriver.com \
--to=dongdong.deng@windriver.com \
--cc=fweisbec@gmail.com \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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