linux-kernel - Re: [PATCH v8 2/3] perf x86: Topology max dies for whole system

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87bloi6xbg.fsf@ashishki-desk.ger.corp.intel.com>
Date:   Fri, 27 Mar 2020 10:01:23 +0200
From:   Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To:     roman.sudarikov@...ux.intel.com, peterz@...radead.org,
        mingo@...hat.com, acme@...nel.org, mark.rutland@....com,
        jolsa@...hat.com, namhyung@...nel.org,
        linux-kernel@...r.kernel.org, eranian@...gle.com,
        bgregg@...flix.com, ak@...ux.intel.com, kan.liang@...ux.intel.com
Cc:     alexander.antonov@...el.com, roman.sudarikov@...ux.intel.com,
        alexander.shishkin@...ux.intel.com
Subject: Re: [PATCH v8 2/3] perf x86: Topology max dies for whole system

roman.sudarikov@...ux.intel.com writes:

> From: Roman Sudarikov <roman.sudarikov@...ux.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