linux-kernel - Re: [PATCH] PowerPC: kernel: compiling issue, make additional room in exception vector area

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5178F7C3.6070700@asianux.com>
Date:	Thu, 25 Apr 2013 17:30:43 +0800
From:	Chen Gang <gang.chen@...anux.com>
To:	Michael Neuling <mikey@...ling.org>
CC:	Mike Qiu <qiudayu@...ux.vnet.ibm.com>,
	Michael Ellerman <michael@...erman.id.au>,
	linuxppc-dev@...ts.ozlabs.org, sfr@...b.auug.org.au,
	matt@...abs.org, linux-kernel@...r.kernel.org, paulus@...ba.org,
	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Subject: Re: [PATCH] PowerPC: kernel: compiling issue, make additional room
 in exception vector area

On 2013年04月25日 17:05, Chen Gang wrote:
> On 2013年04月25日 17:00, Michael Neuling wrote:
>>>>
>>>> Signed-off-by: Chen Gang <gang.chen@...anux.com>
>>>> ---
>>>>  arch/powerpc/include/asm/kvm_asm.h   |    2 +-
>>>>  arch/powerpc/kernel/exceptions-64s.S |    6 +++---
>>>>  2 files changed, 4 insertions(+), 4 deletions(-)
>>>>
>>>> diff --git a/arch/powerpc/include/asm/kvm_asm.h b/arch/powerpc/include/asm/kvm_asm.h
>>>> index b9dd382..2c65bae 100644
>>>> --- a/arch/powerpc/include/asm/kvm_asm.h
>>>> +++ b/arch/powerpc/include/asm/kvm_asm.h
>>>> @@ -86,7 +86,7 @@
>>>>  #define BOOK3S_INTERRUPT_PROGRAM	0x700
>>>>  #define BOOK3S_INTERRUPT_FP_UNAVAIL	0x800
>>>>  #define BOOK3S_INTERRUPT_DECREMENTER	0x900
>>>> -#define BOOK3S_INTERRUPT_HV_DECREMENTER	0x980
>>>> +#define BOOK3S_INTERRUPT_HV_DECREMENTER	0x988
>> This is hardwird in the architecture.. you can't just move it
>>
> 

I think of a way to solve it: we just move the related code to another
area, after enter the original entry (e.g. 0x900), we let it jump to
that area to excuse the related code.

:-)

> OK, thank you, I need continue to fix it. It seems we have to read the
> details to shrink one instruction (4 bytes), at least.
> 
> Welcome additional suggestions or completions.
> 
> Thanks.
> 


-- 
Chen Gang

Asianux Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/