From: Timothy Pearson <tpearson@raptorengineering.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Timothy Pearson <tpearson@raptorengineering.com>,
kvm <kvm@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2 0/4] Reenable VFIO support on POWER systems
Date: Thu, 9 Mar 2023 13:28:20 -0600 (CST) [thread overview]
Message-ID: <1816556668.17777469.1678390100763.JavaMail.zimbra@raptorengineeringinc.com> (raw)
In-Reply-To: <87bkl2ywz2.fsf@mpe.ellerman.id.au>
----- Original Message -----
> From: "Michael Ellerman" <mpe@ellerman.id.au>
> To: "Timothy Pearson" <tpearson@raptorengineering.com>, "kvm" <kvm@vger.kernel.org>
> Cc: "linuxppc-dev" <linuxppc-dev@lists.ozlabs.org>
> Sent: Thursday, March 9, 2023 5:40:01 AM
> Subject: Re: [PATCH v2 0/4] Reenable VFIO support on POWER systems
> Timothy Pearson <tpearson@raptorengineering.com> writes:
>> This patch series reenables VFIO support on POWER systems. It
>> is based on Alexey Kardashevskiys's patch series, rebased and
>> successfully tested under QEMU with a Marvell PCIe SATA controller
>> on a POWER9 Blackbird host.
>>
>> Alexey Kardashevskiy (3):
>> powerpc/iommu: Add "borrowing" iommu_table_group_ops
>> powerpc/pci_64: Init pcibios subsys a bit later
>> powerpc/iommu: Add iommu_ops to report capabilities and allow blocking
>> domains
>
> As sent the patches had lost Alexey's authorship (no From: line), I
> fixed it up when applying so the first 3 are authored by Alexey.
>
> cheers
Thanks for catching that, it wasn't intentional. Probably used a wrong Git command...
next prev parent reply other threads:[~2023-03-09 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 17:29 [PATCH v2 0/4] Reenable VFIO support on POWER systems Timothy Pearson
2023-03-06 23:46 ` Alex Williamson
2023-03-07 0:35 ` Timothy Pearson
2023-03-07 0:59 ` Alex Williamson
2023-03-07 23:04 ` Timothy Pearson
2023-03-07 0:51 ` Alexey Kardashevskiy
2023-03-09 11:38 ` Michael Ellerman
2023-03-09 11:40 ` Michael Ellerman
2023-03-09 19:28 ` Timothy Pearson [this message]
2023-03-18 19:06 ` Timothy Pearson
2023-03-21 10:33 ` Michael Ellerman
2023-03-21 13:18 ` Timothy Pearson
2023-03-21 21:43 ` Michael Ellerman
2023-03-23 6:49 ` Narayana Murty
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=1816556668.17777469.1678390100763.JavaMail.zimbra@raptorengineeringinc.com \
--to=tpearson@raptorengineering.com \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.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).