From: Thomas Gleixner <tglx@linutronix.de>
To: Rahul Tanwar <rahul.tanwar@linux.intel.com>
Cc: mingo@redhat.com, bp@alien8.de, hpa@zytor.com,
tony.luck@intel.com, x86@kernel.org, andriy.shevchenko@intel.com,
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 10:34:55 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908211028030.2223@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190821081330.1187-1-rahul.tanwar@linux.intel.com>
On Wed, 21 Aug 2019, Rahul Tanwar wrote:
> 'ioapic_dynirq_base' contains the virtual IRQ base number. Presently, it is
> updated to the end of hardware IRQ numbers but this is done only when IOAPIC
> configuration type is IOAPIC_DOMAIN_LEGACY or IOAPIC_DOMAIN_STRICT. There is
> a third type IOAPIC_DOMAIN_DYNAMIC which applies when IOAPIC configuration
> comes from devicetree.
> Please see dtb_add_ioapic() in arch/x86/kernel/devicetree.c
We know how DT based ioapics are added. No need to point to it.
> In case of IOAPIC_DOMAIN_DYNAMIC (DT/OF based system), 'ioapic_dynirq_base'
> remains to zero initialized value. This means that for OF based systems,
> virtual IRQ base will get set to zero. Zero value for a virtual IRQ is a
> invalid value.
> Please see https://yarchive.net/comp/linux/zero.html for more details.
First of all, please do not use random archive links. See
Documentation/process/ how links to LKML archives should look like
Secondly, this link is irrelevant. ioapic_dynirq_base has nothing to do
with virtual IRQ number 0. It's a boundary for the dynamic allocation of
virtual interrupt numbers so that the core allocator does not pick
interrupts out of the IOAPIC's fixed interrupt number space.
This can be legitimately 0 when IOAPIC is not enabled at all.
Can you please explain what kind of problem you were seing and what this
really fixes?
Thanks,
tglx
next prev parent reply other threads:[~2019-08-21 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 8:13 Rahul Tanwar
2019-08-21 8:34 ` Thomas Gleixner [this message]
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
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=alpine.DEB.2.21.1908211028030.2223@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=alan@linux.intel.com \
--cc=andriy.shevchenko@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=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
all inboxes | Powered by JetHome®