Re: [v4, 2/3] ppc64/book3s: make some room for common interrupt vector code

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 (FWNM

Re: [v4, 2/3] ppc64/book3s: make some room for common interrupt vector code

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 o

Re: [v4, 2/3] ppc64/book3s: make some room for common interrupt vector code

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 dis

[PATCH v4 2/3] ppc64/book3s: make some room for common interrupt vector code

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 e