From: Borislav Petkov <bp@suse.de>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>, Robert Richter <rric@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Jan Stancek <jstancek@redhat.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Sherry Hurwitz <sherry.hurwitz@amd.com>
Subject: Re: [BUG/RFC] perf test fails on AMD CPUs
Date: Wed, 19 Aug 2015 05:55:19 +0200 [thread overview]
Message-ID: <20150819035519.GA31385@nazgul.tnic> (raw)
In-Reply-To: <20150818101025.GA15340@krava.brq.redhat.com>
On Tue, Aug 18, 2015 at 12:10:25PM +0200, Jiri Olsa wrote:
> buuuuuut anyway, it looks like latest AMD firmware issue:
>
> [root@amd-pike-07 ~]# cat /sys/devices/system/cpu/cpu0/microcode/version
> 0x6000822
> [root@amd-pike-07 perf]# ./perf test 18
> 18: Test breakpoint overflow signal handler : Ok
>
> [root@amd-pike-07 perf]# cat /sys/devices/system/cpu/cpu0/microcode/version
> 0x6000832
> [root@amd-pike-07 perf]# ./perf test 18
> 18: Test breakpoint overflow signal handler : FAILED!
>
>
> [root@amd-pike-07 ~]# cat /proc/cpuinfo
> processor : 7
> vendor_id : AuthenticAMD
> cpu family : 21
> model : 2
> model name : AMD Opteron(tm) Processor 3380
> stepping : 0
> microcode : 0x6000832
>
> SNIP
Whoops.
Can you please confirm with your debugging code that with version
0x6000822 EFLAGS.RF is set and with 0x6000832 it isn't when running the
aforementioned test?
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2015-08-19 3:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 22:29 Jiri Olsa
2015-08-17 4:36 ` Borislav Petkov
2015-08-17 7:33 ` Jiri Olsa
2015-08-17 16:06 ` Andy Lutomirski
2015-08-18 8:52 ` Borislav Petkov
2015-08-18 10:10 ` Jiri Olsa
2015-08-19 3:55 ` Borislav Petkov [this message]
2015-08-19 8:55 ` Jiri Olsa
2015-08-19 15:47 ` Borislav Petkov
2015-08-19 15:58 ` Jiri Olsa
2015-08-19 16:12 ` Borislav Petkov
2015-08-21 7:45 ` Jiri Olsa
2015-08-24 22:37 ` sherry hurwitz
2015-12-10 19:26 ` Borislav Petkov
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=20150819035519.GA31385@nazgul.tnic \
--to=bp@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=rric@kernel.org \
--cc=sherry.hurwitz@amd.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®