From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>, ak@suse.de
Subject: Re: [PATCH -mm] x86_64: kill 19000+ sparse warnings
Date: Wed, 25 Apr 2007 23:07:56 -0700 [thread overview]
Message-ID: <463041BC.8000708@oracle.com> (raw)
In-Reply-To: <20070425225516.8b573d34.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 25 Apr 2007 22:45:09 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
>> From: Randy Dunlap <randy.dunlap@oracle.com>
>>
>> Eliminate 19439 (!!) sparse warnings like:
>> include/linux/mm.h:321:22: warning: constant 0xffff810000000000 is so big it is unsigned long
>>
>> Eliminate 56 sparse warnings like:
>> arch/x86_64/kernel/setup.c:248:16: warning: constant 0xffffffff80000000 is so big it is unsigned long
>>
>> Eliminate 5 sparse warnings like:
>> arch/x86_64/kernel/module.c:49:13: warning: constant 0xfffffffffff00000 is so big it is unsigned long
>>
>> Eliminate 23 sparse warnings like:
>> arch/x86_64/mm/init.c:551:37: warning: constant 0xffffc20000000000 is so big it is unsigned long
>>
>> Eliminate 6 sparse warnings like:
>> arch/x86_64/kernel/module.c:49:13: warning: constant 0xffffffff88000000 is so big it is unsigned long
>>
>> Eliminate 23 sparse warnings like:
>> arch/x86_64/mm/init.c:552:6: warning: constant 0xffffe1ffffffffff is so big it is unsigned long
>>
>> Eliminate 3 sparse warnings like:
>> arch/x86_64/kernel/e820.c:186:17: warning: constant 0x3fffffffffff is so big it is long
>>
>> ...
>>
>> +#ifdef __ASSEMBLY__
>> #define MAXMEM 0x3fffffffffff
>> #define VMALLOC_START 0xffffc20000000000
>> #define VMALLOC_END 0xffffe1ffffffffff
>> #define MODULES_VADDR 0xffffffff88000000
>> #define MODULES_END 0xfffffffffff00000
>> #define MODULES_LEN (MODULES_END - MODULES_VADDR)
>> +#else
>> +#define MAXMEM 0x3fffffffffffUL
>> +#define VMALLOC_START 0xffffc20000000000UL
>> +#define VMALLOC_END 0xffffe1ffffffffffUL
>> +#define MODULES_VADDR 0xffffffff88000000UL
>> +#define MODULES_END 0xfffffffffff00000UL
>> +#define MODULES_LEN (MODULES_END - MODULES_VADDR)
>> +#endif
>>
>
> hm, the duplication is unfortunate.
Yep.
> I wonder if it's worth doing a cpp token-pasting trick to avoid having to
> do that.
oh. there is already an include/asm-x86_64/const.h that will help
with that. I'll try it out.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-04-26 6:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 5:45 [PATCH -mm] x86_64: kill 19000+ sparse warnings Randy Dunlap
2007-04-26 5:55 ` Andrew Morton
2007-04-26 6:07 ` Randy Dunlap [this message]
2007-04-26 6:14 ` Andrew Morton
2007-04-26 6:21 ` Randy Dunlap
2007-04-26 6:28 ` Andrew Morton
2007-04-26 6:33 ` Randy Dunlap
2007-04-26 7:15 ` [PATCH -mm, v2] " Randy Dunlap
2007-04-26 9:24 ` [PATCH -mm] " Andi Kleen
2007-04-27 6:49 ` Jan Engelhardt
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=463041BC.8000708@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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 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.