All of lore.kernel.org
 help / color / mirror / Atom feed
From: wangweidong1@huawei.com (Wang Weidong)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Thumb-2: Fix out-of-range offset for Thumb-2 in, proc-macros.S
Date: Tue, 17 Jun 2014 09:23:56 +0800	[thread overview]
Message-ID: <539F98AC.9050105@huawei.com> (raw)
In-Reply-To: <20140616134908.GI16758@arm.com>

On 2014/6/16 21:49, Will Deacon wrote:
> On Tue, Jun 10, 2014 at 08:00:01AM +0100, Wang Weidong wrote:
>> The STR Instruction Encoding T4 points that the <imm> is in the
>> range 0-255.So split the instruction into two for Thumb-2. Just
>> like commit 874d5d3ccc("ARM: 6623/1: Thumb-2: Fix out-of-range
>> offset for Thumb-2 in proc-v7.S").
>>
>> Signed-off-by: Wang Weidong <wangweidong1@huawei.com>
>> ---
>>  arch/arm/mm/proc-macros.S | 4 +++-
>>  1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/mm/proc-macros.S b/arch/arm/mm/proc-macros.S
>> index ee1d805..63f710c 100644
>> --- a/arch/arm/mm/proc-macros.S
>> +++ b/arch/arm/mm/proc-macros.S
>> @@ -252,7 +252,9 @@
>>  	tst	r3, #L_PTE_PRESENT | L_PTE_YOUNG	@ present and young?
>>  	movne	r2, #0				@ no -> fault
>>  
>> -	str	r2, [r0, #2048]!		@ hardware version
>> + ARM(	str	r2, [r0, #2048]! 		) @ hardware version
>> + THUMB( add	r0, r0, #2048 			)
>> + THUMB( str	r2, [r0] 			)
>>  	mov	ip, #0
>>  	mcr	p15, 0, r0, c7, c10, 1		@ clean L1 D line
>>  	mcr	p15, 0, ip, c7, c10, 4		@ data write barrier
> 
> AFAICT this is in xscale_set_pte_ext_epilogue which should only be built as
> ARM. Are you seeing a real issue here?
> 
> Will
> 

Hi will,

I don't see any issue here. I just review the codes while I learn thumb-2.
It does only build as ARM, so ignore it.

Regards
Wang

> .
> 

WARNING: multiple messages have this Message-ID (diff)
From: Wang Weidong <wangweidong1@huawei.com>
To: Will Deacon <will.deacon@arm.com>
Cc: "linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	"gregory.clement@free-electrons.com" 
	<gregory.clement@free-electrons.com>,
	"nico@linaro.org" <nico@linaro.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: Thumb-2: Fix out-of-range offset for Thumb-2 in, proc-macros.S
Date: Tue, 17 Jun 2014 09:23:56 +0800	[thread overview]
Message-ID: <539F98AC.9050105@huawei.com> (raw)
In-Reply-To: <20140616134908.GI16758@arm.com>

On 2014/6/16 21:49, Will Deacon wrote:
> On Tue, Jun 10, 2014 at 08:00:01AM +0100, Wang Weidong wrote:
>> The STR Instruction Encoding T4 points that the <imm> is in the
>> range 0-255.So split the instruction into two for Thumb-2. Just
>> like commit 874d5d3ccc("ARM: 6623/1: Thumb-2: Fix out-of-range
>> offset for Thumb-2 in proc-v7.S").
>>
>> Signed-off-by: Wang Weidong <wangweidong1@huawei.com>
>> ---
>>  arch/arm/mm/proc-macros.S | 4 +++-
>>  1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/mm/proc-macros.S b/arch/arm/mm/proc-macros.S
>> index ee1d805..63f710c 100644
>> --- a/arch/arm/mm/proc-macros.S
>> +++ b/arch/arm/mm/proc-macros.S
>> @@ -252,7 +252,9 @@
>>  	tst	r3, #L_PTE_PRESENT | L_PTE_YOUNG	@ present and young?
>>  	movne	r2, #0				@ no -> fault
>>  
>> -	str	r2, [r0, #2048]!		@ hardware version
>> + ARM(	str	r2, [r0, #2048]! 		) @ hardware version
>> + THUMB( add	r0, r0, #2048 			)
>> + THUMB( str	r2, [r0] 			)
>>  	mov	ip, #0
>>  	mcr	p15, 0, r0, c7, c10, 1		@ clean L1 D line
>>  	mcr	p15, 0, ip, c7, c10, 4		@ data write barrier
> 
> AFAICT this is in xscale_set_pte_ext_epilogue which should only be built as
> ARM. Are you seeing a real issue here?
> 
> Will
> 

Hi will,

I don't see any issue here. I just review the codes while I learn thumb-2.
It does only build as ARM, so ignore it.

Regards
Wang

> .
> 



  reply	other threads:[~2014-06-17  1:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10  7:00 [PATCH] ARM: Thumb-2: Fix out-of-range offset for Thumb-2 in, proc-macros.S Wang Weidong
2014-06-10  7:00 ` Wang Weidong
2014-06-16 13:49 ` Will Deacon
2014-06-16 13:49   ` Will Deacon
2014-06-17  1:23   ` Wang Weidong [this message]
2014-06-17  1:23     ` Wang Weidong

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=539F98AC.9050105@huawei.com \
    --to=wangweidong1@huawei.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.