From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>, x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL -tip v3] fix 39 'make headers_check' warnings
Date: Mon, 19 Jan 2009 07:40:11 +0530 [thread overview]
Message-ID: <1232331011.3129.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20090118185034.GA26908@elte.hu>
On Sun, 2009-01-18 at 19:50 +0100, Ingo Molnar wrote:
>
> static inline __attribute_const__ __u32 __arch_swab32(__u32 val)
> {
> #ifdef __i386__
> +#ifdef __KERNEL__
> # ifdef CONFIG_X86_BSWAP
> asm("bswap %0" : "=r" (val) : "0" (val));
> # else
> @@ -16,7 +19,13 @@ static inline __attribute_const__ __u32 __arch_swab32(__u32 val)
> : "=q" (val)
> : "0" (val));
> # endif
> -
> +#else /* __KERNEL__ */
> + asm("xchgb %b0,%h0\n\t" /* swap lower bytes */
> + "rorl $16,%0\n\t" /* swap words */
> + "xchgb %b0,%h0" /* swap higher bytes */
> + : "=q" (val)
> + : "0" (val));
> +#endif /* __KERNEL__ */
> #else /* __i386__ */
> asm("bswapl %0"
> : "=r" (val)
> @@ -37,6 +46,7 @@ static inline __attribute_const__ __u64 __arch_swab64(__u64 val)
> __u64 u;
> } v;
> v.u = val;
> +#ifdef __KERNEL__
> # ifdef CONFIG_X86_BSWAP
> asm("bswapl %0 ; bswapl %1 ; xchgl %0,%1"
> : "=r" (v.s.a), "=r" (v.s.b)
> @@ -48,6 +58,13 @@ static inline __attribute_const__ __u64 __arch_swab64(__u64 val)
> : "=r" (v.s.a), "=r" (v.s.b)
> : "0" (v.s.a), "1" (v.s.b));
> # endif
> +#else /* __KERNEL__ */
> + v.s.a = __arch_swab32(v.s.a);
> + v.s.b = __arch_swab32(v.s.b);
> + asm("xchgl %0,%1"
> + : "=r" (v.s.a), "=r" (v.s.b)
> + : "0" (v.s.a), "1" (v.s.b));
> +#endif /* __KERNEL__ */
> return v.u;
> #else /* __i386__ */
> asm("bswapq %0"
>
>
> why does such a change introduce new code? It is duplicating existing code
> instead of cleaning it all up.
>
That's why I was requesting you to check asm/swab.h because I was in
doubt whether we need these functions in userspace or not.
If we do not need these functions in userspace then I will clean these
up.
--
JSR
next prev parent reply other threads:[~2009-01-19 2:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 14:04 [GIT PULL -tip v3] fix 39 'make headers_check' warnings Jaswinder Singh Rajput
2009-01-18 17:28 ` Ingo Molnar
2009-01-18 18:50 ` Ingo Molnar
2009-01-18 18:52 ` Ingo Molnar
2009-01-18 19:08 ` Sam Ravnborg
2009-01-18 19:09 ` Ingo Molnar
2009-01-18 19:45 ` Sam Ravnborg
2009-01-19 2:16 ` Jaswinder Singh Rajput
2009-01-19 5:27 ` Sam Ravnborg
2009-01-19 2:10 ` Jaswinder Singh Rajput [this message]
2009-01-19 2:20 ` Harvey Harrison
2009-01-19 11:15 ` Ingo Molnar
2009-01-19 18:08 ` Harvey Harrison
2009-01-18 18:56 ` Ingo Molnar
2009-01-19 9:19 ` Avi Kivity
2009-01-19 11:01 ` Sam Ravnborg
2009-01-19 11:53 ` Avi Kivity
2009-01-24 6:16 ` Jaswinder Singh Rajput
2009-02-04 14:28 ` Avi Kivity
2009-02-04 15:17 ` Jaswinder Singh Rajput
2009-02-04 15:40 ` Avi Kivity
2009-02-04 16:00 ` Jaswinder Singh Rajput
2009-02-04 16:37 ` Arnd Bergmann
2009-02-04 17:22 ` Avi Kivity
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=1232331011.3129.4.camel@localhost.localdomain \
--to=jaswinder@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=x86@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