public inbox for linux-kernel@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>,
	"daniel.vetter@intel.com" <daniel.vetter@intel.com>,
	"airlied@redhat.com" <airlied@redhat.com>,
	"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>,
	"l.stach@pengutronix.de" <l.stach@pengutronix.de>,
	"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:07:50 +0000	[thread overview]
Message-ID: <6da84ff10e7b34f1b08ac26136aaa325fb91a440.camel@synopsys.com> (raw)
In-Reply-To: <20180709135409.GQ2476@hirez.programming.kicks-ass.net>

Hi Peter,

On Mon, 2018-07-09 at 15:54 +0200, Peter Zijlstra wrote:
> On Mon, Jul 09, 2018 at 04:45:50PM +0300, Alexey Brodkin wrote:
> > diff --git a/drivers/base/devres.c b/drivers/base/devres.c
> > index f98a097e73f2..d65327cb83c9 100644
> > --- 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[];
> >  };
> 
> From a quick reading in Documentation/driver-model/devres.txt this
> devres muck is supposed to be device memory, right?
> 
> atomics (as in atomic*_t) are not defined for use on mmio.
> 
> wth kind of code is relying on this?

It's Etnaviv (GPU/DRM) driver in etnaviv_gpu_platform_probe(),
see https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/etnaviv/etnaviv_gpu.c#L1740:
---------------------->8---------------------
	struct drm_gpu_scheduler {
		...
		atomic64_t			job_id_count;
		...
	};

	struct etnaviv_gpu {
		...
		struct drm_gpu_scheduler	sched;
	};

	struct etnaviv_gpu *gpu;

	gpu = devm_kzalloc(dev, sizeof(*gpu), GFP_KERNEL);
---------------------->8---------------------

-Alexey

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

Thread overview: 19+ 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:54 ` Peter Zijlstra
2018-07-09 14:04   ` Mark Rutland
2018-07-09 14:10     ` Geert Uytterhoeven
2018-07-09 14:07   ` Alexey Brodkin [this message]
2018-07-09 14:07 ` Peter Zijlstra
2018-07-09 14:10   ` Peter Zijlstra
2018-07-09 14:33     ` Alexey Brodkin
2018-07-09 14:49       ` Peter Zijlstra
2018-07-09 14:53         ` Alexey Brodkin
2018-10-04 16:19           ` Alexey Brodkin
2018-07-09 15:02         ` David Laight
2018-07-09 15:14           ` Peter Zijlstra
2018-07-09 15:29         ` Mark Rutland
2018-07-09 15:34           ` Peter Zijlstra
2018-07-09 15:45             ` Peter Zijlstra
2018-07-09 15:48               ` Mark Rutland
2018-07-09 16:10                 ` David Laight
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=6da84ff10e7b34f1b08ac26136aaa325fb91a440.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@intel.com \
    --cc=geert@linux-m68k.org \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=l.stach@pengutronix.de \
    --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