From: Jason Gunthorpe <jgg@nvidia.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: linuxppc-dev@lists.ozlabs.org,
Robin Murphy <robin.murphy@arm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Joerg Roedel <jroedel@suse.de>, Joel Stanley <joel@jms.id.au>,
Alex Williamson <alex.williamson@redhat.com>,
Oliver O'Halloran <oohall@gmail.com>,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org,
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] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains
Date: Fri, 08 Jul 2022 13:59:28 +0000 [thread overview]
Message-ID: <20220708135928.GA64621@nvidia.com> (raw)
In-Reply-To: <f2b51230-90b8-ecf0-8011-446e2f526bb4@ozlabs.ru>
On Fri, Jul 08, 2022 at 11:32:58PM +1000, Alexey Kardashevskiy wrote:
> > For power the default domain should be NULL
> >
> > NULL means that the platform is using the group to provide its DMA
> > ops. IIRC this patch was already setup correctly to do this?
> >
> > The transition from NULL to blocking must isolate the group so all DMA
> > is blocked. blocking to NULL should re-estbalish platform DMA API
> > control.
> >
> > The default domain should be non-NULL when the normal dma-iommu stuff is
> > providing the DMA API.
> >
> > So, I think it is already setup properly, it is just the question of
> > what to do when entering/leaving blocking mode.
>
> Well, the patch calls iommu_probe_device() which calls
> iommu_alloc_default_domain() which creates IOMMU_DOMAIN_BLOCKED
> (=0) as
Yes, we always create a blocking domain during probe, but it isn't
used until required
> nothing initialized iommu_def_domain_type. Need a different default type
> (and return NULL when IOMMU API tries creating this type)?
iommu_alloc_default_domain() should fail on power because none of the
domain types it tries to create are supported. This should result in a
NULL group->default_domain
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Joerg Roedel <jroedel@suse.de>,
kvm@vger.kernel.org, Fabiano Rosas <farosas@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Daniel Henrique Barboza <danielhb413@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
Murilo Opsfelder Araujo <muriloo@linux.ibm.com>,
kvm-ppc@vger.kernel.org,
Alex Williamson <alex.williamson@redhat.com>,
Oliver O'Halloran <oohall@gmail.com>,
Joel Stanley <joel@jms.id.au>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH kernel] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains
Date: Fri, 8 Jul 2022 10:59:28 -0300 [thread overview]
Message-ID: <20220708135928.GA64621@nvidia.com> (raw)
In-Reply-To: <f2b51230-90b8-ecf0-8011-446e2f526bb4@ozlabs.ru>
On Fri, Jul 08, 2022 at 11:32:58PM +1000, Alexey Kardashevskiy wrote:
> > For power the default domain should be NULL
> >
> > NULL means that the platform is using the group to provide its DMA
> > ops. IIRC this patch was already setup correctly to do this?
> >
> > The transition from NULL to blocking must isolate the group so all DMA
> > is blocked. blocking to NULL should re-estbalish platform DMA API
> > control.
> >
> > The default domain should be non-NULL when the normal dma-iommu stuff is
> > providing the DMA API.
> >
> > So, I think it is already setup properly, it is just the question of
> > what to do when entering/leaving blocking mode.
>
> Well, the patch calls iommu_probe_device() which calls
> iommu_alloc_default_domain() which creates IOMMU_DOMAIN_BLOCKED
> (==0) as
Yes, we always create a blocking domain during probe, but it isn't
used until required
> nothing initialized iommu_def_domain_type. Need a different default type
> (and return NULL when IOMMU API tries creating this type)?
iommu_alloc_default_domain() should fail on power because none of the
domain types it tries to create are supported. This should result in a
NULL group->default_domain
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: linuxppc-dev@lists.ozlabs.org,
Robin Murphy <robin.murphy@arm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Joerg Roedel <jroedel@suse.de>, Joel Stanley <joel@jms.id.au>,
Alex Williamson <alex.williamson@redhat.com>,
Oliver O'Halloran <oohall@gmail.com>,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org,
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] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains
Date: Fri, 8 Jul 2022 10:59:28 -0300 [thread overview]
Message-ID: <20220708135928.GA64621@nvidia.com> (raw)
In-Reply-To: <f2b51230-90b8-ecf0-8011-446e2f526bb4@ozlabs.ru>
On Fri, Jul 08, 2022 at 11:32:58PM +1000, Alexey Kardashevskiy wrote:
> > For power the default domain should be NULL
> >
> > NULL means that the platform is using the group to provide its DMA
> > ops. IIRC this patch was already setup correctly to do this?
> >
> > The transition from NULL to blocking must isolate the group so all DMA
> > is blocked. blocking to NULL should re-estbalish platform DMA API
> > control.
> >
> > The default domain should be non-NULL when the normal dma-iommu stuff is
> > providing the DMA API.
> >
> > So, I think it is already setup properly, it is just the question of
> > what to do when entering/leaving blocking mode.
>
> Well, the patch calls iommu_probe_device() which calls
> iommu_alloc_default_domain() which creates IOMMU_DOMAIN_BLOCKED
> (==0) as
Yes, we always create a blocking domain during probe, but it isn't
used until required
> nothing initialized iommu_def_domain_type. Need a different default type
> (and return NULL when IOMMU API tries creating this type)?
iommu_alloc_default_domain() should fail on power because none of the
domain types it tries to create are supported. This should result in a
NULL group->default_domain
Jason
next prev parent reply other threads:[~2022-07-08 13:59 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 13:55 [PATCH kernel] powerpc/iommu: Add iommu_ops to report capabilities and allow blocking domains Alexey Kardashevskiy
2022-07-07 13:55 ` Alexey Kardashevskiy
2022-07-07 13:55 ` Alexey Kardashevskiy
2022-07-07 15:10 ` Jason Gunthorpe
2022-07-07 15:10 ` Jason Gunthorpe
2022-07-07 15:10 ` Jason Gunthorpe
2022-07-08 4:58 ` Alexey Kardashevskiy
2022-07-08 5:00 ` Alexey Kardashevskiy
2022-07-08 5:00 ` Alexey Kardashevskiy
2022-07-08 6:34 ` Alexey Kardashevskiy
2022-07-08 6:34 ` Alexey Kardashevskiy
2022-07-08 6:34 ` Alexey Kardashevskiy
2022-07-08 7:32 ` Tian, Kevin
2022-07-08 7:32 ` Tian, Kevin
2022-07-08 7:32 ` Tian, Kevin
2022-07-08 9:45 ` Alexey Kardashevskiy
2022-07-08 9:45 ` Alexey Kardashevskiy
2022-07-08 9:45 ` Alexey Kardashevskiy
2022-07-08 10:18 ` Tian, Kevin
2022-07-08 10:18 ` Tian, Kevin
2022-07-08 10:18 ` Tian, Kevin
2022-07-29 2:21 ` Alexey Kardashevskiy
2022-07-29 2:21 ` Alexey Kardashevskiy
2022-07-29 2:21 ` Alexey Kardashevskiy
2022-07-29 2:53 ` Oliver O'Halloran
2022-07-29 2:53 ` Oliver O'Halloran
2022-07-29 2:53 ` Oliver O'Halloran
2022-07-29 3:10 ` Tian, Kevin
2022-07-29 3:10 ` Tian, Kevin
2022-07-29 3:10 ` Tian, Kevin
2022-07-29 3:50 ` Alexey Kardashevskiy
2022-07-29 3:50 ` Alexey Kardashevskiy
2022-07-29 3:50 ` Alexey Kardashevskiy
2022-07-29 4:24 ` Tian, Kevin
2022-07-29 4:24 ` Tian, Kevin
2022-07-29 4:24 ` Tian, Kevin
2022-07-29 12:09 ` Jason Gunthorpe
2022-07-29 12:09 ` Jason Gunthorpe
2022-07-29 12:09 ` Jason Gunthorpe
2022-07-08 11:55 ` Jason Gunthorpe
2022-07-08 11:55 ` Jason Gunthorpe
2022-07-08 11:55 ` Jason Gunthorpe
2022-07-08 13:10 ` Alexey Kardashevskiy
2022-07-08 13:10 ` Alexey Kardashevskiy
2022-07-08 13:10 ` Alexey Kardashevskiy
2022-07-08 13:19 ` Jason Gunthorpe
2022-07-08 13:19 ` Jason Gunthorpe
2022-07-08 13:19 ` Jason Gunthorpe
2022-07-08 13:32 ` Alexey Kardashevskiy
2022-07-08 13:32 ` Alexey Kardashevskiy
2022-07-08 13:32 ` Alexey Kardashevskiy
2022-07-08 13:59 ` Jason Gunthorpe [this message]
2022-07-08 13:59 ` Jason Gunthorpe
2022-07-08 13:59 ` Jason Gunthorpe
2022-07-09 2:58 ` Alexey Kardashevskiy
2022-07-09 2:58 ` Alexey Kardashevskiy
2022-07-09 2:58 ` Alexey Kardashevskiy
2022-07-10 6:29 ` Jason Gunthorpe
2022-07-10 6:29 ` Jason Gunthorpe
2022-07-10 6:29 ` Jason Gunthorpe
2022-07-10 12:32 ` Alexey Kardashevskiy
2022-07-10 12:32 ` Alexey Kardashevskiy
2022-07-10 12:32 ` Alexey Kardashevskiy
2022-07-11 13:24 ` Alexey Kardashevskiy
2022-07-11 13:24 ` Alexey Kardashevskiy
2022-07-11 13:24 ` Alexey Kardashevskiy
2022-07-11 18:46 ` Jason Gunthorpe
2022-07-11 18:46 ` Jason Gunthorpe
2022-07-11 18:46 ` Jason Gunthorpe
2022-07-12 2:27 ` Alexey Kardashevskiy
2022-07-12 2:27 ` Alexey Kardashevskiy
2022-07-12 2:27 ` Alexey Kardashevskiy
2022-07-12 5:44 ` Jason Gunthorpe
2022-07-12 5:44 ` Jason Gunthorpe
2022-07-12 5:44 ` 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=20220708135928.GA64621@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=joel@jms.id.au \
--cc=jroedel@suse.de \
--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=oohall@gmail.com \
--cc=robin.murphy@arm.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.