public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shanker Donthineni <shankerd@codeaurora.org>
To: Marc Zyngier <marc.zyngier@arm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Jason Cooper <jason@lakedaemon.net>,
	Vikram Sethi <vikrams@codeaurora.org>
Subject: Re: [PATCH] irqchip: gic-v3-its: Don't assume GICv3 hardware supports 16bit INTID
Date: Mon, 20 Mar 2017 04:52:29 -0500	[thread overview]
Message-ID: <e951b77e-5bc0-1895-928c-1d699091dcbd@codeaurora.org> (raw)
In-Reply-To: <a7e9f0a6-6118-a8a1-c6e9-8e6841c49f30@arm.com>

Hi Marc,


On 03/17/2017 10:49 AM, Marc Zyngier wrote:
> On 15/03/17 05:46, Shanker Donthineni wrote:
>> The current ITS driver is assuming every ITS hardware implementation
>> supports minimum of 16bit INTID. But this is not true, as per GICv3
>> specification, INTID field is IMPLEMENTATION DEFINED in the range of
>> 14-24 bits. We might see an unpredictable system behavior on systems
>> where hardware support less than 16bits and software tries to use
>> 64K LPI interrupts.
>>
>> On Qualcomm Datacenter Technologies QDF2400 platform, boot log shows
>> confusing information about number of LPI chunks as shown below. The
>> QDF2400 ITS hardware supports 24bit INTID.
>>
>> This patch allocates the memory resources for PEND/PROP tables based
>> on discoverable value which is specified in GITS_TYPER.IDbits. Also
>> taking this opportunity to increase number of LPI/MSI(x) to 128K if
>> the hardware is capable, and show log message that reflects the
>> correct number of LPI chunks.
> As much as I like the idea of fixing the obvious bug that assuming 16bit
> of ID space is, what is the rational of capping the support to another
> arbitrary value?

I believe 128K LPIs are sufficient so capped to 17 bits.

> Why can't we (just like other tables) try and allocate the full amount
> required (with a possible back-off if allocations fail)?

Qualcomm ITS hardware supports 24bit LPI, it requires lot of memory to handle  2^24  entry property and pending table.

>
> Thanks,
>
> 	M.

-- 
Shanker Donthineni
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

      reply	other threads:[~2017-03-20  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15  5:46 [PATCH] irqchip: gic-v3-its: Don't assume GICv3 hardware supports 16bit INTID Shanker Donthineni
2017-03-17 15:49 ` Marc Zyngier
2017-03-20  9:52   ` Shanker Donthineni [this message]

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=e951b77e-5bc0-1895-928c-1d699091dcbd@codeaurora.org \
    --to=shankerd@codeaurora.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=tglx@linutronix.de \
    --cc=vikrams@codeaurora.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