From: qizhong.cheng <qizhong.cheng@mediatek.com> To: Chen-Yu Tsai <wenst@chromium.org> Cc: "Ryder Lee" <ryder.lee@mediatek.com>, "Jianjun Wang" <jianjun.wang@mediatek.com>, "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>, "Krzysztof Wilczyński" <kw@linux.com>, "Bjorn Helgaas" <bhelgaas@google.com>, linux-pci@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, chuanjia.liu@mediatek.com, qizhong.cheng@mediatek.com Subject: Re: [PATCH] PCI: mediatek: Change MSI interrupt processing sequence Date: Mon, 24 Jan 2022 16:34:43 +0800 [thread overview] Message-ID: <a43c470c41d083ad632b276ebf17795f35c98a3a.camel@mediatek.com> (raw) In-Reply-To: <CAGXv+5GUW6qcxwnfj3dsn7Lb1yY5bNv+v+PQ2VN1NX9yPmGd2A@mail.gmail.com> On Mon, 2022-01-24 at 14:55 +0800, Chen-Yu Tsai wrote: > On Mon, Jan 24, 2022 at 2:27 PM qizhong.cheng > <qizhong.cheng@mediatek.com> wrote: > > > > Hi chenYu, > > > > On Mon, 2022-01-24 at 11:12 +0800, Chen-Yu Tsai wrote: > > > Hi, > > > > > > On Sun, Jan 23, 2022 at 11:34 AM qizhong cheng > > > <qizhong.cheng@mediatek.com> wrote: > > > > > > > > As an edge-triggered interrupts, its interrupt status should be > > > > cleared > > > > before dispatch to the handler of device. > > > > > > I'm curious, is this just a code correction or are there real > > > world > > > cases where something fails? > > > > Yes, we found a failure when used iperf tool for wifi and network > > cards > > performance testing. The function of "while" has just been > > executed, > > and the EP sent an MSI before executing "Clear MSI interrupt > > status". > > After executing "Clear MSI interrupt status", this edge-triggered > > interrupt status is cleared, but EP is still waiting for interrupt > > handler. > > Can you also include this in the commit log? It would be nice to > record > the exact scenario that this fix targets. Thanks for your suggestion. I will add commit log in the next version for others review. > > ChenYu > > > > > > > Also, please add a Fixes tag and maybe Cc stable so this gets > > > backported > > > automatically. > > > > Thanks for your review, I will fix it in the next version. > > > > > > > > ChenYu > > > > > > > Signed-off-by: qizhong cheng <qizhong.cheng@mediatek.com> > > > > --- > > > > drivers/pci/controller/pcie-mediatek.c | 4 ++-- > > > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > > > > > diff --git a/drivers/pci/controller/pcie-mediatek.c > > > > b/drivers/pci/controller/pcie-mediatek.c > > > > index 2f3f974977a3..705ea33758b1 100644 > > > > --- a/drivers/pci/controller/pcie-mediatek.c > > > > +++ b/drivers/pci/controller/pcie-mediatek.c > > > > @@ -624,12 +624,12 @@ static void mtk_pcie_intr_handler(struct > > > > irq_desc *desc) > > > > if (status & MSI_STATUS){ > > > > unsigned long imsi_status; > > > > > > > > + /* Clear MSI interrupt status */ > > > > + writel(MSI_STATUS, port->base + > > > > PCIE_INT_STATUS); > > > > while ((imsi_status = readl(port->base > > > > + > > > > PCIE_IMSI_STATUS))) { > > > > for_each_set_bit(bit, > > > > &imsi_status, > > > > MTK_MSI_IRQS_NUM) > > > > generic_handle_domain_i > > > > rq(p > > > > ort->inner_domain, bit); > > > > } > > > > - /* Clear MSI interrupt status */ > > > > - writel(MSI_STATUS, port->base + > > > > PCIE_INT_STATUS); > > > > } > > > > } > > > > > > > > -- > > > > 2.25.1 > > > > > > > > > > > > _______________________________________________ > > > > Linux-mediatek mailing list > > > > Linux-mediatek@lists.infradead.org > > > > http://lists.infradead.org/mailman/listinfo/linux-mediatek _______________________________________________ Linux-mediatek mailing list Linux-mediatek@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: qizhong.cheng <qizhong.cheng@mediatek.com> To: Chen-Yu Tsai <wenst@chromium.org> Cc: "Ryder Lee" <ryder.lee@mediatek.com>, "Jianjun Wang" <jianjun.wang@mediatek.com>, "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>, "Krzysztof Wilczyński" <kw@linux.com>, "Bjorn Helgaas" <bhelgaas@google.com>, linux-pci@vger.kernel.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, chuanjia.liu@mediatek.com, qizhong.cheng@mediatek.com Subject: Re: [PATCH] PCI: mediatek: Change MSI interrupt processing sequence Date: Mon, 24 Jan 2022 16:34:43 +0800 [thread overview] Message-ID: <a43c470c41d083ad632b276ebf17795f35c98a3a.camel@mediatek.com> (raw) In-Reply-To: <CAGXv+5GUW6qcxwnfj3dsn7Lb1yY5bNv+v+PQ2VN1NX9yPmGd2A@mail.gmail.com> On Mon, 2022-01-24 at 14:55 +0800, Chen-Yu Tsai wrote: > On Mon, Jan 24, 2022 at 2:27 PM qizhong.cheng > <qizhong.cheng@mediatek.com> wrote: > > > > Hi chenYu, > > > > On Mon, 2022-01-24 at 11:12 +0800, Chen-Yu Tsai wrote: > > > Hi, > > > > > > On Sun, Jan 23, 2022 at 11:34 AM qizhong cheng > > > <qizhong.cheng@mediatek.com> wrote: > > > > > > > > As an edge-triggered interrupts, its interrupt status should be > > > > cleared > > > > before dispatch to the handler of device. > > > > > > I'm curious, is this just a code correction or are there real > > > world > > > cases where something fails? > > > > Yes, we found a failure when used iperf tool for wifi and network > > cards > > performance testing. The function of "while" has just been > > executed, > > and the EP sent an MSI before executing "Clear MSI interrupt > > status". > > After executing "Clear MSI interrupt status", this edge-triggered > > interrupt status is cleared, but EP is still waiting for interrupt > > handler. > > Can you also include this in the commit log? It would be nice to > record > the exact scenario that this fix targets. Thanks for your suggestion. I will add commit log in the next version for others review. > > ChenYu > > > > > > > Also, please add a Fixes tag and maybe Cc stable so this gets > > > backported > > > automatically. > > > > Thanks for your review, I will fix it in the next version. > > > > > > > > ChenYu > > > > > > > Signed-off-by: qizhong cheng <qizhong.cheng@mediatek.com> > > > > --- > > > > drivers/pci/controller/pcie-mediatek.c | 4 ++-- > > > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > > > > > diff --git a/drivers/pci/controller/pcie-mediatek.c > > > > b/drivers/pci/controller/pcie-mediatek.c > > > > index 2f3f974977a3..705ea33758b1 100644 > > > > --- a/drivers/pci/controller/pcie-mediatek.c > > > > +++ b/drivers/pci/controller/pcie-mediatek.c > > > > @@ -624,12 +624,12 @@ static void mtk_pcie_intr_handler(struct > > > > irq_desc *desc) > > > > if (status & MSI_STATUS){ > > > > unsigned long imsi_status; > > > > > > > > + /* Clear MSI interrupt status */ > > > > + writel(MSI_STATUS, port->base + > > > > PCIE_INT_STATUS); > > > > while ((imsi_status = readl(port->base > > > > + > > > > PCIE_IMSI_STATUS))) { > > > > for_each_set_bit(bit, > > > > &imsi_status, > > > > MTK_MSI_IRQS_NUM) > > > > generic_handle_domain_i > > > > rq(p > > > > ort->inner_domain, bit); > > > > } > > > > - /* Clear MSI interrupt status */ > > > > - writel(MSI_STATUS, port->base + > > > > PCIE_INT_STATUS); > > > > } > > > > } > > > > > > > > -- > > > > 2.25.1 > > > > > > > > > > > > _______________________________________________ > > > > Linux-mediatek mailing list > > > > Linux-mediatek@lists.infradead.org > > > > http://lists.infradead.org/mailman/listinfo/linux-mediatek _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-01-24 8:35 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-23 3:33 [PATCH] PCI: mediatek: Change MSI interrupt processing sequence qizhong cheng 2022-01-23 3:33 ` qizhong cheng 2022-01-23 3:33 ` qizhong cheng 2022-01-24 3:12 ` Chen-Yu Tsai 2022-01-24 3:12 ` Chen-Yu Tsai 2022-01-24 3:12 ` Chen-Yu Tsai 2022-01-24 6:27 ` qizhong.cheng 2022-01-24 6:27 ` qizhong.cheng 2022-01-24 6:55 ` Chen-Yu Tsai 2022-01-24 6:55 ` Chen-Yu Tsai 2022-01-24 6:55 ` Chen-Yu Tsai 2022-01-24 8:34 ` qizhong.cheng [this message] 2022-01-24 8:34 ` qizhong.cheng 2022-01-25 16:57 ` Bjorn Helgaas 2022-01-25 16:57 ` Bjorn Helgaas 2022-01-25 16:57 ` Bjorn Helgaas 2022-01-25 17:21 ` Marc Zyngier 2022-01-25 17:21 ` Marc Zyngier 2022-01-25 17:21 ` Marc Zyngier 2022-01-26 3:37 ` qizhong.cheng 2022-01-26 3:37 ` qizhong.cheng 2022-01-27 21:21 ` Bjorn Helgaas 2022-01-27 21:21 ` Bjorn Helgaas 2022-01-27 21:21 ` Bjorn Helgaas 2022-01-28 7:58 ` Jianjun Wang 2022-01-28 7:58 ` Jianjun Wang 2022-02-08 7:08 ` qizhong.cheng 2022-02-08 7:08 ` qizhong.cheng 2022-01-28 8:57 ` Marc Zyngier 2022-01-28 8:57 ` Marc Zyngier 2022-01-28 8:57 ` Marc Zyngier 2022-01-28 13:12 ` Bjorn Helgaas 2022-01-28 13:12 ` Bjorn Helgaas 2022-01-28 13:12 ` Bjorn Helgaas 2022-01-28 15:09 ` Marc Zyngier 2022-01-28 15:09 ` Marc Zyngier 2022-01-28 15:09 ` Marc Zyngier
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=a43c470c41d083ad632b276ebf17795f35c98a3a.camel@mediatek.com \ --to=qizhong.cheng@mediatek.com \ --cc=bhelgaas@google.com \ --cc=chuanjia.liu@mediatek.com \ --cc=jianjun.wang@mediatek.com \ --cc=kw@linux.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=linux-pci@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=ryder.lee@mediatek.com \ --cc=wenst@chromium.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.