On Thu, Jul 01, 2010 at 12:16:18AM -0700, Zach Pfeffer wrote:
Thank you for the corrections. I'm correcting them now. Some responses:
Randy Dunlap wrote:
+struct vcm *vcm_create(size_t start_addr, size_t len);
Seems odd to use size_t for start_addr.
I used size_t because I wanted
Thank you for the corrections. I'm correcting them now. Some responses:
Randy Dunlap wrote:
+struct vcm *vcm_create(size_t start_addr, size_t len);
Seems odd to use size_t for start_addr.
I used size_t because I wanted to allow the start_addr the same range
as len. Is there a better type
On Tue, 29 Jun 2010 22:55:48 -0700 Zach Pfeffer wrote:
This patch contains the documentation for the API, termed the Virtual
Contiguous Memory Manager. Its use would allow all of the IOMMU to VM,
VM to device and device to IOMMU interoperation code to be refactored
into platform independent
This patch contains the documentation for the API, termed the Virtual
Contiguous Memory Manager. Its use would allow all of the IOMMU to VM,
VM to device and device to IOMMU interoperation code to be refactored
into platform independent code.
Comments, suggestions and criticisms are welcome and