From: kbuild test robot <fengguang.wu@intel.com>
To: Michal Hocko <mhocko@suse.com>
Cc: kbuild-all@01.org, linux-mm@kvack.org
Subject: [memcg:down_write_killable-core-4.5-merge 11/12] arch/x86/include/asm/rwsem.h:106:2: error: 'asm' operand has impossible constraints
Date: Sun, 17 Apr 2016 10:42:21 +0800 [thread overview]
Message-ID: <201604171016.EgHMwPEn%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2590 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git down_write_killable-core-4.5-merge
head: 2abae317b1c05a462762da079706a9222c99209f
commit: b5e50bccc40edf01218784bd14a6f9c2222b638b [11/12] locking, rwsem: provide down_write_killable
config: i386-randconfig-x0-04170940 (attached as .config)
reproduce:
git checkout b5e50bccc40edf01218784bd14a6f9c2222b638b
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from include/linux/rwsem.h:52:0,
from include/linux/mm_types.h:10,
from include/linux/sched.h:27,
from kernel/locking/rwsem.c:9:
kernel/locking/rwsem.c: In function 'down_write_killable':
>> arch/x86/include/asm/rwsem.h:106:2: error: 'asm' operand has impossible constraints
asm volatile("# beginning down_write\n\t" \
^
arch/x86/include/asm/rwsem.h:128:13: note: in expansion of macro '____down_write'
if (IS_ERR(____down_write(sem, "call_rwsem_down_write_failed_killable")))
^
vim +/asm +106 arch/x86/include/asm/rwsem.h
^1da177e include/asm-i386/rwsem.h Linus Torvalds 2005-04-16 100 * lock for writing
^1da177e include/asm-i386/rwsem.h Linus Torvalds 2005-04-16 101 */
fae51f6c arch/x86/include/asm/rwsem.h Michal Hocko 2016-02-01 102 #define ____down_write(sem, slow_path) \
fae51f6c arch/x86/include/asm/rwsem.h Michal Hocko 2016-02-01 103 ({ \
fae51f6c arch/x86/include/asm/rwsem.h Michal Hocko 2016-02-01 104 long tmp; \
fae51f6c arch/x86/include/asm/rwsem.h Michal Hocko 2016-02-01 105 struct rw_semaphore* ret = sem; \
fae51f6c arch/x86/include/asm/rwsem.h Michal Hocko 2016-02-01 @106 asm volatile("# beginning down_write\n\t" \
fae51f6c arch/x86/include/asm/rwsem.h Michal Hocko 2016-02-01 107 LOCK_PREFIX " xadd %1,(%2)\n\t" \
fae51f6c arch/x86/include/asm/rwsem.h Michal Hocko 2016-02-01 108 /* adds 0xffff0001, returns the old value */ \
fae51f6c arch/x86/include/asm/rwsem.h Michal Hocko 2016-02-01 109 " test " __ASM_SEL(%w1,%k1) "," __ASM_SEL(%w1,%k1) "\n\t" \
:::::: The code at line 106 was first introduced by commit
:::::: fae51f6cba6ec620af820033d4feecb075a11909 x86, rwsem: provide __down_write_killable
:::::: TO: Michal Hocko <mhocko@suse.com>
:::::: CC: Michal Hocko <mhocko@suse.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 19480 bytes --]
reply other threads:[~2016-04-17 2:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201604171016.EgHMwPEn%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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