From: Vegard Nossum <vegard.nossum@gmail.com>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Sam Ravnborg <sam@ravnborg.org>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86: cpu/intel.c cleanup
Date: Sat, 14 Mar 2009 15:00:25 +0100 [thread overview]
Message-ID: <19f34abd0903140700r6c23da9aq6747fbcce7bcc4b2@mail.gmail.com> (raw)
In-Reply-To: <1237037822.4546.8.camel@ht.satnam>
2009/3/14 Jaswinder Singh Rajput <jaswinder@kernel.org>:
> From: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> Date: Sat, 14 Mar 2009 17:47:38 +0530
> Subject: [PATCH] x86: cpu/intel.c cleanup
>
> - fix various style problems
> - fix header files issues
>
[...]
> static void __cpuinit early_init_intel(struct cpuinfo_x86 *c)
> {
> + u64 misc_enable;
> +
> /* Unmask CPUID levels if masked: */
> if (c->x86 > 6 || (c->x86 == 6 && c->x86_model >= 0xd)) {
> - u64 misc_enable;
>
> rdmsrl(MSR_IA32_MISC_ENABLE, misc_enable);
>
> @@ -44,16 +45,16 @@ static void __cpuinit early_init_intel(struct cpuinfo_x86 *c)
> }
>
> if ((c->x86 == 0xf && c->x86_model >= 0x03) ||
> - (c->x86 == 0x6 && c->x86_model >= 0x0e))
> + (c->x86 == 0x6 && c->x86_model >= 0x0e))
> set_cpu_cap(c, X86_FEATURE_CONSTANT_TSC);
>
> #ifdef CONFIG_X86_64
> set_cpu_cap(c, X86_FEATURE_SYSENTER32);
> -#else
> +#else /* CONFIG_X86_64 */
> /* Netburst reports 64 bytes clflush size, but does IO in 128 bytes */
> if (c->x86 == 15 && c->x86_cache_alignment == 64)
> c->x86_cache_alignment = 128;
> -#endif
> +#endif /* CONFIG_X86_64 */
>
> /* CPUID workaround for 0F33/0F34 CPU */
> if (c->x86 == 0xF && c->x86_model == 0x3
> @@ -96,19 +97,18 @@ static void __cpuinit early_init_intel(struct cpuinfo_x86 *c)
> * Ingo Molnar reported a Pentium D (model 6) and a Xeon
> * (model 2) with the same problem.
> */
> - if (c->x86 == 15) {
> - u64 misc_enable;
> + if (c->x86 != 15)
> + return;
>
> - rdmsrl(MSR_IA32_MISC_ENABLE, misc_enable);
> + rdmsrl(MSR_IA32_MISC_ENABLE, misc_enable);
>
> - if (misc_enable & MSR_IA32_MISC_ENABLE_FAST_STRING) {
> - printk(KERN_INFO "kmemcheck: Disabling fast string operations\n");
> + if (misc_enable & MSR_IA32_MISC_ENABLE_FAST_STRING) {
> + pr_info("kmemcheck: Disabling fast string operations\n");
>
> - misc_enable &= ~MSR_IA32_MISC_ENABLE_FAST_STRING;
> - wrmsrl(MSR_IA32_MISC_ENABLE, misc_enable);
> - }
> + misc_enable &= ~MSR_IA32_MISC_ENABLE_FAST_STRING;
> + wrmsrl(MSR_IA32_MISC_ENABLE, misc_enable);
> }
> -#endif
> +#endif /* CONFIG_KMEMCHECK */
> }
I don't really like this change (last hunk). Doesn't it seem a bit
pointless? It breaks the symmetry with the masked CPUID levels at the
beginning of the function. If somebody wants to add something else to
this function, it might have to be reindented again. Or is there a
problem with too long lines here?
But it's just a question of taste -- if this is the preferred style,
then it's fine.
Vegard
next prev parent reply other threads:[~2009-03-14 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 12:41 Jaswinder Singh Rajput
2009-03-14 13:11 ` Sam Ravnborg
2009-03-14 13:20 ` Ingo Molnar
2009-03-14 13:37 ` Jaswinder Singh Rajput
2009-03-14 14:00 ` Vegard Nossum [this message]
2009-03-14 15:31 ` Ingo Molnar
2009-03-14 16:04 ` Jaswinder Singh Rajput
2009-03-14 17:04 ` Ingo Molnar
2009-03-14 18:05 ` Jaswinder Singh Rajput
2009-03-15 5:55 ` Ingo Molnar
2009-03-14 13:21 ` Jaswinder Singh Rajput
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=19f34abd0903140700r6c23da9aq6747fbcce7bcc4b2@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=jaswinder@kernel.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
all inboxes | Powered by JetHome®