public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] per cpu MCA/INIT fixes.
Date: Thu, 06 Jan 2005 17:14:06 +0000	[thread overview]
Message-ID: <200501060914.06506.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <200501060308.j0638M7s194286@ben.americas.sgi.com>

On Wednesday, January 5, 2005 7:08 pm, Russ Anderson wrote:
>  #ifdef CONFIG_VIRTUAL_MEM_MAP
> Index: linux/arch/ia64/mm/discontig.c
> =================================> --- linux.orig/arch/ia64/mm/discontig.c 2005-01-05 15:26:42.455970944 -0600
> +++ linux/arch/ia64/mm/discontig.c 2005-01-05 15:33:50.644044221 -0600
> @@ -348,12 +348,12 @@
>    mem_data[node].node_data = __va(pernode);
>    pernode += L1_CACHE_ALIGN(sizeof(struct ia64_node_data));
>
> -  mca_data_phys = (void *)pernode;
> -  pernode += L1_CACHE_ALIGN(sizeof(ia64_mca_cpu_t)) * phys_cpus;
> -
>    mem_data[node].pgdat->bdata = bdp;
>    pernode += L1_CACHE_ALIGN(sizeof(pg_data_t));
>
> +  mca_data_phys = (void *)pernode;
> +  pernode += L1_CACHE_ALIGN(sizeof(ia64_mca_cpu_t)) * phys_cpus;
> +

The above will probably conflict with Jack's recent change to stagger the 
per-node structures by one cacheline.  You may have to rediff against one of 
Tony's test trees.

> +#ifdef CONFIG_SMP
> +#include <asm/mca.h>
> +#endif

Just a nit, header files should always be safe to include unconditionally.  If 
they're not, the headers need fixing (barring out of tree stuff like kdb of 
course).

Jesse


  reply	other threads:[~2005-01-06 17:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06  3:08 [patch] per cpu MCA/INIT fixes Russ Anderson
2005-01-06 17:14 ` Jesse Barnes [this message]
2005-01-06 18:21 ` Russ Anderson
2005-01-06 18:28 ` Luck, Tony
2005-01-06 18:36 ` Jesse Barnes
2005-01-06 20:50 ` Russ Anderson
2005-01-06 23:17 ` Russ Anderson
2005-01-07  6:51 ` Luck, Tony
2005-01-07  7:08 ` Luck, Tony
2005-01-07 17:47 ` Bjorn Helgaas
2005-01-07 18:56 ` Luck, Tony
2005-01-07 19:28 ` Russ Anderson

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=200501060914.06506.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=linux-ia64@vger.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