All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Keith Busch <keith.busch@intel.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
	liudongdong3@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI/DPC: Fix shared interrupt handling
Date: Thu, 14 Dec 2017 07:54:44 -0700	[thread overview]
Message-ID: <20171214075444.6bfbf01e@w520.home> (raw)
In-Reply-To: <20171214145030.GA25329@localhost.localdomain>

On Thu, 14 Dec 2017 07:50:31 -0700
Keith Busch <keith.busch@intel.com> wrote:

> On Wed, Dec 13, 2017 at 05:01:58PM -0700, Alex Williamson wrote:
> > @@ -109,6 +109,7 @@ static void interrupt_event_handler(struct work_struct *work)
> >  	struct dpc_dev *dpc = container_of(work, struct dpc_dev, work);
> >  	struct pci_dev *dev, *temp, *pdev = dpc->dev->port;
> >  	struct pci_bus *parent = pdev->subordinate;
> > +	u16 ctl;
> >  
> >  	pci_lock_rescan_remove();
> >  	list_for_each_entry_safe_reverse(dev, temp, &parent->devices,
> > @@ -135,6 +136,10 @@ static void interrupt_event_handler(struct work_struct *work)
> >  
> >  	pci_write_config_word(pdev, dpc->cap_pos + PCI_EXP_DPC_STATUS,
> >  		PCI_EXP_DPC_STATUS_TRIGGER | PCI_EXP_DPC_STATUS_INTERRUPT);
> > +
> > +	pci_read_config_word(pdev, dpc->cap_pos + PCI_EXP_DPC_CTL, &ctl);
> > +	pci_write_config_word(pdev, dpc->cap_pos + PCI_EXP_DPC_CTL,
> > +			      ctl & ~PCI_EXP_DPC_CTL_INT_EN);  
> 
> Did you mean to re-enable the interrupt here rather than mask it off?

D'oh, yes.  v2 coming.  Thanks,

Alex

      reply	other threads:[~2017-12-14 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  0:01 [PATCH] PCI/DPC: Fix shared interrupt handling Alex Williamson
2017-12-14 14:50 ` Keith Busch
2017-12-14 14:54   ` Alex Williamson [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=20171214075444.6bfbf01e@w520.home \
    --to=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=liudongdong3@huawei.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 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.