From: David Laight <David.Laight@ACULAB.COM>
To: 'Jose Abreu' <jose.abreu@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Vineet Gupta <vineet.gupta1@synopsys.com>,
Alexey Brodkin <alexey.brodkin@synopsys.com>,
Joao Pinto <joao.pinto@synopsys.com>,
"Vitor Soares" <vitor.soares@synopsys.com>
Subject: RE: [PATCH v2] ARC: io.h: Implement reads{x}()/writes{x}()
Date: Thu, 29 Nov 2018 14:38:59 +0000 [thread overview]
Message-ID: <ff1e11923e92405d883474d715008c0a@AcuMS.aculab.com> (raw)
In-Reply-To: <19fb2e394afcb073bbc109e432417fbbc03323f6.1543499759.git.joabreu@synopsys.com>
From: Jose Abreu
> Sent: 29 November 2018 14:29
>
> Some ARC CPU's do not support unaligned loads/stores. Currently, generic
> implementation of reads{b/w/l}()/writes{b/w/l}() is being used with ARC.
> This can lead to misfunction of some drivers as generic functions do a
> plain dereference of a pointer that can be unaligned.
>
> Let's use {get/put}_unaligned() helper instead of plain dereference of
> pointer in order to fix this.
...
> +#define __raw_readsx(t,f) \
> +static inline void __raw_reads##f(const volatile void __iomem *addr, \
> + void *buffer, unsigned int count) \
> +{ \
> + if (count) { \
> + const unsigned long bptr = (unsigned long)buffer; \
> + u##t *buf = buffer; \
> +\
> + do { \
> + u##t x = __raw_read##f(addr); \
> +\
> + /* Some ARC CPU's don't support unaligned accesses */ \
> + if (bptr % ((t) / 8)) { \
> + put_unaligned(x, buf++); \
> + } else { \
> + *buf++ = x; \
> + } \
> + } while (--count); \
> + } \
> +}
Does the compiler move the alignment test outside the loop?
You really want two copies of the loop body.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2018-11-29 14:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 14:29 Jose Abreu
2018-11-29 14:38 ` David Laight [this message]
2018-11-29 14:42 ` Jose Abreu
2018-11-29 16:13 ` Jose Abreu
2018-11-29 21:20 ` Arnd Bergmann
2018-11-30 8:56 ` Jose Abreu
2018-11-30 13:44 ` Arnd Bergmann
2018-11-30 13:57 ` David Laight
2018-11-30 19:00 ` Vineet Gupta
2018-12-03 10:10 ` David Laight
2018-12-03 17:31 ` Vineet Gupta
2018-11-29 21:16 ` 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=ff1e11923e92405d883474d715008c0a@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=alexey.brodkin@synopsys.com \
--cc=joao.pinto@synopsys.com \
--cc=jose.abreu@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=vineet.gupta1@synopsys.com \
--cc=vitor.soares@synopsys.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
all inboxes | Powered by JetHome®