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-next>] [day] [month] [year] [list]
Message-ID: <CA+QbAV6-C9wxPttEx0uDn_K5Y1LaGt8pxDWc8RJmN4DqR+NHtQ@mail.gmail.com>
Date:	Wed, 15 Oct 2014 16:44:34 -0700
From:	Kallol Biswas <nucleodyne@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: PCIe PASID (Process Address Space ID) and iommu code

Resending, as message got bounced for html content.
--------------------------------------------
Hi,
    PCIe has introduced PASID TLP Prefix.  There are two ECNs on this.

It seems that AMD iommu code makes use of PASID. Is there a device that
utilizes this TLP prefix?

PASID allocation and management within a device is not clear to me. How
does device know which PASID to issue for which virtual address? Who makes
the association? Must be software/OS, but how? There is no table for this
like MSI-X table.

Any pointer/documentation will be appreciated.

Regards,
--
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