lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20151201151510.GB18805@8bytes.org>
Date:	Tue, 1 Dec 2015 16:15:10 +0100
From:	Joerg Roedel <joro@...tes.org>
To:	Yong Wu <yong.wu@...iatek.com>
Cc:	iommu@...ts.linux-foundation.org,
	Will Deacon <will.deacon@....com>,
	linux-kernel@...r.kernel.org, yingjoe.chen@...iatek.com,
	srv_heupstream@...iatek.com, Daniel Kurtz <djkurtz@...gle.com>,
	Tomasz Figa <tfiga@...gle.com>, eddie.huang@...iatek.com,
	Matthias Brugger <matthias.bgg@...il.com>
Subject: Re: [PATCH 0/8] iommu: Make core iommu-groups code more generic

Hi Yong Wu,

On Tue, Dec 01, 2015 at 07:29:51PM +0800, Yong Wu wrote:
>      Currently We have to use iommu_detach_group and iommu_attach_group.
> Is there any plan for adding detach/attach the device within a iommu
> group?

No, there is no such plan. The reason is using attach/detach_device
always also affects the other devices in the iommu-group. Therefore
attach/detach_device was limited to devices which have no others in
their group.
Having attach/detach_group makes it more obvious to the user that the
call affects more than one device.


	Joerg

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ