From: Bjorn Helgaas <bhelgaas@google.com>
To: "Bjørn Erik Nilsen" <ben@datarespons.no>
Cc: "jg1.han@samsung.com" <jg1.han@samsung.com>,
"marex@denx.de" <marex@denx.de>,
"pratyush.anand@gmail.com" <pratyush.anand@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"kishon@ti.com" <kishon@ti.com>,
"Mohit.KUMAR@st.com" <Mohit.KUMAR@st.com>,
"ajay.khandelwal@st.com" <ajay.khandelwal@st.com>,
"tharvey@gateworks.com" <tharvey@gateworks.com>,
"Eric.Nelson@boundarydevices.com"
<Eric.Nelson@boundarydevices.com>,
"troy.kisky@boundarydevices.com" <troy.kisky@boundarydevices.com>
Subject: Re: [PATCH v5 0/2] Kernel oops from pci_disable_msi
Date: Mon, 9 Dec 2013 15:27:54 -0700 [thread overview]
Message-ID: <20131209222754.GC2135@google.com> (raw)
In-Reply-To: <52a63678.4902980a.6fd7.ffffa2b9SMTPIN_ADDED_MISSING@mx.google.com>
On Mon, Dec 09, 2013 at 10:30:17PM +0100, Bjørn Erik Nilsen wrote:
>
> 9. des. 2013 kl. 22:21 skrev Bjorn Helgaas <bhelgaas@google.com>:
>
> > On Mon, Dec 9, 2013 at 2:15 PM, Bjørn Erik Nilsen <ben@datarespons.no> wrote:
> >> Hi Bjorn,
> >>
> >> 9. des. 2013 kl. 21:43 skrev Bjorn Helgaas <bhelgaas@google.com>:
> >>
> >>> On Fri, Nov 29, 2013 at 02:35:23PM +0100, Bjørn Erik Nilsen wrote:
> >>>> This patchset address Marek Vasut's comments on the previous
> >>>> patches. I decided to split into two separate commits as they are
> >>>> unrelated.
> >>>>
> >>>> Bjørn Erik Nilsen (2):
> >>>> PCI: designware: Fix crash in dw_msi_teardown_irq
> >>>> PCI: designware: Remove redundant call to pci_write_config
> >>>
> >>> Hi Bjørn,
> >>>
> >>> There's been a fair amount of discussion about the first patch, so I'm
> >>> ignoring these for now. Please repost these (again) when that all settles
> >>> down.
> >>
> >> I'm under the impression that all concerns have been addressed and that the discussion has settled down.
> >>
> >> What are the outstanding issues to be solved regarding these patches?
> >>
> >> I'm asking because these patches are acked-by Marek Vasut and Jingoo Han as well as tested-by Mohit Kumar (and obviously myself).
> >>
> >> Jingoo Han confirms he can reproduce the crash on Exynos and that the first patch fixes the problem.
> >
> > I didn't trace through the discussion closely enough to follow
> > complaints and their resolution or retraction. Can you post the
> > current version including the acks, just so I make sure I get the
> > latest stuff?
>
> I'm not able to repost right now, but I can do it tomorrow morning if needed.
>
> v5 (as posted) is the latest however, and the amendment is:
>
> Acked-by: Marek Vasut <marex@denx.de>
> Acked-by: Jingoo Han <jg1.han@samsung.com>
> Tested-by: Mohit Kumar <mohit.kumar@st.com>
OK, I added these and applied to a pci/host-designware branch for v3.14. I
also added the following cleanup patch as suggested by Marek:
commit 0b8cfb6aa3aabc96177b1e68ef13d2eb5c686606
Author: Bjorn Helgaas <bhelgaas@google.com>
Date: Mon Dec 9 15:11:25 2013 -0700
PCI: designware: Use typical "for" loop idiom
It's conventional to use "for" rather than "while" for simple iteration.
No functional change.
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
diff --git a/drivers/pci/host/pcie-designware.c b/drivers/pci/host/pcie-designware.c
index 5274085ecd4b..1c92833a4ed3 100644
--- a/drivers/pci/host/pcie-designware.c
+++ b/drivers/pci/host/pcie-designware.c
@@ -214,8 +214,7 @@ static void clear_irq_range(struct pcie_port *pp, unsigned int irq_base,
{
unsigned int i, res, bit, val;
- i = 0;
- while (i < nvec) {
+ for (i = 0; i < nvec; i++) {
irq_set_msi_desc_off(irq_base, i, NULL);
clear_bit(pos + i, pp->msi_irq_in_use);
/* Disable corresponding interrupt on MSI interrupt controller */
@@ -224,7 +223,6 @@ static void clear_irq_range(struct pcie_port *pp, unsigned int irq_base,
dw_pcie_rd_own_conf(pp, PCIE_MSI_INTR0_ENABLE + res, 4, &val);
val &= ~(1 << bit);
dw_pcie_wr_own_conf(pp, PCIE_MSI_INTR0_ENABLE + res, 4, val);
- ++i;
}
}
@@ -268,8 +266,7 @@ static int assign_irq(int no_irqs, struct msi_desc *desc, int *pos)
* descs are also successfully allocated.
*/
- i = 0;
- while (i < no_irqs) {
+ for (i = 0; i < no_irqs; i++) {
if (irq_set_msi_desc_off(irq, i, desc) != 0) {
clear_irq_range(pp, irq, i, pos0);
goto no_valid_irq;
@@ -281,7 +278,6 @@ static int assign_irq(int no_irqs, struct msi_desc *desc, int *pos)
dw_pcie_rd_own_conf(pp, PCIE_MSI_INTR0_ENABLE + res, 4, &val);
val |= 1 << bit;
dw_pcie_wr_own_conf(pp, PCIE_MSI_INTR0_ENABLE + res, 4, val);
- i++;
}
*pos = pos0;
prev parent reply other threads:[~2013-12-09 22:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <528a1bb6.6a88700a.28c9.ffff824aSMTPIN_ADDED_MISSING@mx.google.com>
[not found] ` <CAErSpo4TbUuq0wb06JV9Xchmcjsk9q3cm7+XO-dOSiJAAhXPMA@mail.gmail.com>
2013-11-18 21:02 ` Kernel oops from pci_disable_msi Bjorn Helgaas
2013-11-18 23:11 ` Jingoo Han
2013-11-19 11:24 ` Marek Vasut
[not found] ` <1384861142.3682.1.camel@bnilsen-HP-EliteBook-8760w>
[not found] ` <cmu-lmtpd-19155-1384861370-13@frontend1.mail.m-online.net>
2013-11-19 22:01 ` Marek Vasut
[not found] ` <cmu-lmtpd-1612-1384936883-21@frontend1.mail.m-online.net>
2013-11-20 10:30 ` Marek Vasut
[not found] ` <cmu-lmtpd-21237-1384948548-21@frontend1.mail.m-online.net>
2013-11-20 12:02 ` Marek Vasut
[not found] ` <cmu-lmtpd-23243-1384949805-3@frontend1.mail.m-online.net>
2013-11-20 13:57 ` Marek Vasut
[not found] ` <1385036087.3945.28.camel@bnilsen-HP>
[not found] ` <1385039987.6020.5.camel@bnilsen-HP>
[not found] ` <16.79.22145.6305E825@epmailin9.samsung.com>
2013-11-22 8:48 ` Jingoo Han
[not found] ` <1385118399.3944.32.camel@bnilsen-HP>
[not found] ` <7D.78.31634.B838F825@epmailin2.samsung.com>
2013-11-26 11:21 ` [PATCH] " Jingoo Han
[not found] ` <cmu-lmtpd-32538-1385137032-0@frontend1.mail.m-online.net>
2013-11-26 21:19 ` Marek Vasut
[not found] ` <cmu-lmtpd-17794-1385506605-2@frontend1.mail.m-online.net>
2013-11-26 23:05 ` Marek Vasut
2013-11-27 9:46 ` Marek Vasut
[not found] ` <cmu-lmtpd-20073-1385566822-1@frontend1.mail.m-online.net>
2013-11-27 19:05 ` [PATCH v4] " Marek Vasut
[not found] ` <C7.DF.00504.D1216925@epmailin4.samsung.com>
2013-11-29 7:37 ` Jingoo Han
2013-11-29 13:35 ` [PATCH v5 0/2] " Bjørn Erik Nilsen
2013-11-29 13:35 ` [PATCH v5 1/2] PCI: designware: Fix crash in dw_msi_teardown_irq Bjørn Erik Nilsen
2013-11-29 14:32 ` Marek Vasut
[not found] ` <cmu-lmtpd-25244-1385737839-23@frontend1.mail.m-online.net>
2013-11-29 15:36 ` Marek Vasut
[not found] ` <cmu-lmtpd-32360-1385742114-0@frontend1.mail.m-online.net>
2013-11-29 17:02 ` Marek Vasut
[not found] ` <cmu-lmtpd-8418-1385750273-5@frontend1.mail.m-online.net>
2013-12-02 8:10 ` Marek Vasut
2013-11-29 13:35 ` [PATCH v5 2/2] PCI: designware: Remove redundant call to pci_write_config Bjørn Erik Nilsen
2013-12-05 1:52 ` [PATCH v5 0/2] Kernel oops from pci_disable_msi Jingoo Han
2013-12-05 2:18 ` Marek Vasut
2013-12-05 2:24 ` Jingoo Han
2013-12-05 4:07 ` Mohit KUMAR DCG
2013-12-09 20:43 ` Bjorn Helgaas
[not found] ` <52a632f0.e42c980a.3d86.ffff8faeSMTPIN_ADDED_MISSING@mx.google.com>
2013-12-09 21:21 ` Bjorn Helgaas
[not found] ` <52a63678.4902980a.6fd7.ffffa2b9SMTPIN_ADDED_MISSING@mx.google.com>
2013-12-09 22:27 ` Bjorn Helgaas [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=20131209222754.GC2135@google.com \
--to=bhelgaas@google.com \
--cc=Eric.Nelson@boundarydevices.com \
--cc=Mohit.KUMAR@st.com \
--cc=ajay.khandelwal@st.com \
--cc=ben@datarespons.no \
--cc=jg1.han@samsung.com \
--cc=kishon@ti.com \
--cc=linux-pci@vger.kernel.org \
--cc=marex@denx.de \
--cc=pratyush.anand@gmail.com \
--cc=tharvey@gateworks.com \
--cc=troy.kisky@boundarydevices.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).