From: "Bryant G. Ly" <bryantly@linux.vnet.ibm.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>,
helgaas@kernel.org, bhelgaas@google.com,
benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au
Cc: seroyer@linux.vnet.ibm.com, jjalvare@linux.vnet.ibm.com,
alex.williamson@redhat.com, linux-pci@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, bodong@mellanox.com,
eli@mellanox.com, saeedm@mellanox.com
Subject: Re: [PATCH v5 0/3] Prepartion for SR-IOV PowerVM Enablement
Date: Fri, 8 Dec 2017 08:52:57 -0600 [thread overview]
Message-ID: <daf93824-1f46-a4ab-050d-180cd3765816@linux.vnet.ibm.com> (raw)
In-Reply-To: <e4b660df-f23d-9f4f-6b1b-d681e4ff8bae@ozlabs.ru>
On 12/8/17 12:03 AM, Alexey Kardashevskiy wrote:
> On 06/12/17 02:13, Bryant G. Ly wrote:
>>
>> On 12/4/17 7:24 PM, Alexey Kardashevskiy wrote:
>>> On 05/12/17 02:08, Bryant G. Ly wrote:
>>>> On 12/2/17 7:45 PM, Alexey Kardashevskiy wrote:
>>>>> On 10/11/17 01:00, Bryant G. Ly wrote:
>>>>>> v1 - Initial patch
>>>>>> v2 - Addressed Bjorn's comment on creating a highly platform
>>>>>> dependent global exported symbol.
>>>>>> v3 - Based patch off linux-ppc/master
>>>>>> v4 - Using the sriov-drivers_autoprobe mechanism per Bjorn's request
>>>>>> v5 - Fixed comments and commit message
>>>>> What is this made against of? I'd like to give it a try but it does not
>>>>> apply to Linus'es tree or powerpc/next. Thanks.
>>>>>
>>>> This was made against powerpc/next back when it was still under 4.14-rc6.
>>>> It has been in review for awhile...
>>> Sure, sha1 or github tree would be enough though to try.
>> 6cff0a118f23b98c604a3604ea9de11338e24fbe
>>
>> or if you want to just use the github tree its:
>>
>> https://github.com/powervm/sriov-ppc/tree/upstream
>
> Thanks! Looks good, works fine (tried MLX5 wit hpowernv - works, pseries
> under KVM - prints a nice error instead of crashing),
>
> Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>
>
Thanks for the review/testing. I will drop the full patch that enables SRIOV on PowerVM next week.
The patch will require unreleased PHYP and PFW firmware to fully function.
I will include you and Russell to those patches.
-Bryant
>
>>>> -Bryant
>>>>
>>>>>> Bryant G. Ly (3):
>>>>>> powerpc/kernel: Separate SR-IOV Calls
>>>>>> pseries: Add PSeries SR-IOV Machine dependent calls
>>>>>> PCI/IOV: Add pci_vf_drivers_autoprobe() interface
>>>>>>
>>>>>> arch/powerpc/include/asm/machdep.h | 7 ++++++
>>>>>> arch/powerpc/include/asm/pci-bridge.h | 4 +---
>>>>>> arch/powerpc/kernel/eeh_driver.c | 4 ++--
>>>>>> arch/powerpc/kernel/pci-common.c | 23 +++++++++++++++++++
>>>>>> arch/powerpc/kernel/pci_dn.c | 6 -----
>>>>>> arch/powerpc/platforms/powernv/eeh-powernv.c | 33 ++++++++++++++--------------
>>>>>> arch/powerpc/platforms/powernv/pci-ioda.c | 6 +++--
>>>>>> arch/powerpc/platforms/pseries/eeh_pseries.c | 24 ++++++++++++++++++++
>>>>>> arch/powerpc/platforms/pseries/pci.c | 31 ++++++++++++++++++++++----
>>>>>> drivers/pci/iov.c | 11 ++++++++++
>>>>>> include/linux/pci.h | 2 ++
>>>>>> 11 files changed, 118 insertions(+), 33 deletions(-)
>>>>>>
>
next prev parent reply other threads:[~2017-12-08 14:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 14:00 [PATCH v5 0/3] Prepartion for SR-IOV PowerVM Enablement Bryant G. Ly
2017-11-09 14:00 ` [PATCH v5 1/3] powerpc/kernel: Separate SR-IOV Calls Bryant G. Ly
2017-12-12 11:39 ` [v5,1/3] " Michael Ellerman
2017-11-09 14:00 ` [PATCH v5 2/3] pseries: Add PSeries SR-IOV Machine dependent calls Bryant G. Ly
2017-11-09 14:00 ` [PATCH v5 3/3] PCI/IOV: Add pci_vf_drivers_autoprobe() interface Bryant G. Ly
2017-11-29 16:13 ` [PATCH v5 0/3] Prepartion for SR-IOV PowerVM Enablement Bryant G. Ly
2017-12-01 11:48 ` Michael Ellerman
2017-12-03 1:45 ` Alexey Kardashevskiy
2017-12-04 15:08 ` Bryant G. Ly
2017-12-05 1:24 ` Alexey Kardashevskiy
2017-12-05 15:13 ` Bryant G. Ly
2017-12-08 6:03 ` Alexey Kardashevskiy
2017-12-08 14:52 ` Bryant G. Ly [this message]
2017-12-04 4:48 ` Russell Currey
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=daf93824-1f46-a4ab-050d-180cd3765816@linux.vnet.ibm.com \
--to=bryantly@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=bodong@mellanox.com \
--cc=eli@mellanox.com \
--cc=helgaas@kernel.org \
--cc=jjalvare@linux.vnet.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=saeedm@mellanox.com \
--cc=seroyer@linux.vnet.ibm.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).