From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Tanwar, Rahul" <rahul.tanwar@linux.intel.com>,
mingo@redhat.com, bp@alien8.de, hpa@zytor.com,
tony.luck@intel.com, x86@kernel.org, alan@linux.intel.com,
rppt@linux.ibm.com, linux-kernel@vger.kernel.org,
qi-ming.wu@intel.com, cheol.yong.kim@intel.com,
rahul.tanwar@intel.com
Subject: Re: [PATCH] x86/apic: Update virtual irq base for DT/OF based system as well
Date: Wed, 21 Aug 2019 19:47:38 +0300 [thread overview]
Message-ID: <20190821164738.GA30120@smile.fi.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1908211510390.2223@nanos.tec.linutronix.de>
On Wed, Aug 21, 2019 at 03:16:31PM +0200, Thomas Gleixner wrote:
> On Wed, 21 Aug 2019, Andy Shevchenko wrote:
> > On Wed, Aug 21, 2019 at 01:20:53PM +0200, Thomas Gleixner wrote:
> > > But x86 implements arch_dynirq_lower_bound() which overrides the core limit
> > > and because ioapic_dynirq_base is zero in the DT case it allows VIRQ 0 to
> > > be allocated which then causes of_irq*() to fail.
> > >
> > > So your change prevents that by excluding the 'GSI' range from allocation,
> > > which means that the first irq number which is handed out is 24, assumed
> > > you have one IOAPIC with 24 pins.
> >
> > I have tested this on the ACPI-based system where we have 55 lines of IOAPIC,
> > no PIC, and some GPIO lines. Overall I see that nr_irqs is 512 and shifting
> > by 55 freezes 10% of the space for nothing. Luckily we have SPARSE_IRQS
> > selected for any X86, so, it wouldn't waste memory.
> >
> > I think we may do slightly better if we just limit the change to the certain
> > cases.
>
> For DT we can actually avoid that completely. See below.
>
> For ACPI not unfortunately as the stupid GSI mapping is hard coded.
The below works better for my case, so, if you are going with that
Tested-by: Andy Shevchenko <andriy.shevchenko@intel.com>
>
> Thanks,
>
> tglx
>
> 8<-------------
> --- a/arch/x86/kernel/apic/io_apic.c
> +++ b/arch/x86/kernel/apic/io_apic.c
> @@ -2438,7 +2438,13 @@ unsigned int arch_dynirq_lower_bound(uns
> * dmar_alloc_hwirq() may be called before setup_IO_APIC(), so use
> * gsi_top if ioapic_dynirq_base hasn't been initialized yet.
> */
> - return ioapic_initialized ? ioapic_dynirq_base : gsi_top;
> + if (!ioapic_initialized)
> + return gsi_top;
> + /*
> + * For DT enabled machines ioapic_dynirq_base is irrelevant and not
> + * updated. So simply return @from if ioapic_dynirq_base == 0.
> + */
> + return ioapic_dynirq_base ? : from;
> }
>
> #ifdef CONFIG_X86_32
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-08-21 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 8:13 [PATCH] x86/apic: Update virtual irq base for DT/OF based system as well Rahul Tanwar
2019-08-21 8:34 ` Thomas Gleixner
2019-08-21 9:31 ` Tanwar, Rahul
2019-08-21 11:20 ` Thomas Gleixner
2019-08-21 12:34 ` Andy Shevchenko
2019-08-21 13:16 ` Thomas Gleixner
2019-08-21 16:47 ` Andy Shevchenko [this message]
2019-08-22 3:48 ` Tanwar, Rahul
2019-08-26 11:46 ` [tip: x86/urgent] x86/apic: Fix arch_dynirq_lower_bound() bug for DT enabled machines tip-bot2 for Thomas Gleixner
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=20190821164738.GA30120@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=alan@linux.intel.com \
--cc=bp@alien8.de \
--cc=cheol.yong.kim@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qi-ming.wu@intel.com \
--cc=rahul.tanwar@intel.com \
--cc=rahul.tanwar@linux.intel.com \
--cc=rppt@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox