Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Daniel Laird <daniel.j.laird@nxp.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Fix known HW bug with MIPS core on NXP/Philips PNX8550
Date: Thu, 19 Jul 2007 21:32:46 +0400	[thread overview]
Message-ID: <469FA03E.7070209@ru.mvista.com> (raw)
In-Reply-To: <469F822D.9040209@nxp.com>

Hello.

Daniel Laird wrote:

 > Fix known bug with MIPS core when using TLB on NXP/Philips PNX8550

    Would've been god to somehow document it too...

> Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>

> Index: linux-2.6.22.1/arch/mips/mm/tlbex.c
> ===================================================================
> --- linux-2.6.22.1/arch/mips/mm/tlbex.c    (revision 8)
> +++ linux-2.6.22.1/arch/mips/mm/tlbex.c    (working copy)
[...]
> @@ -705,6 +719,7 @@
> 
> /* Some CP0 registers */
> #define C0_INDEX    0, 0
> +#define C0_RANDOM   1, 0
> #define C0_ENTRYLO0    2, 0
> #define C0_TCBIND    2, 2
> #define C0_ENTRYLO1    3, 0
> @@ -712,6 +727,7 @@
> #define C0_BADVADDR    8, 0
> #define C0_ENTRYHI    10, 0
> #define C0_EPC        14, 0
> +#define C0_CONFIG    16, 0
> #define C0_XCONTEXT    20, 0
> 
> #ifdef CONFIG_64BIT
> @@ -734,6 +750,57 @@
> static __initdata struct label labels[128];
> static __initdata struct reloc relocs[128];
> 
> +#ifdef CONFIG_PNX8550
> +static void __init build_pnx8550_bug_fix( u32 **p, struct label **l, 
> struct reloc **r)
> +{
> +#define MFC0(_reg, _cp, _sel)    \
> +    ((cop0_op)  << OP_SH    \
> +    | (mfc_op) << RS_SH    \
> +    | (_reg)   << RT_SH    \
> +    | (_cp)    << RD_SH    \
> +    | (_sel))
> +
> +#define MTC0(_reg, _cp, _sel)    \
> +    ((cop0_op)  << OP_SH    \
> +    | (mtc_op) << RS_SH    \
> +    | (_reg)   << RT_SH    \
> +    | (_cp)    << RD_SH    \
> +    | (_sel))
> +

    Macro defs inside function, isn't that er... too much?
    And don't we already have macro M() doing exactly what these two macros 
are doing?

> +    /* load epc and badvaddr to k0 and k1 */
> +    i_MFC0(p, K0, C0_EPC);
> +    i_MFC0(p, K1, C0_BADVADDR);
> +
> +    /* branch if code entry  */
> +    il_beq(p, r, K0, K1, label_pnx8550_bac_reset);
> +    i_addiu(p, K0, K0, 4);
> +
> +    /* branch if code entry in BDS */
> +    il_beq(p, r, K0, K1, label_pnx8550_bac_reset);
> +    i_nop(p);
> +    /* Write data tlb entry 11..31 */
> +    i_tlbwr(p);
> +    i_eret(p);
> +    /* BAC Reset */
> +    l_pnx8550_bac_reset(l, *p);
> +    **p = MFC0(K0, C0_CONFIG, 7);
> +    (*p)++;

    Hmmm, why we need another version of i_MFC0? After looking at the currecnt 
code it seemed to me that i_M[FT]C0 are just using i_[d]m[ft]c0 incorrectly -- 
those are difined to have 3 opcode args (by being built as I_u1u2u3() but only 
get passed 2 args.  Hmm, I don't understand how i_[d]m[ft]c0() invocations 
used to work before since they're alsway passing only 2 opcode args where 3 
are requiered...
    Ah, that must be due to those tricky macros above -- with commas inside.
David, then this trickery is unacceptable -- add the needed macro instead; and 
there's no need to use i_M[FT]C0() on a 32-bit only CPU, just use i_m[ft]c0().

> +    i_ori(p, K0, K0, (1<<14));
> +
> +    **p = MTC0(K0, C0_CONFIG, 7);
> +    (*p)++;

    So, this also won't do.

[...]

WBR, Sergei

  parent reply	other threads:[~2007-07-19 17:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 15:24 [PATCH] Fix known HW bug with MIPS core on NXP/Philips PNX8550 Daniel Laird
2007-07-19 15:28 ` Jan-Benedict Glaw
2007-07-19 15:31 ` Maciej W. Rozycki
2007-07-19 16:28 ` Thiemo Seufer
2007-07-19 17:32 ` Sergei Shtylyov [this message]
2007-07-19 20:16   ` danieljlaird
2007-07-19 20:16     ` danieljlaird
  -- strict thread matches above, loose matches on Subject: below --
2007-07-19 14:19 Daniel Laird

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=469FA03E.7070209@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=daniel.j.laird@nxp.com \
    --cc=linux-mips@linux-mips.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