From: Michael Ellerman <michael@ellerman.id.au>
To: Sachin Sant <sachinp@in.ibm.com>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>,
nishimura@mxp.nes.nec.co.jp, lizf@cn.fujitsu.com,
linux-kernel <linux-kernel@vger.kernel.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: 34-rc1-git3 build failure with CGROUP_MEM_RES_CTLR_SWAP=y
Date: Mon, 15 Mar 2010 12:04:13 +1100 [thread overview]
Message-ID: <1268615053.4644.10.camel@concordia> (raw)
In-Reply-To: <4B9CBEE6.1090509@in.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
On Sun, 2010-03-14 at 16:18 +0530, Sachin Sant wrote:
> On a PowerPC box, latest 34-rc1 git(d89b218b8...) fails to build
> with CGROUPS_MEM_RES_CTRL_SWAP=y.
>
> LD init/built-in.o
> LD .tmp_vmlinux1
> mm/built-in.o: In function __xchg:
> arch/powerpc/include/asm/system.h:331: undefined reference to .__xchg_called_with_bad_pointer
> mm/built-in.o: In function __cmpxchg:
> arch/powerpc/include/asm/system.h:474: undefined reference to .__cmpxchg_called_with_bad_pointer
> make: *** [.tmp_vmlinux1] Error 1
>
> The code in question was added via commit 024914477e...
>
> memcg: move charges of anonymous swap
struct swap_cgroup
{
unsigned short id;
};
+unsigned short swap_cgroup_cmpxchg(swp_entry_t ent,
+ unsigned short old, unsigned short new)
+{
...
+ struct swap_cgroup *sc;
...
+ if (cmpxchg(&sc->id, old, new) == old)
On powerpc cmpxchg() currently only handles u32 & u64.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2010-03-15 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 10:48 34-rc1-git3 build failure with CGROUP_MEM_RES_CTLR_SWAP=y Sachin Sant
2010-03-15 1:02 ` [BUGFIX][PATCH] memcg: avoid use cmpxchg in swap cgroup maintainance (Was " KAMEZAWA Hiroyuki
2010-03-15 2:14 ` Balbir Singh
2010-03-15 3:16 ` Daisuke Nishimura
2010-03-15 3:21 ` Benjamin Herrenschmidt
2010-03-15 1:04 ` Michael Ellerman [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=1268615053.4644.10.camel@concordia \
--to=michael@ellerman.id.au \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=lizf@cn.fujitsu.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=sachinp@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).