> From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Wednesday, February 08, 2017 9:37 PM > > >>> On 07.02.17 at 18:35, <roger....@citrix.com> wrote: > > Current __hvm_copy assumes that the destination memory belongs to the > > current > > vcpu, but this is not always the case since for PVHv2 Dom0 build hvm copy > > functions are used with current being the idle vcpu. Add a new vcpu > > parameter > > to hvm copy in order to solve that. Note that only hvm_copy_to_guest_phys is > > changed to take a vcpu parameter, because that's the only one at the moment > > that's required in order to build a PVHv2 Dom0. > > > > While there, also assert that the passed vcpu belongs to a HVM guest. > > > > Signed-off-by: Roger Pau Monné <roger....@citrix.com> > > Various Cc-s missing here, btw. > > Jan >
Reviewed-by: Kevin Tian <kevin.t...@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
