|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Memory Mapped IO devices in a domU
On 12/10/2010 12:49 PM, Ian Pratt wrote:
How would one pass a memory mapped device to a domU? In particular I'm
trying to pass the TPM to a domU. It is a memory mapped device with 5
pages starting at 0xfed40000.
You probably actually want to pass locality 0 through to the guest, which is
one page starting at 0xfed40000.
You can do this by adding the relevant mmio passthrough option to the domain
config file [I forget the actual name].
The easiest way to ensure you're not using the device in dom0 is just not to
load the TPM driver. Alternatively, modify the dom0 driver to use another TPM
locality e.g. 1 (the page above).
Ian
Does such an option even exist? I'm looking through the xm scripts in
tools/python and I see options for iports and irqs, but nothing for
memory mapped io.
Currently I'm playing with the memory_op hypercall, using
XENMEN_add_to_phys but its failing and I'm currently investigating why.
Is this even the right hypercall to use for this? How do I deal with the
fact that the device is already mapped into dom0 by default? Do I need to
explicitly unmap the pages from dom0 first somehow?
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|