linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: akpm@linux-foundation.org, a.p.zijlstra@chello.nl,
	xemul@parallels.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: + procfs-add-vmflags-field-in-smaps-output-v3-fix-2.patch added to -mm tree
Date: Wed, 24 Oct 2012 13:59:59 +0400	[thread overview]
Message-ID: <20121024095959.GA30240@moon> (raw)
In-Reply-To: <20121024204746.8a8c0fa14b6495b5d5013db4@canb.auug.org.au>

On Wed, Oct 24, 2012 at 08:47:46PM +1100, Stephen Rothwell wrote:
> Hi Cyrill,
> 
> On Wed, 24 Oct 2012 12:45:15 +0400 Cyrill Gorcunov <gorcunov@openvz.org> wrote:
> >
> >  static void show_smap_vma_flags(struct seq_file *m, struct vm_area_struct *vma)
> >  {
> > +#define __VM_FLAG(_f, _s)	[ilog2(_f)] = {(const char [2]){_s}}
> 
> I really don't think you need the cast (and it may hide bad usages) or
> the second set of braces.  Thus:

Hi Stephen, could you please elaborate, which bad usage hiding could be there?

> Further is there any reason for the struct?
> 
> #define __VM_FLAG(_f, _s)	[ilog2(_f)] = _s
> 
> static const char mnemonics[BITS_PER_LONG][2] = {
> ...
> };

Well, good point, though the benefit of using stucture here
could be easier way for extension if needed. The compiled result
is the same as for plain array or structure, so I would rather
stick with struct here, until contrary proved (I mean it's not
a problem to update the patch and use array here but I still
think struct it better in long term). If you guys think that I
should move it to array -- no problem, i may update ;)

> >  	seq_puts(m, "VmFlags: ");
> >  	for (i = 0; i < BITS_PER_LONG; i++) {
> > -		if (vma->vm_flags & (1 << i))
> > +		if (vma->vm_flags & (1ul << i)) {
> >  			seq_printf(m, "%c%c ",
> >  				   mnemonics[i].l[0],
> >  				   mnemonics[i].l[1]);
> 
> 				   mnemonics[i][0], mnemonics[i][1]
> 
> /me looks for another bike shed :-)

Heh :)

  reply	other threads:[~2012-10-24 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121023220300.1185C200057@hpza10.eem.corp.google.com>
2012-10-24  8:45 ` + procfs-add-vmflags-field-in-smaps-output-v3-fix-2.patch added to -mm tree Cyrill Gorcunov
2012-10-24  9:24   ` Peter Zijlstra
2012-10-24  9:49     ` Cyrill Gorcunov
2012-10-24  9:47   ` Stephen Rothwell
2012-10-24  9:59     ` Cyrill Gorcunov [this message]
2012-10-24 10:26       ` Stephen Rothwell
2012-10-24 10:39         ` Cyrill Gorcunov

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=20121024095959.GA30240@moon \
    --to=gorcunov@openvz.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=xemul@parallels.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).