From: Ingo Molnar <mingo@kernel.org>
To: "Yan, Zheng" <zheng.z.yan@intel.com>
Cc: linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl
Subject: Re: [PATCH] perf/x86/uncore: Handle pci_read_config_dword() error.
Date: Wed, 24 Oct 2012 10:58:13 +0200 [thread overview]
Message-ID: <20121024085813.GA2509@gmail.com> (raw)
In-Reply-To: <1351068140-13456-1-git-send-email-zheng.z.yan@intel.com>
* Yan, Zheng <zheng.z.yan@intel.com> wrote:
> From: "Yan, Zheng" <zheng.z.yan@intel.com>
>
> Signed-off-by: Yan, Zheng <zheng.z.yan@intel.com>
> ---
> arch/x86/kernel/cpu/perf_event_intel_uncore.c | 43 +++++++++++++++++----------
> 1 file changed, 28 insertions(+), 15 deletions(-)
Thanks, nice fixes.
Was this runtime tested on a real Sandy Bridge-EP et al CPU so
that we know that it does not regress anything?
Thanks,
Ingo
next prev parent reply other threads:[~2012-10-24 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 8:42 [PATCH] perf/x86/uncore: Handle pci_read_config_dword() error Yan, Zheng
2012-10-24 8:58 ` Ingo Molnar [this message]
2012-10-24 8:59 ` Yan, Zheng
2012-10-24 10:11 ` [tip:perf/urgent] perf/x86/uncore: Handle pci_read_config_dword() errors tip-bot for Yan, Zheng
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=20121024085813.GA2509@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=zheng.z.yan@intel.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).