On Mon, Oct 12, 2015 at 06:04:07PM -0700, Andy Lutomirski wrote: ... > > For the benefit of new 64-bit software that uses segmentation (new > versions of DOSEMU might), the new behavior can be detected with a > new ucontext flag UC_SIGCONTEXT_SS. > > To avoid compilation issues, __pad0 is left as an alias for ss in > ucontext. > > The nitty-gritty details are documented in the header file. > > Cc: Stas Sergeev <[email protected]> > Cc: Linus Torvalds <[email protected]> > Cc: Cyrill Gorcunov <[email protected]> > Cc: Pavel Emelyanov <[email protected]> > Signed-off-by: Andy Lutomirski <[email protected]>
Andy, so for old criu versions (prior the 1.5.1 which is Mar 2015, in next versions we already write proper ss into the images) we've been providing __pad = 0, which is ss in a new meaning, and the kernel will overwrite it with @user-ds after this series, correct? This should work for us. Stas, mind to refresh my memory, which ss value doesmu setups here? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
