From: Bjorn Helgaas <helgaas@kernel.org>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: linux-pci@vger.kernel.org, linuxppc-dev@ozlabs.org,
bhelgaas@google.com, mpe@ellerman.id.au
Subject: Re: [PATCH 4/4] drivers/pci/hotplug: Support surprise hotplug
Date: Mon, 26 Sep 2016 08:11:46 -0500 [thread overview]
Message-ID: <20160926131146.GB3569@localhost> (raw)
In-Reply-To: <20160926130802.GA16718@gwshan>
On Mon, Sep 26, 2016 at 11:08:02PM +1000, Gavin Shan wrote:
> On Wed, Sep 21, 2016 at 11:57:03AM -0500, Bjorn Helgaas wrote:
> >Hi Gavin,
> >
> >You don't need my ack for any of these, and I assume you'll merge them
> >through the powerpc tree.
> >
> >Minor comments below, feel free to ignore them.
> >
> >On Wed, Sep 21, 2016 at 10:15:30PM +1000, Gavin Shan wrote:
> >> ...
> >> @@ -536,9 +565,16 @@ static struct pnv_php_slot *pnv_php_alloc_slot(struct device_node *dn)
> >> if (unlikely(!php_slot))
> >> return NULL;
> >>
> >> + php_slot->event = kzalloc(sizeof(struct pnv_php_event), GFP_KERNEL);
> >> + if (unlikely(!php_slot->event)) {
> >> + kfree(php_slot);
> >> + return NULL;
> >> + }
> >
> >Since you *always* allocate the event when allocating the php_slot,
> >making the event a member of php_slot (instead of keeping a pointer to
> >it) would simplify your memory management a bit.
> >
> >It seems to be the style in this file to use "unlikely" liberally, but
> >I really doubt there's any performance consideration in this code. To
> >me it adds more clutter than usefulness.
> >
> >> +static irqreturn_t pnv_php_interrupt(int irq, void *data)
> >> +{
> >> + struct pnv_php_slot *php_slot = data;
> >> + struct pci_dev *pchild, *pdev = php_slot->pdev;
> >> + struct eeh_dev *edev;
> >> + struct eeh_pe *pe;
> >> + struct pnv_php_event *event;
> >> + u16 sts, lsts;
> >> + u8 presence;
> >> + bool added;
> >> + unsigned long flags;
> >> + int ret;
> >> +
> >> + pcie_capability_read_word(pdev, PCI_EXP_SLTSTA, &sts);
> >> + sts &= (PCI_EXP_SLTSTA_PDC | PCI_EXP_SLTSTA_DLLSC);
> >> + pcie_capability_write_word(pdev, PCI_EXP_SLTSTA, sts);
> >
> >I didn't realize that this is some sort of hybrid of native PCIe
> >hotplug and PowerNV-specific stuff. Wonder if there's any opportunity
> >to combine with or leverage pciehp. That seems pretty blue-sky
> >though, since there's so much PowerNV special sauce here.
> >
>
> Bjorn, thanks a lot for your comments. All comments except last one
> (leverage pciehp) are covered in v2 which wasn't copied to linux-pci@
> list to avoid unnecessary traffic. Yeah, the driver is too much PowerNV
> platform specific things, which makes it hard to be built on top of
> pciehp.
Sounds good, thanks!
prev parent reply other threads:[~2016-09-26 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 12:15 [PATCH 0/4] powerpc/powernv: PCI Surprise Hotplug Support Gavin Shan
2016-09-21 12:15 ` [PATCH 1/4] powerpc/eeh: Allow to freeze PE in eeh_pe_set_option() Gavin Shan
2016-09-21 12:15 ` [PATCH 2/4] powerpc/eeh: Export eeh_pe_state_mark() Gavin Shan
2016-09-21 12:15 ` [PATCH 3/4] powerpc/powernv: Unfreeze PE on allocation Gavin Shan
2016-09-21 12:15 ` [PATCH 4/4] drivers/pci/hotplug: Support surprise hotplug Gavin Shan
2016-09-21 16:57 ` Bjorn Helgaas
2016-09-22 10:51 ` Michael Ellerman
2016-09-26 13:08 ` Gavin Shan
2016-09-26 13:11 ` 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=20160926131146.GB3569@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).