From: Chen Gang <gang.chen@asianux.com>
To: Michael Neuling <mikey@neuling.org>
Cc: Mike Qiu <qiudayu@linux.vnet.ibm.com>,
Michael Ellerman <michael@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, sfr@canb.auug.org.au,
matt@ozlabs.org, linux-kernel@vger.kernel.org, paulus@samba.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH] PowerPC: kernel: compiling issue, make additional room in exception vector area
Date: Thu, 25 Apr 2013 17:05:00 +0800 [thread overview]
Message-ID: <5178F1BC.6050905@asianux.com> (raw)
In-Reply-To: <1659.1366880440@ale.ozlabs.ibm.com>
On 2013年04月25日 17:00, Michael Neuling wrote:
>> >
>> > Signed-off-by: Chen Gang <gang.chen@asianux.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
>
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
next prev parent reply other threads:[~2013-04-25 9:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 8:22 "attempt to move .org backwards" still show up Mike Qiu
2013-04-24 8:31 ` Michael Ellerman
2013-04-24 8:35 ` Mike Qiu
2013-04-24 10:37 ` Michael Neuling
2013-04-24 12:47 ` Mike
2013-04-25 1:05 ` Chen Gang
2013-04-25 4:05 ` Mike Qiu
2013-04-25 5:36 ` Chen Gang
2013-04-25 7:23 ` Chen Gang
2013-04-25 6:25 ` Paul Mackerras
2013-04-25 11:16 ` Chen Gang
2013-04-26 1:58 ` Mike Qiu
2013-04-26 2:05 ` Chen Gang
2013-04-25 11:51 ` [PATCH v2] PowerPC: kernel: compiling issue, make additional room in exception vector area Chen Gang
2013-04-25 11:58 ` Chen Gang
2013-04-25 23:16 ` Michael Neuling
2013-04-26 1:06 ` Chen Gang
2013-04-26 1:18 ` Chen Gang
2013-04-26 1:36 ` Chen Gang
2013-04-26 2:03 ` Mike Qiu
2013-04-26 2:06 ` Chen Gang
2013-04-26 3:08 ` Mike Qiu
2013-04-26 3:25 ` Chen Gang
2013-04-26 3:42 ` Chen Gang
2013-04-26 3:54 ` Mike Qiu
2013-04-27 9:28 ` Chen Gang F T
2013-04-27 9:32 ` Mike Qiu
2013-04-27 9:33 ` Chen Gang
2013-04-26 3:19 ` "attempt to move .org backwards" still show up Mike Qiu
2013-04-25 8:18 ` [PATCH] PowerPC: kernel: compiling issue, make additional room in exception vector area Chen Gang
2013-04-25 8:21 ` Chen Gang
2013-04-25 8:24 ` Mike Qiu
2013-04-25 9:00 ` Michael Neuling
2013-04-25 9:05 ` Chen Gang [this message]
2013-04-25 9:30 ` Chen Gang
2013-04-24 8:36 ` "attempt to move .org backwards" still show up Mike Qiu
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=5178F1BC.6050905@asianux.com \
--to=gang.chen@asianux.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matt@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=mikey@neuling.org \
--cc=paulus@samba.org \
--cc=qiudayu@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
/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