All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH -next] ia64/sn: fix percpu warnings
Date: Wed, 28 Oct 2009 16:37:24 +0000	[thread overview]
Message-ID: <4AE87344.6030708@kernel.org> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA3E34C0108@orsmsx505.amr.corp.intel.com>

Hello,

Luck, Tony wrote:
> That's what Randy's patch uses ... but doing it the "right" way gives
> me the "has no CRC!" warning.

Ah, right.  I got confused.

> This seems to be a feature of exported per cpu arrays.  If I hack
> up a driver to make use of softirq_work_list, I see a similar
> no CRC warning for it.
> 
> Is this problem in the ia64 tool chain[1]?  Or do other architectures
> have problems with exported per cpu arrays?

kern/softirq.c has the followings.

 DEFINE_PER_CPU(struct list_head [NR_SOFTIRQS], softirq_work_list);
 EXPORT_PER_CPU_SYMBOL(softirq_work_list);

and it doesn't cause any warning on x86 neither does it on ia64 with
defconfig.  softirq_work_list doesn't trigger any warning there,
right?

Thanks.

-- 
tejun

WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH -next] ia64/sn: fix percpu warnings
Date: Wed, 28 Oct 2009 17:37:24 +0100	[thread overview]
Message-ID: <4AE87344.6030708@kernel.org> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA3E34C0108@orsmsx505.amr.corp.intel.com>

Hello,

Luck, Tony wrote:
> That's what Randy's patch uses ... but doing it the "right" way gives
> me the "has no CRC!" warning.

Ah, right.  I got confused.

> This seems to be a feature of exported per cpu arrays.  If I hack
> up a driver to make use of softirq_work_list, I see a similar
> no CRC warning for it.
> 
> Is this problem in the ia64 tool chain[1]?  Or do other architectures
> have problems with exported per cpu arrays?

kern/softirq.c has the followings.

 DEFINE_PER_CPU(struct list_head [NR_SOFTIRQS], softirq_work_list);
 EXPORT_PER_CPU_SYMBOL(softirq_work_list);

and it doesn't cause any warning on x86 neither does it on ia64 with
defconfig.  softirq_work_list doesn't trigger any warning there,
right?

Thanks.

-- 
tejun

  reply	other threads:[~2009-10-28 16:37 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14  5:34 linux-next: Tree for October 14 Stephen Rothwell
2009-10-14 15:55 ` Randy Dunlap
2009-10-14 21:12   ` Stephen Rothwell
2009-10-14 22:10 ` [PATCH -next] ia64/sn: fix percpu warnings Randy Dunlap
2009-10-14 22:10   ` Randy Dunlap
2009-10-15  1:33   ` Tejun Heo
2009-10-15  1:33     ` Tejun Heo
2009-10-26 18:24     ` Tony Luck
2009-10-26 18:24       ` Tony Luck
2009-10-26 23:35       ` Luck, Tony
2009-10-26 23:35         ` Luck, Tony
2009-10-28 15:03         ` Tejun Heo
2009-10-28 15:03           ` Tejun Heo
2009-10-28 16:24           ` Luck, Tony
2009-10-28 16:24             ` Luck, Tony
2009-10-28 16:37             ` Tejun Heo [this message]
2009-10-28 16:37               ` Tejun Heo
2009-10-28 16:58               ` Luck, Tony
2009-10-28 16:58                 ` Luck, Tony
2009-10-28 22:23                 ` Luck, Tony
2009-10-28 22:23                   ` Luck, Tony
2009-10-29 14:43                   ` Tejun Heo
2009-10-29 14:43                     ` Tejun Heo
2009-10-29 15:43                     ` Tejun Heo
2009-10-29 15:43                       ` Tejun Heo
2009-10-30 16:05                       ` Jan Beulich
2009-10-15  1:17 ` [PATCH -next] vmxnet: fix 2 build problems Randy Dunlap
2009-10-15  1:17   ` Randy Dunlap
2009-10-15  2:00   ` [Pv-drivers] " Bhavesh Davda
2009-10-15  2:00     ` Bhavesh Davda
2009-10-15  3:39     ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2009-10-14 22:10 [PATCH -next] kvm: fix ia64 printk formats Randy Dunlap
2009-10-14 22:10 ` Randy Dunlap
2009-10-15  2:32 ` Zhang, Xiantao
2009-10-15  2:32   ` Zhang, Xiantao

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=4AE87344.6030708@kernel.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tony.luck@intel.com \
    /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.