From: Jason Gunthorpe <jgg@nvidia.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
kvm-ppc@vger.kernel.org, Deming Wang <wangdeming@inspur.com>,
Robin Murphy <robin.murphy@arm.com>,
Alex Williamson <alex.williamson@redhat.com>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
Fabiano Rosas <farosas@linux.ibm.com>,
Murilo Opsfelder Araujo <muriloo@linux.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH kernel 0/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains
Date: Fri, 2 Sep 2022 08:46:19 -0300 [thread overview]
Message-ID: <YxHtC5xw9KBZ6hSc@nvidia.com> (raw)
In-Reply-To: <87tu5qtelx.fsf@mpe.ellerman.id.au>
On Fri, Sep 02, 2022 at 05:33:30PM +1000, Michael Ellerman wrote:
> Jason Gunthorpe <jgg@nvidia.com> writes:
> > On Thu, Jul 14, 2022 at 06:18:19PM +1000, Alexey Kardashevskiy wrote:
> >> Here is another take on iommu_ops on POWER to make VFIO work
> >> again on POWERPC64.
> >>
> >> The tree with all prerequisites is here:
> >> https://github.com/aik/linux/tree/kvm-fixes-wip
> >>
> >> The previous discussion is here:
> >> https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220707135552.3688927-1-aik@ozlabs.ru/
> >> https://patchwork.ozlabs.org/project/kvm-ppc/patch/20220701061751.1955857-1-aik@ozlabs.ru/
> >>
> >> Please comment. Thanks.
> >>
> >>
> >>
> >> 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
> >
> > It has been a little while - and I think this series is still badly
> > needed by powerpc, right?
>
> Your comments on patch 3 left me with the impression it needed a respin,
> but maybe I misread that.
It would be nice, but I understand Alexey will not work on it anymore,
so I wouldn't object to as-is
> Alexey's reply that it needed testing also made me think it wasn't
> ready to pick up.
Well, if so, someone still needs to finish this work. But I think he
tested it, he fixed things that could have only been found by
testing..
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: kvm@vger.kernel.org, Fabiano Rosas <farosas@linux.ibm.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Robin Murphy <robin.murphy@arm.com>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
Deming Wang <wangdeming@inspur.com>,
kvm-ppc@vger.kernel.org,
Alex Williamson <alex.williamson@redhat.com>,
Nicholas Piggin <npiggin@gmail.com>,
Murilo Opsfelder Araujo <muriloo@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH kernel 0/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains
Date: Fri, 2 Sep 2022 08:46:19 -0300 [thread overview]
Message-ID: <YxHtC5xw9KBZ6hSc@nvidia.com> (raw)
In-Reply-To: <87tu5qtelx.fsf@mpe.ellerman.id.au>
On Fri, Sep 02, 2022 at 05:33:30PM +1000, Michael Ellerman wrote:
> Jason Gunthorpe <jgg@nvidia.com> writes:
> > On Thu, Jul 14, 2022 at 06:18:19PM +1000, Alexey Kardashevskiy wrote:
> >> Here is another take on iommu_ops on POWER to make VFIO work
> >> again on POWERPC64.
> >>
> >> The tree with all prerequisites is here:
> >> https://github.com/aik/linux/tree/kvm-fixes-wip
> >>
> >> The previous discussion is here:
> >> https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220707135552.3688927-1-aik@ozlabs.ru/
> >> https://patchwork.ozlabs.org/project/kvm-ppc/patch/20220701061751.1955857-1-aik@ozlabs.ru/
> >>
> >> Please comment. Thanks.
> >>
> >>
> >>
> >> 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
> >
> > It has been a little while - and I think this series is still badly
> > needed by powerpc, right?
>
> Your comments on patch 3 left me with the impression it needed a respin,
> but maybe I misread that.
It would be nice, but I understand Alexey will not work on it anymore,
so I wouldn't object to as-is
> Alexey's reply that it needed testing also made me think it wasn't
> ready to pick up.
Well, if so, someone still needs to finish this work. But I think he
tested it, he fixed things that could have only been found by
testing..
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
kvm-ppc@vger.kernel.org, Deming Wang <wangdeming@inspur.com>,
Robin Murphy <robin.murphy@arm.com>,
Alex Williamson <alex.williamson@redhat.com>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
Fabiano Rosas <farosas@linux.ibm.com>,
Murilo Opsfelder Araujo <muriloo@linux.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH kernel 0/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domain
Date: Fri, 02 Sep 2022 11:46:19 +0000 [thread overview]
Message-ID: <YxHtC5xw9KBZ6hSc@nvidia.com> (raw)
In-Reply-To: <87tu5qtelx.fsf@mpe.ellerman.id.au>
On Fri, Sep 02, 2022 at 05:33:30PM +1000, Michael Ellerman wrote:
> Jason Gunthorpe <jgg@nvidia.com> writes:
> > On Thu, Jul 14, 2022 at 06:18:19PM +1000, Alexey Kardashevskiy wrote:
> >> Here is another take on iommu_ops on POWER to make VFIO work
> >> again on POWERPC64.
> >>
> >> The tree with all prerequisites is here:
> >> https://github.com/aik/linux/tree/kvm-fixes-wip
> >>
> >> The previous discussion is here:
> >> https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220707135552.3688927-1-aik@ozlabs.ru/
> >> https://patchwork.ozlabs.org/project/kvm-ppc/patch/20220701061751.1955857-1-aik@ozlabs.ru/
> >>
> >> Please comment. Thanks.
> >>
> >>
> >>
> >> 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
> >
> > It has been a little while - and I think this series is still badly
> > needed by powerpc, right?
>
> Your comments on patch 3 left me with the impression it needed a respin,
> but maybe I misread that.
It would be nice, but I understand Alexey will not work on it anymore,
so I wouldn't object to as-is
> Alexey's reply that it needed testing also made me think it wasn't
> ready to pick up.
Well, if so, someone still needs to finish this work. But I think he
tested it, he fixed things that could have only been found by
testing..
Jason
next prev parent reply other threads:[~2022-09-02 11:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 8:18 [PATCH kernel 0/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains Alexey Kardashevskiy
2022-07-14 8:18 ` Alexey Kardashevskiy
2022-07-14 8:18 ` Alexey Kardashevskiy
2022-07-14 8:18 ` [PATCH kernel 1/3] powerpc/iommu: Add "borrowing" iommu_table_group_ops Alexey Kardashevskiy
2022-07-14 8:18 ` Alexey Kardashevskiy
2022-07-14 8:18 ` Alexey Kardashevskiy
2022-07-18 16:49 ` Jason Gunthorpe
2022-07-18 16:49 ` Jason Gunthorpe
2022-07-18 16:49 ` Jason Gunthorpe
2022-07-14 8:18 ` [PATCH kernel 2/3] powerpc/pci_64: Init pcibios subsys a bit later Alexey Kardashevskiy
2022-07-14 8:18 ` Alexey Kardashevskiy
2022-07-14 8:18 ` Alexey Kardashevskiy
2022-07-18 16:49 ` Jason Gunthorpe
2022-07-18 16:49 ` Jason Gunthorpe
2022-07-18 16:49 ` Jason Gunthorpe
2022-07-14 8:18 ` [PATCH kernel 3/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains Alexey Kardashevskiy
2022-07-14 8:18 ` Alexey Kardashevskiy
2022-07-14 8:18 ` Alexey Kardashevskiy
2022-07-18 18:09 ` Jason Gunthorpe
2022-07-18 18:09 ` [PATCH kernel 3/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domain Jason Gunthorpe
2022-07-18 18:09 ` [PATCH kernel 3/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains Jason Gunthorpe
2022-07-19 3:18 ` Alexey Kardashevskiy
2022-07-19 3:18 ` [PATCH kernel 3/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domain Alexey Kardashevskiy
2022-07-19 3:18 ` [PATCH kernel 3/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains Alexey Kardashevskiy
2022-09-02 0:20 ` [PATCH kernel 0/3] " Jason Gunthorpe
2022-09-02 0:20 ` [PATCH kernel 0/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domain Jason Gunthorpe
2022-09-02 0:20 ` [PATCH kernel 0/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains Jason Gunthorpe
2022-09-02 7:33 ` Michael Ellerman
2022-09-02 7:33 ` [PATCH kernel 0/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domain Michael Ellerman
2022-09-02 7:33 ` [PATCH kernel 0/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains Michael Ellerman
2022-09-02 11:46 ` Jason Gunthorpe [this message]
2022-09-02 11:46 ` [PATCH kernel 0/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domain Jason Gunthorpe
2022-09-02 11:46 ` [PATCH kernel 0/3] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains Jason Gunthorpe
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=YxHtC5xw9KBZ6hSc@nvidia.com \
--to=jgg@nvidia.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=danielhb413@gmail.com \
--cc=farosas@linux.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=muriloo@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=robin.murphy@arm.com \
--cc=wangdeming@inspur.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.