 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] DMA understanding
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] DMA understanding |
| 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 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.in; s=s1024; t=1277750448; bh=V/p66NuPNoMnXgTGzYS3OJsC/Z9plfvyLRoe5jLJT5Q=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=3Ajy8lENzmpy4ZPkKVfBLUy6Z6GHw8XRSGCEYWKlivMH9jhX4wRamDJ4Db/MsJqBLZaCfPO2+Rnk/S2djpt7+wid1xOBncTKIpYWCohyAihEd5DjwCXBYQu0RySsyPLP53oRB0rJGhCCpVAafxjutNI9AJycdB2Sy72XUMTWlv4= |
| 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=; |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] domU and dom0 hung with Xen console interrupt binding showing in-flight=1, (---M), Dante Cinco |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH] Fix etherboot option ROM loading, Keir Fraser |
| Previous by Thread: | [Xen-devel] domU and dom0 hung with Xen console interrupt binding showing in-flight=1, (---M), Dante Cinco |
| Next by Thread: | Re: [Xen-devel] DMA understanding, Konrad Rzeszutek Wilk |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
