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] [thread-next>] [day] [month] [year] [list]
Message-ID: <15060.1317237495@turing-police.cc.vt.edu>
Date:	Wed, 28 Sep 2011 15:18:15 -0400
From:	Valdis.Kletnieks@...edu
To:	Joerg Roedel <joro@...tes.org>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>,
	Joerg Roedel <joerg.roedel@....com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4] PCI: Add support for PASID capability

On Tue, 27 Sep 2011 00:15:39 +0200, Joerg Roedel said:

> PASID stands for Process Address Space ID, it basically allows a PCI
> device to access multiple IO address spaces at the same time using an
> IOMMU. Users should enable it when they want to compile an IOMMU driver
> into the kernel that supports PASIDs for the translated devices.
> I'll add all that information to the Kconfig help. Thanks a lot for your
> feedback :)

Is this a case where the PCI device drivers in question should be doing a
'select' or 'depends on' if they support talking to an IOMMU using PASID?

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ