> -----Original Message----- > From: Oleksandr Tyshchenko <olekst...@gmail.com> > Sent: 12 January 2021 21:52 > To: xen-devel@lists.xenproject.org > Cc: Oleksandr Tyshchenko <oleksandr_tyshche...@epam.com>; Andrew Cooper > <andrew.coop...@citrix.com>; > George Dunlap <george.dun...@citrix.com>; Ian Jackson <i...@xenproject.org>; > Jan Beulich > <jbeul...@suse.com>; Julien Grall <jul...@xen.org>; Stefano Stabellini > <sstabell...@kernel.org>; Wei > Liu <w...@xen.org>; Roger Pau Monné <roger....@citrix.com>; Paul Durrant > <p...@xen.org>; Jun Nakajima > <jun.nakaj...@intel.com>; Kevin Tian <kevin.t...@intel.com>; Tim Deegan > <t...@xen.org>; Julien Grall > <julien.gr...@arm.com> > Subject: [PATCH V4 04/24] xen/ioreq: Make x86's IOREQ feature common > > From: Oleksandr Tyshchenko <oleksandr_tyshche...@epam.com> > > As a lot of x86 code can be re-used on Arm later on, this patch > moves previously prepared IOREQ support to the common code > (the code movement is verbatim copy). > > The "legacy" mechanism of mapping magic pages for the IOREQ servers > remains x86 specific and not exposed to the common code. > > The common IOREQ feature is supposed to be built with IOREQ_SERVER > option enabled, which is selected for x86's config HVM for now. > > In order to avoid having a gigantic patch here, the subsequent > patches will update remaining bits in the common code step by step: > - Make IOREQ related structs/materials common > - Drop the "hvm" prefixes and infixes > - Remove layering violation by moving corresponding fields > out of *arch.hvm* or abstracting away accesses to them > > Also include <xen/domain_page.h> which will be needed on Arm > to avoid touch the common code again when introducing Arm specific bits. > > This support is going to be used on Arm to be able run device > emulator outside of Xen hypervisor. > > Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshche...@epam.com>
Reviewed-by: Paul Durrant <p...@xen.org>
