From: Andreas Barth <aba@not.so.argh.org>
To: Wu Zhangjin <wuzhangjin@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH v3 1/3] Loongson-2F: Flush the branch target history such as BTB and RAS
Date: Fri, 2 Apr 2010 16:54:01 +0200 [thread overview]
Message-ID: <20100402145401.GS27216@mails.so.argh.org> (raw)
In-Reply-To: <05e2ba2596f23fa4dda64d63ce2480504b1be4ac.1268453720.git.wuzhangjin@gmail.com>
* Wu Zhangjin (wuzhangjin@gmail.com) [100313 05:45]:
> This patch did clear BTB(branch target buffer), forbid RAS(return
> address stack) via Loongson-2F's 64bit diagnostic register.
Unfortunatly the Loongson 2F here still fails with this patch,
compiled with the new binutils and both options enabled.
Testcase: plain debian unstable chroot, build binutils in that chroot.
More ideas, codes, whatever welcome.
Andi
next prev parent reply other threads:[~2010-04-02 15:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 4:34 [PATCH v3 0/3] Workaround the Out-of-order Issue of Loongson-2F Wu Zhangjin
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 [this message]
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=20100402145401.GS27216@mails.so.argh.org \
--to=aba@not.so.argh.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).