>>> On 03.04.18 at 17:54, wrote:
> Commit 0d31d16 (x86/setup: do not relocate Xen over current Xen image
> placement) disallowed src/dst images overlaps when relocating Xen image.
> Though it deliberately allowed destination region between __image_base__
> and (__image_base__ + XEN_IMG_OFFSET) ove
On Wed, Apr 11, 2018 at 02:58:01AM -0600, Jan Beulich wrote:
> >>> On 11.04.18 at 10:54, wrote:
> > On Tue, Apr 03, 2018 at 05:54:14PM +0200, Daniel Kiper wrote:
> >> Commit 0d31d16 (x86/setup: do not relocate Xen over current Xen image
> >> placement) disallowed src/dst images overlaps when reloc
On Tue, Apr 03, 2018 at 05:54:14PM +0200, Daniel Kiper wrote:
> Commit 0d31d16 (x86/setup: do not relocate Xen over current Xen image
> placement) disallowed src/dst images overlaps when relocating Xen image.
> Though it deliberately allowed destination region between __image_base__
> and (__image_
>>> On 11.04.18 at 10:54, wrote:
> On Tue, Apr 03, 2018 at 05:54:14PM +0200, Daniel Kiper wrote:
>> Commit 0d31d16 (x86/setup: do not relocate Xen over current Xen image
>> placement) disallowed src/dst images overlaps when relocating Xen image.
>> Though it deliberately allowed destination region
Commit 0d31d16 (x86/setup: do not relocate Xen over current Xen image
placement) disallowed src/dst images overlaps when relocating Xen image.
Though it deliberately allowed destination region between __image_base__
and (__image_base__ + XEN_IMG_OFFSET) overlaps with the end of source
image. And he
