From: Borislav Petkov <bp@suse.de>
To: sherry hurwitz <sherry.hurwitz@amd.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
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>
Subject: Re: [BUG/RFC] perf test fails on AMD CPUs
Date: Thu, 10 Dec 2015 20:26:36 +0100 [thread overview]
Message-ID: <20151210192636.GA3822@pd.tnic> (raw)
In-Reply-To: <55DB9C9D.7020003@amd.com>
On Mon, Aug 24, 2015 at 05:37:17PM -0500, sherry hurwitz wrote:
Hey Sherry,
> I have duplicated your problem and asked the HW architect that wrote
> 832 to review the diff between the 822 and 832 microcode patch.
were there any updates to this issue in the meantime?
Thanks.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
prev parent reply other threads:[~2015-12-10 19:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 22:29 [BUG/RFC] perf test fails on AMD CPUs 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
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 [this message]
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=20151210192636.GA3822@pd.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 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.