Re: [Xen-devel] [PATCH] x86/setup: do not relocate below the end of current Xen image placement

2017-11-28 Thread Jan Beulich
>>> On 28.11.17 at 13:41, wrote: > On Mon, Nov 27, 2017 at 09:51:56AM -0700, Jan Beulich wrote: >> >>> On 27.11.17 at 16:41, wrote: >> > If it is possible we would like to have the Xen image higher than the >> > booloader put it and certainly do

Re: [Xen-devel] [PATCH] x86/setup: do not relocate below the end of current Xen image placement

2017-11-28 Thread Daniel Kiper
On Tue, Nov 28, 2017 at 07:02:01AM -0700, Jan Beulich wrote: > >>> On 28.11.17 at 14:53, wrote: > > On Tue, Nov 28, 2017 at 06:37:17AM -0700, Jan Beulich wrote: > >> >>> On 28.11.17 at 13:47, wrote: > >> > Then all cases should be covered. > >> >

Re: [Xen-devel] [PATCH] x86/setup: do not relocate below the end of current Xen image placement

2017-11-28 Thread Jan Beulich
>>> On 28.11.17 at 14:53, wrote: > On Tue, Nov 28, 2017 at 06:37:17AM -0700, Jan Beulich wrote: >> >>> On 28.11.17 at 13:47, wrote: >> > Then all cases should be covered. >> >> I don't think that's going to be enough: Once Xen gets moved, >> the

Re: [Xen-devel] [PATCH] x86/setup: do not relocate below the end of current Xen image placement

2017-11-28 Thread Daniel Kiper
On Tue, Nov 28, 2017 at 06:37:17AM -0700, Jan Beulich wrote: > >>> On 28.11.17 at 13:47, wrote: > > On Tue, Nov 28, 2017 at 04:51:51AM -0700, Jan Beulich wrote: > >> >>> On 28.11.17 at 12:32, wrote: > >> > I have a feeling that you can trigger

Re: [Xen-devel] [PATCH] x86/setup: do not relocate below the end of current Xen image placement

2017-11-28 Thread Daniel Kiper
On Mon, Nov 27, 2017 at 09:51:56AM -0700, Jan Beulich wrote: > >>> On 27.11.17 at 16:41, wrote: > > If it is possible we would like to have the Xen image higher than the > > booloader put it and certainly do not overwrite the Xen code and data > > during copy/relocation.

Re: [Xen-devel] [PATCH] x86/setup: do not relocate below the end of current Xen image placement

2017-11-28 Thread Daniel Kiper
On Mon, Nov 27, 2017 at 04:58:52PM +, Andrew Cooper wrote: > On 27/11/17 15:41, Daniel Kiper wrote: > > If it is possible we would like to have the Xen image higher than the > > booloader put it and certainly do not overwrite the Xen code and data > > during copy/relocation. Otherwise the Xen

Re: [Xen-devel] [PATCH] x86/setup: do not relocate below the end of current Xen image placement

2017-11-27 Thread Jan Beulich
>>> On 27.11.17 at 17:58, wrote: > On 27/11/17 15:41, Daniel Kiper wrote: >> If it is possible we would like to have the Xen image higher than the >> booloader put it and certainly do not overwrite the Xen code and data >> during copy/relocation. Otherwise the Xen may

Re: [Xen-devel] [PATCH] x86/setup: do not relocate below the end of current Xen image placement

2017-11-27 Thread Konrad Rzeszutek Wilk
On Mon, Nov 27, 2017 at 04:58:52PM +, Andrew Cooper wrote: > On 27/11/17 15:41, Daniel Kiper wrote: > > If it is possible we would like to have the Xen image higher than the > > booloader put it and certainly do not overwrite the Xen code and data > > during copy/relocation. Otherwise the Xen

Re: [Xen-devel] [PATCH] x86/setup: do not relocate below the end of current Xen image placement

2017-11-27 Thread Andrew Cooper
On 27/11/17 15:41, Daniel Kiper wrote: > If it is possible we would like to have the Xen image higher than the > booloader put it and certainly do not overwrite the Xen code and data > during copy/relocation. Otherwise the Xen may crash silently at boot. > > Signed-off-by: Daniel Kiper

Re: [Xen-devel] [PATCH] x86/setup: do not relocate below the end of current Xen image placement

2017-11-27 Thread Jan Beulich
>>> On 27.11.17 at 16:41, wrote: > If it is possible we would like to have the Xen image higher than the > booloader put it and certainly do not overwrite the Xen code and data > during copy/relocation. Otherwise the Xen may crash silently at boot. Is this something that

[Xen-devel] [PATCH] x86/setup: do not relocate below the end of current Xen image placement

2017-11-27 Thread Daniel Kiper
If it is possible we would like to have the Xen image higher than the booloader put it and certainly do not overwrite the Xen code and data during copy/relocation. Otherwise the Xen may crash silently at boot. Signed-off-by: Daniel Kiper --- xen/arch/x86/setup.c |8