From: "Antonov, Alexander" <alexander.antonov@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, acme@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, linux-kernel@vger.kernel.org,
eranian@google.com, bgregg@netflix.com, ak@linux.intel.com,
kan.liang@linux.intel.com, lkp@intel.com
Subject: Re: [PATCH v10 0/3] perf x86: Exposing IO stack to IO PMON mapping through sysfs
Date: Mon, 8 Jun 2020 11:00:38 +0300 [thread overview]
Message-ID: <8ffcdb0d-1f2d-1a64-63d8-8064ee42afc3@linux.intel.com> (raw)
In-Reply-To: <20200605175314.GQ2750@hirez.programming.kicks-ass.net>
Hi Peter,
Greg Kroah-Hartman had comments for earlier versions of this patch set.
All his comments were addressed, for example in according his remarks
the mapping procedure was reworked to use attr_update flow for new
optional attributes. Also the way of exposing of I/O stacks through
sysfs was redesigned to show up a single file for each mapping of IIO
PMON block to die.
Thanks,
Alexander
On 6/5/2020 8:53 PM, Peter Zijlstra wrote:
> On Mon, Jun 01, 2020 at 11:35:40AM +0300, alexander.antonov@linux.intel.com wrote:
>
> Didn't GregKH have comments on earlier versions of these patches? I
> don't see him on Cc anymore. Were all his comments addressed?
prev parent reply other threads:[~2020-06-08 8:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 8:35 alexander.antonov
2020-06-01 8:35 ` [PATCH v10 1/3] perf/x86/intel/uncore: Expose an Uncore unit to PMON mapping alexander.antonov
2020-06-16 12:21 ` [tip: perf/core] " tip-bot2 for Roman Sudarikov
2020-06-01 8:35 ` [PATCH v10 2/3] perf/x86/intel/uncore: Wrap the max dies calculation into an accessor alexander.antonov
2020-06-16 12:21 ` [tip: perf/core] " tip-bot2 for Roman Sudarikov
2020-06-01 8:35 ` [PATCH v10 3/3] perf/x86/intel/uncore: Expose an Uncore unit to IIO PMON mapping alexander.antonov
2020-06-16 12:21 ` [tip: perf/core] " tip-bot2 for Roman Sudarikov
2020-06-05 17:53 ` [PATCH v10 0/3] perf x86: Exposing IO stack to IO PMON mapping through sysfs Peter Zijlstra
2020-06-05 20:39 ` Andi Kleen
2020-06-08 8:00 ` Antonov, Alexander [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=8ffcdb0d-1f2d-1a64-63d8-8064ee42afc3@linux.intel.com \
--to=alexander.antonov@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bgregg@netflix.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
Powered by JetHome