From: Frederic Weisbecker <fweisbec@gmail.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
stable@kernel.org
Subject: Re: [PATCH] x86,kgdb: Always initialize the hw breakpoint attribute
Date: Tue, 30 Mar 2010 20:49:22 +0200 [thread overview]
Message-ID: <20100330184921.GE5078@nowhere> (raw)
In-Reply-To: <1269974370-24831-1-git-send-email-jason.wessel@windriver.com>
On Tue, Mar 30, 2010 at 01:39:30PM -0500, Jason Wessel wrote:
> It is required to call hw_breakpoint_init() on an attr before using it
> in any other calls. This fixes the problem where kgdb will sometimes
> fail to initialize on x86_64.
>
> CC: Frederic Weisbecker <fweisbec@gmail.com>
> CC: Ingo Molnar <mingo@elte.hu>
> CC: stable@kernel.org
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
> ---
> arch/x86/kernel/kgdb.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kernel/kgdb.c b/arch/x86/kernel/kgdb.c
> index bfba601..d9adcde 100644
> --- a/arch/x86/kernel/kgdb.c
> +++ b/arch/x86/kernel/kgdb.c
> @@ -618,6 +618,7 @@ int kgdb_arch_init(void)
> * portion of kgdb because this operation requires mutexs to
> * complete.
> */
> + hw_breakpoint_init(&attr);
> attr.bp_addr = (unsigned long)kgdb_arch_init;
> attr.type = PERF_TYPE_BREAKPOINT;
Minor neat: In this case you don't need to set the type.
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
> attr.bp_len = HW_BREAKPOINT_LEN_1;
> --
> 1.6.3.1.9.g95405b
>
prev parent reply other threads:[~2010-03-30 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 18:39 [PATCH] x86,kgdb: Always initialize the hw breakpoint attribute Jason Wessel
2010-03-30 18:49 ` Frederic Weisbecker [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=20100330184921.GE5078@nowhere \
--to=fweisbec@gmail.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@kernel.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