On 7/12/2016 5:02 PM, Yu Zhang wrote:
XenGT leverages ioreq server to track and forward the accesses to GPU
I/O resources, e.g. the PPGTT(per-process graphic translation tables).
Currently, ioreq server uses rangeset to track the BDF/ PIO/MMIO ranges
to be emulated. To select an ioreq server, the rangeset is searched to
see if the I/O range is recorded. However, number of ram pages to be
tracked may exceed the upper limit of rangeset.
Previously, one solution was proposed to refactor the rangeset, and
extend its upper limit. However, after 12 rounds discussion, we have
decided to drop this approach due to security concerns. Now this new
patch series introduces a new mem type, HVMMEM_ioreq_server, and added
hvm operations to let one ioreq server to claim its ownership of ram
pages with this type. Accesses to a page of this type will be handled
by the specified ioreq server directly.
Yu Zhang (4):
x86/ioreq server: Rename p2m_mmio_write_dm to p2m_ioreq_server.
x86/ioreq server: Add new functions to get/set memory types.
x86/ioreq server: Add HVMOP to map guest ram with p2m_ioreq_server to
an ioreq server.
x86/ioreq server: Reset outstanding p2m_ioreq_server entries when an
ioreq server unmaps.
xen/arch/x86/hvm/emulate.c | 33 +++-
xen/arch/x86/hvm/hvm.c | 395 ++++++++++++++++++++++++++-------------
xen/arch/x86/hvm/ioreq.c | 41 ++++
xen/arch/x86/mm/hap/hap.c | 9 +
xen/arch/x86/mm/hap/nested_hap.c | 2 +-
xen/arch/x86/mm/p2m-ept.c | 14 +-
xen/arch/x86/mm/p2m-pt.c | 30 ++-
xen/arch/x86/mm/p2m.c | 77 ++++++++
xen/arch/x86/mm/shadow/multi.c | 3 +-
xen/include/asm-x86/hvm/ioreq.h | 2 +
xen/include/asm-x86/p2m.h | 36 +++-
xen/include/public/hvm/hvm_op.h | 34 +++-
12 files changed, 528 insertions(+), 148 deletions(-)
Hi Jan & George, any comments on this version? :)
Sorry if this mail disturbs, but it has been more than 3 weeks since the
post...
Thanks
Yu
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
