From: Joshua Kinard <kumba@gentoo.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Linux MIPS List <linux-mips@linux-mips.org>
Subject: [PATCH]: MIPS: oprofile: Distinguish R14000 from R12000
Date: Mon, 25 May 2015 00:15:21 -0400 [thread overview]
Message-ID: <5562A1D9.2080400@gentoo.org> (raw)
From: Joshua Kinard <kumba@gentoo.org>
Currently, arch/mips/oprofile/op_model_mipsxx.c treats an R14000 as an
R12000. This patch distinguishes one from the other.
Signed-off-by: Joshua Kinard <kumba@gentoo.org>
---
op_model_mipsxx.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
linux-mips-oprofile-fix-r14k.patch
diff --git a/arch/mips/oprofile/op_model_mipsxx.c b/arch/mips/oprofile/op_model_mipsxx.c
index 6a6e2cc..75f1967 100644
--- a/arch/mips/oprofile/op_model_mipsxx.c
+++ b/arch/mips/oprofile/op_model_mipsxx.c
@@ -408,10 +408,13 @@ static int __init mipsxx_init(void)
break;
case CPU_R12000:
- case CPU_R14000:
op_model_mipsxx_ops.cpu_type = "mips/r12000";
break;
+ case CPU_R14000:
+ op_model_mipsxx_ops.cpu_type = "mips/r14000";
+ break;
+
case CPU_R16000:
op_model_mipsxx_ops.cpu_type = "mips/r16000";
break;
next reply other threads:[~2015-05-25 4:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 4:15 Joshua Kinard [this message]
2015-06-01 16:15 ` [PATCH]: MIPS: oprofile: Distinguish R14000 from R12000 Ralf Baechle
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=5562A1D9.2080400@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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