From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] irqchip: irq-mvebu-odmi: new driver for platform MSI on Marvell 7K/8K
Date: Fri, 19 Feb 2016 10:35:35 +0100 [thread overview]
Message-ID: <20160219103535.28062901@free-electrons.com> (raw)
In-Reply-To: <56C5F433.8010701@arm.com>
Marc,
On Thu, 18 Feb 2016 16:41:23 +0000, Marc Zyngier wrote:
> It looks really nice, except for a couple of points, see below.
Thanks again for the review.
> > +/*
> > + * We don't support the group events, so we simply have 8 interrupts
> > + * per frame.
> > + */
> > +#define NODMIS_PER_FRAME 8
> > +#define NODMIS_SHIFT 3
> > +#define NODMIS_MASK 7
>
> All these values are directly related, so it would be nice if they would
> be expressed in term of each other:
>
> #define NODMIS_SHIFT 3
> #define NODMIS_PER_FRAME (1 << NODMIS_SHIFT)
> #define NODMIS_MASK (NODMIS_PER_FRAME - 1)
Good point, will do.
> > + odmis_bm = kzalloc(odmis_count * NODMIS_PER_FRAME / BITS_PER_BYTE,
> > + GFP_KERNEL);
>
> Blah. this will allocate the exact number of bytes, which you will then
> access as longs, touching memory that's not yours in the process (I've
> been recently bitten and publicly shamed...).
Aah, yes.
> Consider the following:
>
> odmis_bm = kzalloc(BITS_TO_LONGS(odmis_count * NODMIS_PER_FRAME) *
> sizeof(long), GFP_KERNEL);
Will do.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
linux-kernel@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Nadav Haklai <nadavh@marvell.com>,
Lior Amsalem <alior@marvell.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] irqchip: irq-mvebu-odmi: new driver for platform MSI on Marvell 7K/8K
Date: Fri, 19 Feb 2016 10:35:35 +0100 [thread overview]
Message-ID: <20160219103535.28062901@free-electrons.com> (raw)
In-Reply-To: <56C5F433.8010701@arm.com>
Marc,
On Thu, 18 Feb 2016 16:41:23 +0000, Marc Zyngier wrote:
> It looks really nice, except for a couple of points, see below.
Thanks again for the review.
> > +/*
> > + * We don't support the group events, so we simply have 8 interrupts
> > + * per frame.
> > + */
> > +#define NODMIS_PER_FRAME 8
> > +#define NODMIS_SHIFT 3
> > +#define NODMIS_MASK 7
>
> All these values are directly related, so it would be nice if they would
> be expressed in term of each other:
>
> #define NODMIS_SHIFT 3
> #define NODMIS_PER_FRAME (1 << NODMIS_SHIFT)
> #define NODMIS_MASK (NODMIS_PER_FRAME - 1)
Good point, will do.
> > + odmis_bm = kzalloc(odmis_count * NODMIS_PER_FRAME / BITS_PER_BYTE,
> > + GFP_KERNEL);
>
> Blah. this will allocate the exact number of bytes, which you will then
> access as longs, touching memory that's not yours in the process (I've
> been recently bitten and publicly shamed...).
Aah, yes.
> Consider the following:
>
> odmis_bm = kzalloc(BITS_TO_LONGS(odmis_count * NODMIS_PER_FRAME) *
> sizeof(long), GFP_KERNEL);
Will do.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-19 9:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 15:58 [PATCH v2] irqchip: irq-mvebu-odmi: new driver for platform MSI on Marvell 7K/8K Thomas Petazzoni
2016-02-18 15:58 ` Thomas Petazzoni
2016-02-18 16:08 ` Arnd Bergmann
2016-02-18 16:08 ` Arnd Bergmann
2016-02-18 16:16 ` Thomas Petazzoni
2016-02-18 16:16 ` Thomas Petazzoni
2016-02-18 16:27 ` Arnd Bergmann
2016-02-18 16:27 ` Arnd Bergmann
2016-02-18 16:41 ` Marc Zyngier
2016-02-18 16:41 ` Marc Zyngier
2016-02-19 9:35 ` Thomas Petazzoni [this message]
2016-02-19 9:35 ` Thomas Petazzoni
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=20160219103535.28062901@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.