From: christophe lombard <clombard@linux.vnet.ibm.com>
To: benh@au1.ibm.com, linuxppc-dev@lists.ozlabs.org,
fbarrat@linux.vnet.ibm.com, vaibhav@linux.vnet.ibm.com,
andrew.donnellan@au1.ibm.com
Subject: Re: [PATCH] cxl: disable the lazy approach for irqs in POWERVM environment.
Date: Fri, 23 Mar 2018 17:17:56 +0100 [thread overview]
Message-ID: <fd18ea29-18f9-ae02-4e26-535ee189f739@linux.vnet.ibm.com> (raw)
In-Reply-To: <1521771288.16434.326.camel@au1.ibm.com>
Le 23/03/2018 à 03:14, Benjamin Herrenschmidt a écrit :
> On Thu, 2018-03-22 at 17:37 +0100, Christophe Lombard wrote:
>> The cxl driver cannot disable the interrupt at the device level and has
>> to use disable_irq[_nosync] instead.
>> To avoid the implementation of the lazy optimisation (the interrupt is
>> marked disabled, but the hardware is left unmasked), we can disable it,
>> for a particular irq line, by calling
>> 'irq_set_status_flags(irq, IRQ_DISABLE_UNLAZY)'.
>
> Why do you need that ? What's wrong with the lazy approach ? It makes
> disable_irq/enable_irq faster...
>
> You shouldn't need that unless your device is generating a *LOT* of
> irqs while disabled.
>
An issue on POWERVM (CAPI) has been introduced with the following patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bf22ff45bed664aefb5c4e43029057a199b7070c
The PSL or AFU interrupts are never received by the cxl driver because
the interrupts are never unmasked.
Without this patch (genirq: Avoid unnecessary low level irq function
calls), the callback desc->irq_data.chip->irq_unmask(&desc->irq_data);
(= ics_rtas_unmask_irq()) is called by default through irq_enable().
The cxl driver disables the interrupts before attaching the process
element and enables the interrupts after that.
In the current code, irq_enable() unmasks the irq only if the irq state
is IRQD_IRQ_MASKED but it does not.
Call irq_set_status_flags(irq, IRQ_DISABLE_UNLAZY) allows forcing
irq_disable() to update the irq state to IRQD_IRQ_MASKED and by default
irq_enable() will unmask the irq through ics_rtas_unmask_irq().
>> Signed-off-by: Christophe Lombard <clombard@linux.vnet.ibm.com>
>> ---
>> drivers/misc/cxl/guest.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/misc/cxl/guest.c b/drivers/misc/cxl/guest.c
>> index f58b4b6c..dc476e1 100644
>> --- a/drivers/misc/cxl/guest.c
>> +++ b/drivers/misc/cxl/guest.c
>> @@ -389,6 +389,7 @@ static void disable_afu_irqs(struct cxl_context *ctx)
>> hwirq = ctx->irqs.offset[r];
>> for (i = 0; i < ctx->irqs.range[r]; hwirq++, i++) {
>> virq = irq_find_mapping(NULL, hwirq);
>> + irq_set_status_flags(virq, IRQ_DISABLE_UNLAZY);
>> disable_irq(virq);
>> }
>> }
next prev parent reply other threads:[~2018-03-23 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 16:37 [PATCH] cxl: disable the lazy approach for irqs in POWERVM environment Christophe Lombard
2018-03-23 2:14 ` Benjamin Herrenschmidt
2018-03-23 16:17 ` christophe lombard [this message]
2018-03-24 8:14 ` Benjamin Herrenschmidt
2018-05-07 16:02 ` christophe lombard
2018-05-07 21:01 ` Benjamin Herrenschmidt
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=fd18ea29-18f9-ae02-4e26-535ee189f739@linux.vnet.ibm.com \
--to=clombard@linux.vnet.ibm.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=benh@au1.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=vaibhav@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).