public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 1/1] x86,kgdb: Always initialize the hw breakpoint attribute
Date: Tue, 30 Mar 2010 21:15:04 +0200	[thread overview]
Message-ID: <20100330191502.GG5078@nowhere> (raw)
In-Reply-To: <1269975907-27602-1-git-send-email-jason.wessel@windriver.com>

On Tue, Mar 30, 2010 at 02:05:07PM -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: Ingo Molnar <mingo@elte.hu>
> CC: stable@kernel.org
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
> Acked-by: Frederic Weisbecker <fweisbec@gmail.com>


Queued for perf/urgent, thanks!



> ---
>  arch/x86/kernel/kgdb.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/x86/kernel/kgdb.c b/arch/x86/kernel/kgdb.c
> index bfba601..b2258ca 100644
> --- a/arch/x86/kernel/kgdb.c
> +++ b/arch/x86/kernel/kgdb.c
> @@ -618,8 +618,8 @@ 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;
>  	attr.bp_len = HW_BREAKPOINT_LEN_1;
>  	attr.bp_type = HW_BREAKPOINT_W;
>  	attr.disabled = 1;
> -- 
> 1.5.4.3
> 


  reply	other threads:[~2010-03-30 19:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 19:05 [PATCH 1/1] x86,kgdb: Always initialize the hw breakpoint attribute Jason Wessel
2010-03-30 19:15 ` Frederic Weisbecker [this message]
2010-04-02 19:06 ` [tip:perf/core] " tip-bot for 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=20100330191502.GG5078@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