All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valentine Barshak <vbarshak@ru.mvista.com>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, sr@denx.de
Subject: Re: [RFC] [PATCH] PowerPC: Workaround for the 440EP(x)/GR(x)	processors identical PVR issue.
Date: Fri, 26 Oct 2007 15:05:13 +0400	[thread overview]
Message-ID: <4721C9E9.10208@ru.mvista.com> (raw)
In-Reply-To: <1193345051.7018.15.camel@pasglop>

Benjamin Herrenschmidt wrote:
> On Thu, 2007-10-25 at 22:16 +0400, Valentine Barshak wrote:
>> PowerPC 440EP(x) 440GR(x) processors have the same PVR values, since
>> they have identical cores. However, FPU is not supported on GR(x) and
>> enabling APU instruction broadcast in the CCR0 register (to enable FPU)
>> may cause unpredictable results. There's no safe way to detect FPU
>> support at runtime. This patch provides a workarund for the issue.
>> We use a POWER6 "logical PVR approach". First, we identify all EP(x)
>> and GR(x) processors as GR(x) ones (which is safe). Then we check 
>> the device tree cpu path. If we have a EP(x) processor entry,
>> we call identify_cpu again with PVR | 0x8. This bit is always 0
>> in the real PVR. This way we enable FPU only for 440EP(x).
>>
>> Signed-off-by: Valentine Barshak <vbarshak@ru.mvista.com>
> 
> Why not just or-in the FPU feature bit ?
> 
> Ben.
> 
> 

It's not enough. We need to enable APU instruction broadcast for EP(x) 
(call __init_fpu_44x in arch/powerpc/kernel/cpu_setup_44x.S).
Or do you suggest to or-in FPU feature bit and enable APUIB later, not 
in the cpu_setup callback?
Thanks,
Valentine.

  reply	other threads:[~2007-10-26 11:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 18:16 [RFC] [PATCH] PowerPC: Workaround for the 440EP(x)/GR(x) processors identical PVR issue Valentine Barshak
2007-10-25 20:44 ` Benjamin Herrenschmidt
2007-10-26 11:05   ` Valentine Barshak [this message]
2007-10-26 11:25     ` Benjamin Herrenschmidt
2007-10-26 13:16       ` Valentine Barshak

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=4721C9E9.10208@ru.mvista.com \
    --to=vbarshak@ru.mvista.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sr@denx.de \
    /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.