From: Shinya Kuribayashi <shinya.kuribayashi@necel.com>
To: Wu Zhangjin <wuzhangjin@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, Greg KH <gregkh@suse.de>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Loongson-2F: Flush the branch target history such as BTB and RAS
Date: Thu, 11 Mar 2010 12:27:42 +0900 [thread overview]
Message-ID: <4B98632E.70806@necel.com> (raw)
In-Reply-To: <d513f16856e499e82f0b4e428c97fe06afb5a426.1268153722.git.wuzhangjin@gmail.com>
Wu Zhangjin wrote:
> From: Wu Zhangjin <wuzhangjin@gmail.com>
>
> As the Chapter 15: "Errata: Issue of Out-of-order in loongson"[1] shows, to
> workaround the Issue of Loongson-2F,We need to do:
>
> "When switching from user model to kernel model, you should flush the branch
> target history such as BTB and RAS."
Just wondered, model or mode?
> This patch did clear BTB(branch target buffer), forbid RAS(row address strobe)
> via Loongson-2F's 64bit diagnostic register.
Are you sure that RAS represents "Row Address Strobe", not "Return
Address Stack?"
By the way, we have a similar local workaround for vr55xx processors
when switching from kernel mode to user mode. It's not necessarily
related to out-of-order issues, but we need to prevent the processor
from doing instruction prefetch beyond "eret" instruction.
In the long term, it would be appreciated that the kernel has a set
of hooks when switching KUX-modes, so that each machine could have
his own, processor-specific treatmens.
Shinya
> [1] Chinese Version: http://www.loongson.cn/uploadfile/file/200808211
> [2] English Version of Chapter 15:
> http://groups.google.com.hk/group/loongson-dev/msg/e0d2e220958f10a6?dmode=source
>
> Signed-off-by: Wu Zhangjin <wuzhangjin@gmail.com>
> ---
> arch/mips/include/asm/stackframe.h | 19 +++++++++++++++++++
> 1 files changed, 19 insertions(+), 0 deletions(-)
>
> diff --git a/arch/mips/include/asm/stackframe.h b/arch/mips/include/asm/stackframe.h
> index 3b6da33..b84cfda 100644
> --- a/arch/mips/include/asm/stackframe.h
> +++ b/arch/mips/include/asm/stackframe.h
> @@ -121,6 +121,25 @@
> .endm
> #else
> .macro get_saved_sp /* Uniprocessor variation */
> +#ifdef CONFIG_CPU_LOONGSON2F
> + /*
> + * Clear BTB(branch target buffer), forbid RAS(row address
> + * strobe) to workaround the Out-of-oder Issue in Loongson2F
> + * via it's diagnostic register.
> + */
> + move k0, ra
> + jal 1f
> + nop
> +1: jal 1f
> + nop
> +1: jal 1f
> + nop
> +1: jal 1f
> + nop
> +1: move ra, k0
> + li k0, 3
> + mtc0 k0, $22
> +#endif /* CONFIG_CPU_LOONGSON2F */
> #if defined(CONFIG_32BIT) || defined(KBUILD_64BIT_SYM32)
> lui k1, %hi(kernelsp)
> #else
next prev parent reply other threads:[~2010-03-11 3:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 17:12 [PATCH 0/3] Workaround the Out-of-order Issue of Loongson-2F Wu Zhangjin
2010-03-09 17:12 ` [PATCH 1/3] Loongson-2F: Flush the branch target history such as BTB and RAS Wu Zhangjin
2010-03-10 10:44 ` Sergei Shtylyov
2010-03-10 15:24 ` Wu Zhangjin
2010-03-11 3:27 ` Shinya Kuribayashi [this message]
2010-03-11 3:35 ` Wu Zhangjin
2010-03-11 9:59 ` Ralf Baechle
2010-03-13 3:52 ` Wu Zhangjin
2010-03-14 23:42 ` Shinya Kuribayashi
2010-03-09 17:12 ` [PATCH 2/3] Loongson-2F: Enable fixups of binutils 2.20.1 Wu Zhangjin
2010-03-09 17:12 ` [PATCH 3/3] Loongson-2F: Fixup of problems introduced by -mfix-loongson2f-jump " Wu Zhangjin
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=4B98632E.70806@necel.com \
--to=shinya.kuribayashi@necel.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=wuzhangjin@gmail.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;
as well as URLs for NNTP newsgroup(s).