From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: roman.sudarikov@linux.intel.com, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org, mark.rutland@arm.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
Cc: alexander.antonov@intel.com, roman.sudarikov@linux.intel.com,
alexander.shishkin@linux.intel.com
Subject: Re: [PATCH v8 2/3] perf x86: Topology max dies for whole system
Date: Fri, 27 Mar 2020 10:01:23 +0200 [thread overview]
Message-ID: <87bloi6xbg.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20200320073110.4761-3-roman.sudarikov@linux.intel.com>
roman.sudarikov@linux.intel.com writes:
> From: Roman Sudarikov <roman.sudarikov@linux.intel.com>
>
> Helper function to return number of dies on the platform.
It's not a function though, it's a macro. And maybe more of an
"accessor" than a "helper".
It's also good to mention in the commit message, why this change is
needed and sometimes (though maybe not here) why this way is better than
the alternatives.
Another thing about the subject line is that it has to describe the
action that the patch is taking, in imperative mood. In this case it
could be "Turn the max die calculation into a function".
The prefix of the subject line should be: perf/x86/intel/uncore. Check
out git log arch/x86/events/intel/uncore.c for examples.
I also think that it won't be unreasonable to fold this patch into the
next one. That's up to you, of course.
Regards,
--
Alex
next prev parent reply other threads:[~2020-03-27 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 7:31 [PATCH v8 0/3] perf x86: Exposing IO stack to IO PMON mapping through sysfs roman.sudarikov
2020-03-20 7:31 ` [PATCH v8 1/3] perf x86: Infrastructure for exposing an Uncore unit to PMON mapping roman.sudarikov
2020-03-24 20:28 ` Sudarikov, Roman
2020-03-27 8:23 ` Alexander Shishkin
2020-03-20 7:31 ` [PATCH v8 2/3] perf x86: Topology max dies for whole system roman.sudarikov
2020-03-27 8:01 ` Alexander Shishkin [this message]
2020-03-20 7:31 ` [PATCH v8 3/3] perf x86: Exposing an Uncore unit to PMON for Intel Xeon® server platform roman.sudarikov
2020-03-27 8:47 ` Alexander Shishkin
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=87bloi6xbg.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.antonov@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=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=roman.sudarikov@linux.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
all inboxes | Powered by JetHome®