From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Harman Kalra <hkalra@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Vamsi Krishna Attunuru <vattunuru@marvell.com>,
Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] drivers/octeontx2: fix recursive qint interrupts
Date: Sat, 27 Jul 2019 11:56:55 +0000 [thread overview]
Message-ID: <BYAPR18MB2424BF1FED0B24A6702B1966C8C30@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1564050397-12361-1-git-send-email-hkalra@marvell.com>
> -----Original Message-----
> From: Harman Kalra <hkalra@marvell.com>
> Sent: Thursday, July 25, 2019 3:57 PM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Nithin Kumar
> Dabilpuram <ndabilpuram@marvell.com>; Vamsi Krishna Attunuru
> <vattunuru@marvell.com>; Kiran Kumar Kokkilagadda
> <kirankumark@marvell.com>
> Cc: dev@dpdk.org; Harman Kalra <hkalra@marvell.com>
> Subject: [PATCH v2] drivers/octeontx2: fix recursive qint interrupts
>
> In case of QINT interrupt occurrence, SW fails to clear the QINT line resulting
> in recursive interrupts because currently interrupt handler gets the cause of
> the interrupt by reading NIX_LF_RQ[SQ/CQ/AURA/POOL]_OP_INT but does
> not write 1 to clear RQ[SQ/CQ/ERR]_INT field in respective
> NIX_LF_RQ[SQ/CQ/AURA/POOL]_OP_INT registers.
>
> Fixes: dc47ba15f645 ("net/octeontx2: handle queue specific error
> interrupts")
> Fixes: 50b95c3ea7af ("mempool/octeontx2: add NPA IRQ handler")
>
> Signed-off-by: Harman Kalra <hkalra@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
next prev parent reply other threads:[~2019-07-27 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 10:26 Harman Kalra
2019-07-27 11:56 ` Jerin Jacob Kollanukkaran [this message]
2019-07-29 19:51 ` Thomas Monjalon
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=BYAPR18MB2424BF1FED0B24A6702B1966C8C30@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=vattunuru@marvell.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).