From: Wu Zhangjin <wuzhangjin@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org,
Shinya Kuribayashi <shinya.kuribayashi@necel.com>,
Wu Zhangjin <wuzhangjin@gmail.com>
Subject: [PATCH v3 0/3] Workaround the Out-of-order Issue of Loongson-2F
Date: Sat, 13 Mar 2010 12:34:14 +0800 [thread overview]
Message-ID: <cover.1268453720.git.wuzhangjin@gmail.com> (raw)
From: Wu Zhangjin <wuzhangjin@gmail.com>
Hi, Ralf
Is that possible to apply this patchset for both 2.6.33(the stable release) and
2.6.34? then we can get a not broken support for loongson-2f with the
options(-mfix-loongson2f-nop, -mfix-loongson2f-jump) provided by the latest
binutils (>=2.20.1).
Thanks & Regards,
Wu Zhangjin
-------
Changes:
v2->v3:
o Herein, RAS is short for Return Address Stack not Row Address Strobe, at
the same time, the "model" in the translation of Chapter 15 should be "mode".
(feedback from Shinya Kuribayashi)
v1->v2:
o Cleanup some comments and align some instructions.
----
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:
o When switching from user mode to kernel mode, you should flush the branch
target history such as BTB and RAS.
o Doing some tricks to the indirect branch target to make sure that the
indirect branch target can not be in the I/O region.
This patchset applied the above methods and for the binutils patch[3] have been
merged into binutils 2.20.1, so, it's time to upstream this patchset now.
without this patch, the machines will hang when the instruction sequence hit
the Out-of-order Issue of Loongson-2F, therefore, this patchset is very urgent
for both 2.6.33 and 2.6.34.
[1] Chinese Version: http://www.loongson.cn/uploadfile/file/20080821113149.pdf
[2] English Version of Chapter 15:
http://groups.google.com.hk/group/loongson-dev/msg/e0d2e220958f10a6?dmode=source
[3] http://sourceware.org/ml/binutils/2009-11/msg00387.html
Regards,
Wu Zhangjin
Wu Zhangjin (3):
Loongson-2F: Flush the branch target history such as BTB and RAS
Loongson-2F: Enable fixups of binutils 2.20.1
Loongson-2F: Fixup of problems introduced by -mfix-loongson2f-jump of
binutils 2.20.1
arch/mips/Makefile | 4 +++-
arch/mips/include/asm/stackframe.h | 19 +++++++++++++++++++
arch/mips/loongson/common/reset.c | 11 ++++++++++-
3 files changed, 32 insertions(+), 2 deletions(-)
next reply other threads:[~2010-03-13 4:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 4:34 Wu Zhangjin [this message]
2010-03-13 4:34 ` [PATCH v3 1/3] Loongson-2F: Flush the branch target history such as BTB and RAS Wu Zhangjin
2010-03-17 15:11 ` Ralf Baechle
2010-04-02 14:54 ` Andreas Barth
2010-04-03 1:42 ` Wu Zhangjin
2010-04-06 19:10 ` Andreas Barth
2010-04-07 7:30 ` Wu Zhangjin
2010-04-10 8:10 ` Andreas Barth
2010-04-12 3:33 ` Wu Zhangjin
2010-04-03 1:53 ` Zhang Le
2010-04-03 3:11 ` Andreas Barth
2010-03-13 4:34 ` [PATCH v3 2/3] Loongson-2F: Enable fixups of binutils 2.20.1 Wu Zhangjin
2010-03-17 13:52 ` Ralf Baechle
2010-03-27 16:29 ` Zhang Le
2010-03-27 17:20 ` Zhang Le
2010-03-27 23:17 ` zhangfx
2010-04-07 13:02 ` Wu Zhangjin
2010-03-13 4:34 ` [PATCH v3 3/3] Loongson-2F: Fixup of problems introduced by -mfix-loongson2f-jump " Wu Zhangjin
2010-03-17 15:02 ` Ralf Baechle
2010-03-27 17:13 ` Zhang Le
2010-04-07 12:57 ` 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=cover.1268453720.git.wuzhangjin@gmail.com \
--to=wuzhangjin@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=shinya.kuribayashi@necel.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 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.