From: Dave Jones <davej@redhat.com>
To: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
Cc: mingo@redhat.com, hpa@zytor.com, tglx@linutronix.de,
hmh@hmh.eng.br, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] x86: Bugfix bit-rot in the calling of legacy_cache_size
Date: Mon, 29 Sep 2014 23:41:29 -0400 [thread overview]
Message-ID: <20140930034129.GB14558@redhat.com> (raw)
In-Reply-To: <1412046710-2686-2-git-send-email-pure.logic@nexus-software.ie>
On Tue, Sep 30, 2014 at 04:11:48AM +0100, Bryan O'Donoghue wrote:
> Make an update to identify_cpu to make an explicit call to default_init()
> We want to do this since some processors that report vendor strings via
> cpuid also want to run legacy_cache_size callbacks - which won't happen
> since init_intel() init_amd() and friends take the place of default_init()
> and don't themselves make explicit calls to legacy_cache_size.
>
> Also current code has an
> #ifdef CONFIG_X86_64
> cpu_detect_cache_sizes(c);
> #endif
...
> static void default_init(struct cpuinfo_x86 *c)
> {
> -#ifdef CONFIG_X86_64
> cpu_detect_cache_sizes(c);
> -#else
> +
> /* Not much we can do here... */
> /* Check if at least it has cpuid */
> if (c->cpuid_level == -1) {
> @@ -79,7 +78,6 @@ static void default_init(struct cpuinfo_x86 *c)
> else if (c->x86 == 3)
> strcpy(c->x86_model_id, "386");
> }
> -#endif
Shouldn't this patch be more like..
-#ifdef CONFIG_X86_64
cpu_detect_cache_sizes(c);
-#else
+
+#ifdef CONFIG_X86_32
?
The 386/486 stuff in this codepath isn't huge, but it
seems pointless to be compiling it on 64-bit.
Dave
next prev parent reply other threads:[~2014-09-30 3:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 3:11 [PATCH 0/3] Quark X1000 Cache/TLB reporting/fixes Bryan O'Donoghue
2014-09-30 3:11 ` [PATCH 1/3] x86: Bugfix bit-rot in the calling of legacy_cache_size Bryan O'Donoghue
2014-09-30 3:41 ` Dave Jones [this message]
2014-09-30 8:45 ` Bryan O'Donoghue
2014-09-30 20:28 ` Thomas Gleixner
2014-09-30 21:02 ` Bryan O'Donoghue
2014-09-30 3:11 ` [PATCH 2/3] x86: Quark: Update cache reporting, add Quark SoC X1000 string Bryan O'Donoghue
2014-09-30 19:38 ` Thomas Gleixner
2014-09-30 3:11 ` [PATCH 3/3] x86: Quark: Comment setup_arch for TLB/PGE bugfix Bryan O'Donoghue
2014-09-30 20:03 ` Thomas Gleixner
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=20140930034129.GB14558@redhat.com \
--to=davej@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pure.logic@nexus-software.ie \
--cc=tglx@linutronix.de \
--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
Powered by JetHome