public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
Cc: Dave Jones <davej@redhat.com>,
	tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] x86: Quark: Enable correct cache size/type reporting
Date: Mon, 29 Sep 2014 16:17:27 +0200	[thread overview]
Message-ID: <20140929141727.GA19294@gmail.com> (raw)
In-Reply-To: <542968AE.3090407@nexus-software.ie>


* Bryan O'Donoghue <pure.logic@nexus-software.ie> wrote:

> On 29/09/14 14:40, Dave Jones wrote:
> >On Mon, Sep 29, 2014 at 03:06:12AM +0100, Bryan O'Donoghue wrote:
> >  > Quark X1000 lacks cpuid(4). It has cpuid(2) but returns no cache
> >  > descriptors we can work with i.e. cpuid(2) returns
> >  > eax=0x00000001 ebx=0x00000000 ecx=0x00000000 edx=0x00000000
> >  >
> >  > Quark X1000 contains a 16k 4-way set associative unified L1 cache
> >  > with 256 sets
> >  >
> >  > This patch emulates cpuid(4) in a similar way to other x86
> >  > processors like AMDs which don't support cpuid(4). The Quark code
> >  > is based on the existing AMD code.
> >
> >This looks like it would work, but I wonder if it would be a lot
> >simpler to do something like what we do in centaur_size_cache()
> >which is the other case I recall where we had to override
> >the CPUs definition of cache size.
> 
> Hi Dave.
> 
> It's working alright :)
> 
> My feeling is that we'll probably end up with less changes/new code taking
> the approach of quirking.

OTOH, if the Quark quirk is a .legacy_cache_size callback, it 
will be compiled out on 64-bit kernels. With your patch it's 
unconditional.

So Dave's suggestion makes sense.

Thanks,

	Ingo

  reply	other threads:[~2014-09-29 14:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29  2:06 [PATCH 0/1] x86: Quark: Enable correct cache size/type reporting Bryan O'Donoghue
2014-09-29  2:06 ` [PATCH 1/1] " Bryan O'Donoghue
2014-09-29 12:15   ` Ingo Molnar
2014-09-29 12:22     ` Bryan O'Donoghue
2014-09-29 12:34       ` Ingo Molnar
2014-09-29 12:35         ` Bryan O'Donoghue
2014-09-29 13:40   ` Dave Jones
2014-09-29 14:11     ` Bryan O'Donoghue
2014-09-29 14:17       ` Ingo Molnar [this message]
2014-09-29 14:18         ` Bryan O'Donoghue
2014-09-29 12:17 ` [PATCH 0/1] " Ingo Molnar

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=20140929141727.GA19294@gmail.com \
    --to=mingo@kernel.org \
    --cc=davej@redhat.com \
    --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