Heiko Carstens <[EMAIL PROTECTED]> writes: >> >> >> Set KEXEC_ARCH_S390 in order to make sure that kexec works also in > compat >> >> >> mode on s390. >> >> > >> >> > That seems fine to me, but could you explain a little more about it? >> >> >> >> If you call sys_kexec_load in compat mode, you are required to pass >> >> the architecture your kernel is actually running. The kexec kernel >> >> code only supports one switching to one mode. So a 32bit user space >> >> must be prepared to accept a 64bit handoff. The flag reports >> >> that you can do that. >> > >> > Thanks. >> > >> > I have applied this patch to kexec-tools-testing >> >> I'm actually confused a little on this patch. Because usually >> a flag like that to be useful requires things be conditional. >> One flag for a 32bit kernel and a different flag for a 64bit kernel. >> >> Does S390 not support a 32bit kernel? > > S390 supports both. The binary interface for 32bit and 64bit kernel > images is identical, hence I don't see a need to make anything conditional. > Whatever the user wants: it should work.
What is the binary interface? Could you describe what that binary interface is or give me a pointer? Does the s390 not distinguish between 32bit and 64bit code? Eric _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
