[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] DMA understanding


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Abhinav Srivastava <abhinavs_iitkgp@xxxxxxxxxxx>
  • Date: Tue, 29 Jun 2010 00:10:48 +0530 (IST)
  • Delivery-date: Mon, 28 Jun 2010 11:41:33 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ISVe12so6R71AZA6ftOd+xjsatMSC/3mXu9wseGKuXzy3Whqfiaur1Q5LkJBGzT0RkfVyVf1GtUw6nX8WQgEO2ANc96zy1xjNWSX0mZRD8rqi73ydr8ALsXNN2cUuKNYdpOVWsoBPGxL8Xm2H46gx4sqbUFX07tPmbzxsn1BxY4=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi there,

I am trying to understand how an HVM guest domain performs its DMA operations, 
and how this DMA operations are intercepted by the Xen. I wanted to understand 
both the code path with and without Vt-d support (for intel processors). On 
looking inside the Xen code, I found that iommu code is inside the vmx/vtd/ 
directory only. By seeing the code, my understanding is that when Vt-d is 
enabled, iommu.c and dmar.c inside the vtd directory is the place to look for 
DMA operations. However, I do not understand which code path inside the 
hypervisor is getting used in case of Vt-d is disabled?  How does Xen intercept 
guest DMA operations in this case? I am using Xen 3.3 version for my project (I 
admit that it is very old version).

Any help would be appreciated.

Thanks,
Abhinav





_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.