From: David Laight <David.Laight@ACULAB.COM>
To: "'Christophe Leroy'" <christophe.leroy@c-s.fr>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"scottwood@freescale.com" <scottwood@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 07/11] powerpc/8xx: macro for handling CPU15 errata
Date: Tue, 20 Jan 2015 11:09:08 +0000 [thread overview]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6D1CACEFD9@AcuExch.aculab.com> (raw)
In-Reply-To: <20150120095735.A55671A5E86@localhost.localdomain>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1405 bytes --]
>From Christophe Leroy
> Having a macro will help keep clear code.
It might remove an #if but it doesn't really help.
All it means is that anyone reading the code has to hunt for
the definition before proceeding.
Some comment about what (and why) the extra code is needed
might help.
...
> +
> +#ifdef CONFIG_8xx_CPU15
> +#define DO_8xx_CPU15(tmp, addr) \
> + addi tmp, addr, PAGE_SIZE; \
> + tlbie tmp; \
> + addi tmp, addr, PAGE_SIZE; \
You've even transcribed this incorrectly.
Clearly not tested :-)
David
> + tlbie tmp
> +#else
> +#define DO_8xx_CPU15(tmp, addr)
> +#endif
> +
> InstructionTLBMiss:
> #ifdef CONFIG_8xx_CPU6
> mtspr SPRN_DAR, r3
> @@ -304,12 +315,7 @@ InstructionTLBMiss:
> EXCEPTION_PROLOG_0
> mtspr SPRN_SPRG_SCRATCH2, r10
> mfspr r10, SPRN_SRR0 /* Get effective address of fault */
> -#ifdef CONFIG_8xx_CPU15
> - addi r11, r10, PAGE_SIZE
> - tlbie r11
> - addi r11, r10, -PAGE_SIZE
> - tlbie r11
> -#endif
> + DO_8xx_CPU15(r11, r10)
>
> /* If we are faulting a kernel address, we have to use the
> * kernel page tables.
> --
> 2.1.0
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2015-01-20 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 9:57 Christophe Leroy
2015-01-20 11:09 ` David Laight [this message]
2015-01-20 11:32 ` leroy christophe
2015-01-20 11:43 ` David Laight
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=063D6719AE5E284EB5DD2968C1650D6D1CACEFD9@AcuExch.aculab.com \
--to=david.laight@aculab.com \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
/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®