All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Roel Kluin <roel.kluin@gmail.com>, Cliff Wickman <cpw@sgi.com>,
	Robin Holt <holt@sgi.com>, Mike Travis <travis@sgi.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: bau_msg_head points to a_queue_first in uv_table_bases_finish()
Date: Sun, 17 Jan 2010 08:12:27 +0100	[thread overview]
Message-ID: <20100117071227.GC19512@elte.hu> (raw)
In-Reply-To: <4B507093.6050002@gmail.com>


* Roel Kluin <roel.kluin@gmail.com> wrote:

> bau_msg_head should point to bau_msg_head
> 
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
> ---
> Is this correct?
> 
> diff --git a/arch/x86/kernel/tlb_uv.c b/arch/x86/kernel/tlb_uv.c
> index 364d015..3d66331 100644
> --- a/arch/x86/kernel/tlb_uv.c
> +++ b/arch/x86/kernel/tlb_uv.c
> @@ -691,7 +691,7 @@ uv_table_bases_finish(int blade,
>  			continue;
>  
>  		bcp = (struct bau_control *)&per_cpu(bau_control, cpu);
> -		bcp->bau_msg_head	= bau_tablesp->va_queue_first;
> +		bcp->bau_msg_head	= bau_tablesp->bau_msg_head;
>  		bcp->va_queue_first	= bau_tablesp->va_queue_first;
>  		bcp->va_queue_last	= bau_tablesp->va_queue_last;
>  		bcp->msg_statuses	= bau_tablesp->msg_statuses;

Seems like you either caught a real bug - or that there's a somewhat quirky 
initialization sequence here which should be commented upon in the source.

Cliff, Robin, what's your take on Roel's patch?

Thanks,

	Ingo

  reply	other threads:[~2010-01-17  7:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-15 13:41 [PATCH] x86: bau_msg_head points to a_queue_first in uv_table_bases_finish() Roel Kluin
2010-01-17  7:12 ` Ingo Molnar [this message]
2010-01-17 12:53   ` Robin Holt
2010-01-18 13:35   ` Cliff Wickman

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=20100117071227.GC19512@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=cpw@sgi.com \
    --cc=holt@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=roel.kluin@gmail.com \
    --cc=travis@sgi.com \
    --cc=x86@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 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.