[PATCH v5 0/3] Extend ioreq server to support multiple ioreq pages

["Julian Vetter" <julian.vetter@xxxxxxxxxx>]

Thank you again Jan for you feedback on the series! As you suggested I
have kept the struct ioreq_page fully intakt and just dropped the struct
page_info *page, because I have replaced the __map_domain_page_global()
by an explicit vmap(). So, the page can be recovered via vmap_to_page().
My only concern with my patch series is that in non-debug builds on x86,
map_domain_page_global() avoids vmap overhead for low MFNs by directly
returning a directmap address. But when switching to vmap()
unconditionally this optimization is gone. But this is required so that
vmap_to_page() works correctly and can recover the struct page_info *
uniformly at teardown. What do you think?

Julian Vetter (3):
  ioreq: Unify buf and non-buf ioreq page management
  ioreq: Indent ioreq_server_{alloc,free}_mfn() body one level deeper
  x86/ioreq: Extend ioreq server to support multiple ioreq pages

 xen/arch/x86/hvm/ioreq.c |  65 +++++++++++++++---
 xen/common/ioreq.c       | 141 +++++++++++++++++++++++++++------------
 xen/include/xen/ioreq.h  |   7 +-
 3 files changed, 158 insertions(+), 55 deletions(-)

-- 
2.51.0



--
Julian Vetter | Vates Hypervisor & Kernel Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech