From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Cc: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>,
Michael Neuling <mikey@neuling.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [v4, 2/3] ppc64/book3s: make some room for common interrupt vector code
Date: Mon, 18 Apr 2016 09:14:45 +0530 [thread overview]
Message-ID: <5714582D.7070606@linux.vnet.ibm.com> (raw)
In-Reply-To: <1460725197.22415.7.camel@ellerman.id.au>
On 04/15/2016 06:29 PM, Michael Ellerman wrote:
> On Fri, 2016-04-15 at 21:06 +1000, Michael Ellerman wrote:
>> Hi Hari,
>>
>> Thanks for persisting with this.
>>
>> On Thu, 2016-07-04 at 21:58:50 UTC, Hari Bathini wrote:
>>> With the previous patch, we choke out whatever little space is left
>>> below 0x7000 (FWNMI hard block) while there is a hole of ~1400 bytes
>>> below __end_interrupts marker when CONFIG_CBE_RAS is disabled.
>>> Considering CONFIG_CBE_RAS is not enabled by default for BOOK3S, this
>>> is not a desirable scenario especially when we have to worry about
>>> each additional instruction that goes below 0x7000.
>>>
>>> Memory region from 0x1800 to 0x4000 is dedicated for common interrupt
>>> vector code. Also, we never hit an interrupt below 0x300 when IR=DR=1
>>> implying memory region between 0x4000 to 0x4300 can also be used for
>>> common interrupt vector code. So, we can effectively use memory region
>>> between 0x1800 to 0x4300 for common interrupt vector code.
>> On Power9 the system-call-vectored instruction will use the region at 0x3000, so
>> moving code into that space is not a good long term plan.
>>
>> I'll take your v2 and put it in next next week.
> I'll add this fixes line, which I think is correct:
>
> Fixes: c1fb6816fb1b ("powerpc: Add relocation on exception vector handlers")
Yeah. Thanks!
> cheers
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2016-04-18 3:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 21:57 [PATCH v4 1/3] ppc64/book3s: fix branching to out of line handlers in relocation kernel Hari Bathini
2016-04-07 21:58 ` [PATCH v4 2/3] ppc64/book3s: make some room for common interrupt vector code Hari Bathini
2016-04-15 11:06 ` [v4, " Michael Ellerman
2016-04-15 12:59 ` Michael Ellerman
2016-04-18 3:44 ` Hari Bathini [this message]
2016-04-07 22:00 ` [PATCH v4 3/3] ppc64/book3s: remove __end_handlers marker Hari Bathini
2016-04-21 13:39 ` [v4,3/3] " Michael Ellerman
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=5714582D.7070606@linux.vnet.ibm.com \
--to=hbathini@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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.