From: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>
To: Dave Hansen <dave.hansen@intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Ingo Molnar <mingo@kernel.org>, Vlastimil Babka <vbabka@suse.cz>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Anshuman Khandual <anshuman.khandual@arm.com>
Subject: Re: [PATCH V2] fork: Improve error message for corrupted page tables
Date: Tue, 06 Aug 2019 11:30:02 -0700 [thread overview]
Message-ID: <9a09db3d4827bc6bf49c4579d495d71015f2c5a6.camel@intel.com> (raw)
In-Reply-To: <73b77479-cdd2-6d53-14ae-25ec4c4c3d25@intel.com>
On Tue, 2019-08-06 at 09:30 -0700, Dave Hansen wrote:
> On 8/5/19 8:05 PM, Sai Praneeth Prakhya wrote:
> > +static const char * const resident_page_types[NR_MM_COUNTERS] = {
> > + [MM_FILEPAGES] = "MM_FILEPAGES",
> > + [MM_ANONPAGES] = "MM_ANONPAGES",
> > + [MM_SWAPENTS] = "MM_SWAPENTS",
> > + [MM_SHMEMPAGES] = "MM_SHMEMPAGES",
> > +};
>
> One trick to ensure that this gets updated if the names are ever
> updated. You can do:
>
> #define NAMED_ARRAY_INDEX(x) [x] = __stringify(x),
>
> and
>
> static const char * const resident_page_types[NR_MM_COUNTERS] = {
> NAMED_ARRAY_INDEX(MM_FILE_PAGES),
> NAMED_ARRAY_INDEX(MM_SHMEMPAGES),
> ...
> };
Thanks for the suggestion Dave. I will add this in V3.
Even with this, (if ever) anyone who changes the name of page types or adds an
new entry would still need to update struct resident_page_types[]. So, I will
add the comment as suggested by Vlastimil.
>
> That makes sure that any name changes make it into the strings. Then
> stick a:
>
> BUILD_BUG_ON(NR_MM_COUNTERS != ARRAY_SIZE(resident_page_types));
>
> somewhere. That makes sure that any new array indexes get a string
> added in the array. Otherwise you get nice, early, compile-time errors.
Sure! this sounds good and a small nit-bit :)
For the BUILD_BUG_ON() to work, the definition of struct should be changed as
below
static const char * const resident_page_types[] = {
...
}
i.e. we should not specify the size of array.
Regards,
Sai
prev parent reply other threads:[~2019-08-06 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 3:05 Sai Praneeth Prakhya
2019-08-06 7:53 ` Vlastimil Babka
2019-08-06 8:32 ` Anshuman Khandual
2019-08-06 16:11 ` Prakhya, Sai Praneeth
2019-08-06 16:10 ` Prakhya, Sai Praneeth
2019-08-06 8:36 ` Michal Hocko
2019-08-06 21:21 ` Sai Praneeth Prakhya
2019-08-06 16:30 ` Dave Hansen
2019-08-06 18:30 ` Sai Praneeth Prakhya [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=9a09db3d4827bc6bf49c4579d495d71015f2c5a6.camel@intel.com \
--to=sai.praneeth.prakhya@intel.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=vbabka@suse.cz \
/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