On 11/03/13 20:45, Daniel Kiper wrote: > On Mon, Mar 11, 2013 at 02:27:26PM +0000, Andrew Cooper wrote: >> On 11/03/13 14:13, Daniel Kiper wrote: >>> On Mon, Mar 11, 2013 at 01:43:02PM +0000, David Vrabel wrote: >>>> On 11/03/13 13:30, Daniel Kiper wrote: >>>>> On Mon, Mar 11, 2013 at 01:21:30PM +0000, David Vrabel wrote: >>>>>> On 11/03/13 11:17, Daniel Kiper wrote: >>>>>>> Heh... It looks that there is a misunderstanding. At first I thought >>>>>>> that David was going to replace purgatory functionality by switching >>>>>>> from 64-bit to 32-bit in kexec_reloc. But later I realized that >>>>>>> I missed Xen 64-bit/dom 32-bit case. Now I agree that this switch >>>>>>> must stay as is. However, now I think that there is another >>>>>>> small mistake which should be fixed. Please look above. >>>>>> Which mistake? I'm not sure what you're referring to. >>>>> I thought about that: >>>>> >>>>> if ( image->arch == EM_386 ) >>>>> reloc_flags |= KEXEC_RELOC_FLAG_COMPAT; >>>>> >>>>> It should be change to: >>>>> >>>>> if ( is_pv_32on64_domain(dom0) ) >>>>> reloc_flags |= KEXEC_RELOC_FLAG_COMPAT; >>>> This isn't a mistake but a deliberate improvement to the old interface. >>> I am still not convinced. >>> >>>> It is clearer and more useful for this sub-architecture to be explicitly >>>> supplied in the kexec_load call than implicitly through some other >>>> side-channel. >>> First of all you do not need to pass any info about architecure to >>> new kernel or something like that (please check my previous emails). >> Yes - you really do. Guessing the architecture of a blob of code is >> insane, and any current interface which relies on this guessing is >> broken by design. > Which interface do you mean? Old Xen? kexec-tools? purgatory? > > Why do you need to enforce architecture? purgatory starts new kernel > image like BIOS does it. What is wrong with that? Do you set something > in BIOS to differentiate between 32-bit and 64-bit system? Fine, but that is irrelevant. Purgatory can do whatever it wants as soon as it is running. What Xen cares about is entering into the binary blob in the correct operating mode. This binary blob will usually be purgatory but can be any executable image loaded using the new interface. If that image claims to be a 32bit image, Xen will enter it in 32bit mode. If it claims to be 64bit, Xen will enter it in 64bit mode. If it is being stupid and claiming to be 32bit when it is in fact 64bit (or vice versa) then it has only itself to blame. What is absolutely unacceptable (which is the case in the current interface) is for Xen to assume that the entry point for the blob is the same operating mode as dom0. Just because "this happens to be the case when using kexec-tools at the moment" is no reason nor excuse to functionally break the interface. ~Andrew
