aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/thermal
diff options
context:
space:
mode:
authorKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2010-05-11 10:05:49 -0400
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2010-07-27 11:51:00 -0400
commitb097186fd29d5bc5a26d1ae87995821ffc27b66e (patch)
tree64aeb8bf4f6e0eea409d4ad5e12d9788a136732c /Documentation/thermal
parentd2cb214551de8180542a04ec8c86c0c9412c5124 (diff)
downloadkernel_samsung_aries-b097186fd29d5bc5a26d1ae87995821ffc27b66e.zip
kernel_samsung_aries-b097186fd29d5bc5a26d1ae87995821ffc27b66e.tar.gz
kernel_samsung_aries-b097186fd29d5bc5a26d1ae87995821ffc27b66e.tar.bz2
swiotlb-xen: SWIOTLB library for Xen PV guest with PCI passthrough.
This patchset: PV guests under Xen are running in an non-contiguous memory architecture. When PCI pass-through is utilized, this necessitates an IOMMU for translating bus (DMA) to virtual and vice-versa and also providing a mechanism to have contiguous pages for device drivers operations (say DMA operations). Specifically, under Xen the Linux idea of pages is an illusion. It assumes that pages start at zero and go up to the available memory. To help with that, the Linux Xen MMU provides a lookup mechanism to translate the page frame numbers (PFN) to machine frame numbers (MFN) and vice-versa. The MFN are the "real" frame numbers. Furthermore memory is not contiguous. Xen hypervisor stitches memory for guests from different pools, which means there is no guarantee that PFN==MFN and PFN+1==MFN+1. Lastly with Xen 4.0, pages (in debug mode) are allocated in descending order (high to low), meaning the guest might never get any MFN's under the 4GB mark. Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> Cc: Albert Herranz <albert_herranz@yahoo.es> Cc: Ian Campbell <Ian.Campbell@citrix.com>
Diffstat (limited to 'Documentation/thermal')
0 files changed, 0 insertions, 0 deletions