From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xen-devel <xen-devel@lists.xen.org>,
Feng Jin <joe.jin@oracle.com>,
Sucheta Chakraborty <sucheta.chakraborty@qlogic.com>
Subject: Re: [PATCH 2/3] Refactor msi/msix restore code Part2
Date: Fri, 02 Aug 2013 17:16:01 +0800 [thread overview]
Message-ID: <51FB78D1.6060802@oracle.com> (raw)
In-Reply-To: <20130801151616.GE21528@konrad-lan.dumpdata.com>
On 2013-08-01 23:16, Konrad Rzeszutek Wilk wrote:
> On Wed, Jul 31, 2013 at 04:41:32PM -0600, Bjorn Helgaas wrote:
>> On Tue, Jul 23, 2013 at 9:08 PM, Zhenzhong Duan
>> <zhenzhong.duan@oracle.com> wrote:
>>> xen_initdom_restore_msi_irqs trigger a hypercall to restore addr/data/mask
>>> in dom0. It's better to do the same for default_restore_msi_irqs in baremetal.
>>>
>>> Move restore of mask in default_restore_msi_irqs, this could avoid mask
>>> restored twice in dom0, once in hypercall, the other in kernel.
>>>
>>> Without that, qlcnic driver calling pci_reset_function will lost interrupt
>>> in dom0.
>>>
>>> Tested-by: Sucheta Chakraborty <sucheta.chakraborty@qlogic.com>
>>> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@oracle.com>
>>> ---
>>> drivers/pci/msi.c | 17 ++++++++++++++---
>>> 1 files changed, 14 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
>>> index 87223ae..922fb49 100644
>>> --- a/drivers/pci/msi.c
>>> +++ b/drivers/pci/msi.c
>>> @@ -216,6 +216,8 @@ void unmask_msi_irq(struct irq_data *data)
>>> #ifdef HAVE_DEFAULT_MSI_RESTORE_IRQS
>>> void default_restore_msi_irqs(struct pci_dev *dev, int irq)
>>> {
>>> + int pos;
>>> + u16 control;
>>> struct msi_desc *entry;
>>>
>>> entry = NULL;
>>> @@ -228,8 +230,19 @@ void default_restore_msi_irqs(struct pci_dev *dev, int irq)
>>> entry = irq_get_msi_desc(irq);
>>> }
>>>
>>> - if (entry)
>>> + if (entry) {
>>> write_msi_msg(irq, &entry->msg);
>>> + if (dev->msix_enabled) {
>>> + msix_mask_irq(entry, entry->masked);
>>> + readl(entry->mask_base);
>>> + } else {
>>> + pos = entry->msi_attrib.pos;
>>> + pci_read_config_word(dev, pos + PCI_MSI_FLAGS,
>>> + &control);
>>> + msi_mask_irq(entry, msi_capable_mask(control),
>>> + entry->masked);
>>> + }
>>> + }
>>> }
>>> #endif
>>>
>>> @@ -406,7 +419,6 @@ static void __pci_restore_msi_state(struct pci_dev *dev)
>>> arch_restore_msi_irqs(dev, dev->irq);
>>>
>>> pci_read_config_word(dev, dev->msi_cap + PCI_MSI_FLAGS, &control);
>>> - msi_mask_irq(entry, msi_capable_mask(control), entry->masked);
>>> control &= ~PCI_MSI_FLAGS_QSIZE;
>>> control |= (entry->msi_attrib.multiple << 4) | PCI_MSI_FLAGS_ENABLE;
>>> pci_write_config_word(dev, dev->msi_cap + PCI_MSI_FLAGS, control);
>>> @@ -430,7 +442,6 @@ static void __pci_restore_msix_state(struct pci_dev *dev)
>>>
>>> list_for_each_entry(entry, &dev->msi_list, list) {
>>> arch_restore_msi_irqs(dev, entry->irq);
>>> - msix_mask_irq(entry, entry->masked);
>>> }
>>>
>>> control &= ~PCI_MSIX_FLAGS_MASKALL;
>> Konrad, are you OK with this patch now?
> Yes, I wanted to make sure that the existing behavior under baremetal
> was not altered.
>
> And Duan had confirmed it was not - thought to be on a safe side it
> would be good to confirm this via testing just in case.
I had ever let our customer test on baremetal and it passed.
zduan
WARNING: multiple messages have this Message-ID (diff)
From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Sucheta Chakraborty <sucheta.chakraborty@qlogic.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Feng Jin <joe.jin@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
xen-devel <xen-devel@lists.xen.org>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 2/3] Refactor msi/msix restore code Part2
Date: Fri, 02 Aug 2013 17:16:01 +0800 [thread overview]
Message-ID: <51FB78D1.6060802@oracle.com> (raw)
In-Reply-To: <20130801151616.GE21528@konrad-lan.dumpdata.com>
On 2013-08-01 23:16, Konrad Rzeszutek Wilk wrote:
> On Wed, Jul 31, 2013 at 04:41:32PM -0600, Bjorn Helgaas wrote:
>> On Tue, Jul 23, 2013 at 9:08 PM, Zhenzhong Duan
>> <zhenzhong.duan@oracle.com> wrote:
>>> xen_initdom_restore_msi_irqs trigger a hypercall to restore addr/data/mask
>>> in dom0. It's better to do the same for default_restore_msi_irqs in baremetal.
>>>
>>> Move restore of mask in default_restore_msi_irqs, this could avoid mask
>>> restored twice in dom0, once in hypercall, the other in kernel.
>>>
>>> Without that, qlcnic driver calling pci_reset_function will lost interrupt
>>> in dom0.
>>>
>>> Tested-by: Sucheta Chakraborty <sucheta.chakraborty@qlogic.com>
>>> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@oracle.com>
>>> ---
>>> drivers/pci/msi.c | 17 ++++++++++++++---
>>> 1 files changed, 14 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
>>> index 87223ae..922fb49 100644
>>> --- a/drivers/pci/msi.c
>>> +++ b/drivers/pci/msi.c
>>> @@ -216,6 +216,8 @@ void unmask_msi_irq(struct irq_data *data)
>>> #ifdef HAVE_DEFAULT_MSI_RESTORE_IRQS
>>> void default_restore_msi_irqs(struct pci_dev *dev, int irq)
>>> {
>>> + int pos;
>>> + u16 control;
>>> struct msi_desc *entry;
>>>
>>> entry = NULL;
>>> @@ -228,8 +230,19 @@ void default_restore_msi_irqs(struct pci_dev *dev, int irq)
>>> entry = irq_get_msi_desc(irq);
>>> }
>>>
>>> - if (entry)
>>> + if (entry) {
>>> write_msi_msg(irq, &entry->msg);
>>> + if (dev->msix_enabled) {
>>> + msix_mask_irq(entry, entry->masked);
>>> + readl(entry->mask_base);
>>> + } else {
>>> + pos = entry->msi_attrib.pos;
>>> + pci_read_config_word(dev, pos + PCI_MSI_FLAGS,
>>> + &control);
>>> + msi_mask_irq(entry, msi_capable_mask(control),
>>> + entry->masked);
>>> + }
>>> + }
>>> }
>>> #endif
>>>
>>> @@ -406,7 +419,6 @@ static void __pci_restore_msi_state(struct pci_dev *dev)
>>> arch_restore_msi_irqs(dev, dev->irq);
>>>
>>> pci_read_config_word(dev, dev->msi_cap + PCI_MSI_FLAGS, &control);
>>> - msi_mask_irq(entry, msi_capable_mask(control), entry->masked);
>>> control &= ~PCI_MSI_FLAGS_QSIZE;
>>> control |= (entry->msi_attrib.multiple << 4) | PCI_MSI_FLAGS_ENABLE;
>>> pci_write_config_word(dev, dev->msi_cap + PCI_MSI_FLAGS, control);
>>> @@ -430,7 +442,6 @@ static void __pci_restore_msix_state(struct pci_dev *dev)
>>>
>>> list_for_each_entry(entry, &dev->msi_list, list) {
>>> arch_restore_msi_irqs(dev, entry->irq);
>>> - msix_mask_irq(entry, entry->masked);
>>> }
>>>
>>> control &= ~PCI_MSIX_FLAGS_MASKALL;
>> Konrad, are you OK with this patch now?
> Yes, I wanted to make sure that the existing behavior under baremetal
> was not altered.
>
> And Duan had confirmed it was not - thought to be on a safe side it
> would be good to confirm this via testing just in case.
I had ever let our customer test on baremetal and it passed.
zduan
next prev parent reply other threads:[~2013-08-02 9:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 3:08 [PATCH 2/3] Refactor msi/msix restore code Part2 Zhenzhong Duan
2013-07-24 13:46 ` Konrad Rzeszutek Wilk
2013-07-24 13:46 ` Konrad Rzeszutek Wilk
2013-07-25 6:52 ` Zhenzhong Duan
2013-07-25 12:25 ` Konrad Rzeszutek Wilk
2013-07-25 12:25 ` Konrad Rzeszutek Wilk
2013-07-26 3:01 ` Zhenzhong Duan
2013-07-26 3:01 ` Zhenzhong Duan
2013-07-25 6:52 ` Zhenzhong Duan
2013-07-31 22:41 ` Bjorn Helgaas
2013-07-31 22:41 ` Bjorn Helgaas
2013-08-01 15:16 ` Konrad Rzeszutek Wilk
2013-08-02 9:16 ` Zhenzhong Duan [this message]
2013-08-02 9:16 ` Zhenzhong Duan
2013-08-02 12:01 ` Konrad Rzeszutek Wilk
2013-08-02 12:01 ` Konrad Rzeszutek Wilk
2013-08-05 7:19 ` Zhenzhong Duan
2013-08-05 7:19 ` Zhenzhong Duan
2013-08-01 15:16 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2013-07-24 3:08 Zhenzhong Duan
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=51FB78D1.6060802@oracle.com \
--to=zhenzhong.duan@oracle.com \
--cc=bhelgaas@google.com \
--cc=joe.jin@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sucheta.chakraborty@qlogic.com \
--cc=xen-devel@lists.xen.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 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.