From: Frederic Weisbecker <fweisbec@gmail.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net
Subject: Re: [GIT PULL] kgdb regression fixes for 2.6.35-rc5
Date: Wed, 28 Jul 2010 23:17:27 +0200 [thread overview]
Message-ID: <20100728211725.GF5394@nowhere> (raw)
In-Reply-To: <1280349590-27754-1-git-send-email-jason.wessel@windriver.com>
On Wed, Jul 28, 2010 at 03:39:49PM -0500, Jason Wessel wrote:
> Linus, please pull the for_linus branch for 2.6.35-rc6.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_linus
>
> The kgdb validation tests found a regression where HW breakpoints
> stopped working with kdb / kgdb. The problem was bisected and after
> talking with Frederic Weisbecker a patch was generated to repair the
> regression.
>
> Thanks,
> Jason.
>
>
> ---
> Jason Wessel (1):
> x86,kgdb: Fix hw breakpoint regression
>
> arch/x86/kernel/kgdb.c | 12 ++++++++++--
> 1 files changed, 10 insertions(+), 2 deletions(-)
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);
}
next prev parent reply other threads:[~2010-07-28 21:17 UTC|newest]
Thread overview: 9+ 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 ` Frederic Weisbecker [this message]
2010-07-28 21:26 ` [GIT PULL] kgdb regression fixes for 2.6.35-rc5 Linus Torvalds
2010-07-29 0:14 ` Jason Wessel
2010-07-29 1:06 ` Frederic Weisbecker
2010-07-29 2:49 ` [Kgdb-bugreport] " DDD
2010-07-29 2:55 ` Frederic Weisbecker
-- strict thread matches above, loose matches on Subject: below --
2010-07-22 0:36 Jason Wessel
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=20100728211725.GF5394@nowhere \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.