From: Robin Murphy <robin.murphy@arm.com>
To: "kwangwoo.lee@sk.com" <kwangwoo.lee@sk.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: "hyunchul3.kim@sk.com" <hyunchul3.kim@sk.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"woosuk.chung@sk.com" <woosuk.chung@sk.com>
Subject: Re: [PATCH v2] arm64: mm: convert __dma_* routines to use start, size
Date: Mon, 1 Aug 2016 14:36:19 +0100 [thread overview]
Message-ID: <21272fb2-bffb-15ee-41a9-af0251a33fd0@arm.com> (raw)
In-Reply-To: <1c4ec01bd3594485b6a4b386994dc6ca@nmail01.hynixad.com>
On 01/08/16 00:45, kwangwoo.lee@sk.com wrote:
[...]
>>>> -----8<-----
>>>> diff --git a/arch/arm64/include/asm/assembler.h
>>>> b/arch/arm64/include/asm/assembler.h
>>>> index 10b017c4bdd8..1c005c90387e 100644
>>>> --- a/arch/arm64/include/asm/assembler.h
>>>> +++ b/arch/arm64/include/asm/assembler.h
>>>> @@ -261,7 +261,16 @@ lr .req x30 // link register
>>>> add \size, \kaddr, \size
>>>> sub \tmp2, \tmp1, #1
>>>> bic \kaddr, \kaddr, \tmp2
>>>> -9998: dc \op, \kaddr
>>>> +9998:
>>>> + .ifeqs "\op", "cvac"
>>>> +alternative_if_not ARM64_WORKAROUND_CLEAN_CACHE
>>>> + dc cvac, \kaddr
>>>> +alternative_else
>>>> + dc civac, \kaddr
>>>> +alternative_endif
>>>> + .else
>>>> + dc \op, \kaddr
>>>> + .endif
>>>> add \kaddr, \kaddr, \tmp1
>>>> cmp \kaddr, \size
>>>> b.lo 9998b
>>>
>>> I agree that it looks not viable because it makes the macro bigger and
>>> conditional specifically with CVAC op.
>>
>> Actually, having had a poke around in the resulting disassembly, it
>> looks like this does work correctly. I can't think of a viable reason
>> for the whole dcache_by_line_op to ever be wrapped in yet another
>> alternative (which almost certainly would go horribly wrong), and it
>> would mean that any other future users are automatically covered for
>> free. It's just horrible to look at at the source level.
>
> Then, Are you going to send a patch for this? Or should I include this change?
I'll do a bit more testing just to make sure, then spin a separate patch
(and try to remember to keep you on CC..)
Robin.
next prev parent reply other threads:[~2016-08-01 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 7:34 Kwangwoo Lee
2016-07-26 10:43 ` Robin Murphy
2016-07-27 1:55 ` kwangwoo.lee
2016-07-27 9:56 ` Robin Murphy
2016-07-28 0:08 ` kwangwoo.lee
2016-07-29 17:06 ` Robin Murphy
2016-07-31 23:45 ` kwangwoo.lee
2016-08-01 13:36 ` Robin Murphy [this message]
2016-08-01 13:53 ` Robin Murphy
2016-08-01 23:24 ` kwangwoo.lee
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=21272fb2-bffb-15ee-41a9-af0251a33fd0@arm.com \
--to=robin.murphy@arm.com \
--cc=catalin.marinas@arm.com \
--cc=hyunchul3.kim@sk.com \
--cc=kwangwoo.lee@sk.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=will.deacon@arm.com \
--cc=woosuk.chung@sk.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®