public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "peterz@infradead.org" <peterz@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"greg@kroah.com" <greg@kroah.com>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"David.Laight@ACULAB.COM" <David.Laight@ACULAB.COM>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"geert@linux-m68k.org" <geert@linux-m68k.org>
Subject: Re: [PATCH v3] devres: Explicitly align datai[] to 64-bit
Date: Mon, 9 Jul 2018 14:33:26 +0000	[thread overview]
Message-ID: <44727d3cebda7bee5b68fb388bd2fecfc6dc7b89.camel@synopsys.com> (raw)
In-Reply-To: <20180709141056.GR2512@hirez.programming.kicks-ass.net>

Hi Peter,

On Mon, 2018-07-09 at 16:10 +0200, Peter Zijlstra wrote:
> On Mon, Jul 09, 2018 at 04:07:17PM +0200, Peter Zijlstra wrote:
> > On Mon, Jul 09, 2018 at 04:45:50PM +0300, Alexey Brodkin wrote:
> > > --- a/drivers/base/devres.c
> > > +++ b/drivers/base/devres.c
> > > @@ -24,8 +24,12 @@ struct devres_node {
> > >  
> > >  struct devres {
> > >  	struct devres_node		node;
> > > -	/* -- 3 pointers */
> > > -	unsigned long long		data[];	/* guarantee ull alignment */
> > > +	/*
> > > +	 * data[] must be 64 bit aligned even on 32 bit architectures
> > > +	 * because it might be accessed by instructions that require
> > > +	 * aligned memory arguments such as atomic64_t.
> > > +	 */
> > > +	u8 __aligned(8)			data[];
> > >  };
> > 
> > Seeing that this ends up in a semi generic allocation thing, I don't
> > feel this should be different from ARCH_KMALLOC_MINALIGN.
> 
> In fact, since alloc_dr() uses kmalloc() to allocate the entire thing,
> it is impossible to guarantee a larger alignment than kmalloc does.

Well but 4-bytes [which is critical for atomic64_t] should be much less
than a sane cache line length so above should work.

-Alexey

  parent reply	other threads:[~2018-07-09 14:33 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-09 13:45 [PATCH v3] devres: Explicitly align datai[] to 64-bit Alexey Brodkin
2018-07-09 13:45 ` Alexey Brodkin
2018-07-09 13:54 ` Peter Zijlstra
2018-07-09 13:54   ` Peter Zijlstra
2018-07-09 14:04   ` Mark Rutland
2018-07-09 14:04     ` Mark Rutland
2018-07-09 14:10     ` Geert Uytterhoeven
2018-07-09 14:10       ` Geert Uytterhoeven
2018-07-09 14:07   ` Alexey Brodkin
2018-07-09 14:07     ` Alexey Brodkin
2018-07-09 14:07 ` Peter Zijlstra
2018-07-09 14:07   ` Peter Zijlstra
2018-07-09 14:10   ` Peter Zijlstra
2018-07-09 14:10     ` Peter Zijlstra
2018-07-09 14:33     ` Alexey Brodkin [this message]
2018-07-09 14:33       ` Alexey Brodkin
2018-07-09 14:49       ` Peter Zijlstra
2018-07-09 14:49         ` Peter Zijlstra
2018-07-09 14:53         ` Alexey Brodkin
2018-07-09 14:53           ` Alexey Brodkin
2018-10-04 16:19           ` Alexey Brodkin
2018-10-04 16:19             ` Alexey Brodkin
2018-07-09 15:02         ` David Laight
2018-07-09 15:02           ` David Laight
2018-07-09 15:14           ` Peter Zijlstra
2018-07-09 15:14             ` Peter Zijlstra
2018-07-09 15:29         ` Mark Rutland
2018-07-09 15:29           ` Mark Rutland
2018-07-09 15:34           ` Peter Zijlstra
2018-07-09 15:34             ` Peter Zijlstra
2018-07-09 15:45             ` Peter Zijlstra
2018-07-09 15:45               ` Peter Zijlstra
2018-07-09 15:48               ` Mark Rutland
2018-07-09 15:48                 ` Mark Rutland
2018-07-09 16:10                 ` David Laight
2018-07-09 16:10                   ` David Laight
2018-07-09 20:28                   ` Vineet Gupta
2018-07-09 20:28                     ` Vineet Gupta

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=44727d3cebda7bee5b68fb388bd2fecfc6dc7b89.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=geert@linux-m68k.org \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@arm.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