> > The present value shows the existing type of default domain.
> > If user wants to change it (Eg: from DMA to IDENTITY or vice versa), he
> attempts to write the new value.
> > Kernel performs checks to make sure that the driver in unbinded and it's
> > safe
> to change the default domain
On Tue, Jun 11, 2019 at 05:27:15PM +, Prakhya, Sai Praneeth wrote:
> 1. Since we already have "type" file, which is "read-only", we could make it
> R/W.
>
> The present value shows the existing type of default domain.
> If user wants to change it (Eg: from DMA to IDENTITY or vice versa), he
> > > > Sure! Makes sense.. per-group default domain type sounds good.
> >
> > I am planning to implement an RFC (supporting only runtime case for
> > now) which works as below
> >
> > 1. User unbinds the driver by writing to sysfs 2. User puts a group in
> > pass through mode by writing "1" to
>
On Mon, Jun 10, 2019 at 09:38:11PM -0700, Sai Praneeth Prakhya wrote:
> Hi All,
>
> + Sohil and Rob Clark (as there are dropped from CC'list)
>
> > > > Most iommu vendor drivers have switched from per-device to per-group
> > > > domain (a.k.a. default domain). So per-group pass-through mode
Hi All,
+ Sohil and Rob Clark (as there are dropped from CC'list)
> > > Most iommu vendor drivers have switched from per-device to per-group
> > > domain (a.k.a. default domain). So per-group pass-through mode makes
> more sense?
> > >
> > > By the way, can we extend this to "per-group default
Hi Sai
On Sun, Jun 09, 2019 at 10:41:10PM -0700, Sai Praneeth Prakhya wrote:
> > > I am working on an IOMMU driver feature that allows a user to specify
> > > if the DMA from a device should be translated by IOMMU or not.
> > > Presently, we support only all devices or none mode i.e. if user
> >
> > I am working on an IOMMU driver feature that allows a user to specify
> > if the DMA from a device should be translated by IOMMU or not.
> > Presently, we support only all devices or none mode i.e. if user
> > specifies "iommu=pt" [X86] or "iommu.passthrough" [ARM64] through
> > kernel command
Hi Sai,
On 6/7/19 10:24 AM, Prakhya, Sai Praneeth wrote:
Hi All,
I am working on an IOMMU driver feature that allows a user to specify if
the DMA from a device should be translated by IOMMU or not. Presently,
we support only all devices or none mode i.e. if user specifies
“iommu=pt” [X86]
On Sat, 2019-06-08 at 09:27 +0200, h...@lst.de wrote:
> Just curious, what exactly is the use case? Explaining how someone
> would wan to use this should drive the way we design an interface for it.
Makes sense.
Some example use cases:
1. Assume an SR-IOV device and if the admin decides to use
Just curious, what exactly is the use case? Explaining how someone
would wan to use this should drive the way we design an interface for it.
___
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
> It's interesting to see this from a fresh angle which isn't clouded by
> other SoC GPU details - thanks for the proposal! A couple more thoughts
> jump out immediately...
>
Thanks a lot! for jumping in and providing your valuable insights :)
Sorry! for taking time to reply on this. Did
On 07/06/2019 03:24, Prakhya, Sai Praneeth wrote:
Hi All,
I am working on an IOMMU driver feature that allows a user to specify if the DMA from a device
should be translated by IOMMU or not. Presently, we support only all devices or none mode i.e. if
user specifies "iommu=pt" [X86] or
Hi All,
I am working on an IOMMU driver feature that allows a user to specify if the
DMA from a device should be translated by IOMMU or not. Presently, we support
only all devices or none mode i.e. if user specifies "iommu=pt" [X86] or
"iommu.passthrough" [ARM64] through kernel command line,
13 matches
Mail list logo
