From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] PCI: Endpoint: Miscellaneous improvements
Date: Mon, 24 Feb 2020 10:34:36 +0000 [thread overview]
Message-ID: <20200224103436.GA8764@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20200224095338.3758-1-kishon@ti.com>
On Mon, Feb 24, 2020 at 03:23:33PM +0530, Kishon Vijay Abraham I wrote:
> Changes from v2:
> *) Added "Tested-by" tag from Vidya Sagar
> *) Added stable fixes tag to "Fix for concurrent memory allocation in
> OB address region"
>
> Changes from v1:
> Rebased to Linux 5.6-rc1 and removed dependencies to my other series
> to unblock [1]
>
> [1] -> http://lore.kernel.org/r/20200103100736.27627-1-vidyas@nvidia.com
>
> v1 of this patch series can be found @
> http://lore.kernel.org/r/20191231100331.6316-1-kishon@ti.com
>
> This series adds miscellaneous improvements to PCIe endpoint core.
> 1) Protect concurrent access to memory allocation in pci-epc-mem
> 2) Replace spinlock with mutex in pci-epc-core and also use
> notification chain mechanism to notify EPC events to EPF driver.
> 3) Since endpoint function device can be created by multiple
> mechanisms (configfs, devicetree, etc..), allowing each of these
> mechanisms to assign a function number would result in mutliple
> endpoint function devices having the same function number. In order
> to avoid this, let EPC core assign a function number to the
> endpoint device.
>
> Kishon Vijay Abraham I (5):
> PCI: endpoint: Use notification chain mechanism to notify EPC events
> to EPF
> PCI: endpoint: Replace spinlock with mutex
> PCI: endpoint: Fix for concurrent memory allocation in OB address
> region
> PCI: endpoint: Protect concurrent access to pci_epf_ops with mutex
> PCI: endpoint: Assign function number for each PF in EPC core
>
> drivers/pci/endpoint/functions/pci-epf-test.c | 13 +-
> drivers/pci/endpoint/pci-ep-cfs.c | 27 +----
> drivers/pci/endpoint/pci-epc-core.c | 113 ++++++++----------
> drivers/pci/endpoint/pci-epc-mem.c | 10 +-
> drivers/pci/endpoint/pci-epf-core.c | 33 ++---
> include/linux/pci-epc.h | 19 ++-
> include/linux/pci-epf.h | 9 +-
> 7 files changed, 108 insertions(+), 116 deletions(-)
Applied to pci/endpoint for v5.7, thanks.
Lorenzo
prev parent reply other threads:[~2020-02-24 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 9:53 [PATCH v3 0/5] PCI: Endpoint: Miscellaneous improvements Kishon Vijay Abraham I
2020-02-24 9:53 ` [PATCH v3 1/5] PCI: endpoint: Use notification chain mechanism to notify EPC events to EPF Kishon Vijay Abraham I
2020-02-24 9:59 ` Kishon Vijay Abraham I
2020-02-24 9:53 ` [PATCH v3 2/5] PCI: endpoint: Replace spinlock with mutex Kishon Vijay Abraham I
2020-02-24 9:53 ` [PATCH v3 3/5] PCI: endpoint: Fix for concurrent memory allocation in OB address region Kishon Vijay Abraham I
2020-02-24 9:53 ` [PATCH v3 4/5] PCI: endpoint: Protect concurrent access to pci_epf_ops with mutex Kishon Vijay Abraham I
2020-02-24 9:53 ` [PATCH v3 5/5] PCI: endpoint: Assign function number for each PF in EPC core Kishon Vijay Abraham I
2020-02-24 10:34 ` Lorenzo Pieralisi [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=20200224103436.GA8764@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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 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).