[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151014164021.GS2048@uranus>
Date: Wed, 14 Oct 2015 19:40:21 +0300
From: Cyrill Gorcunov <gorcunov@...il.com>
To: Andy Lutomirski <luto@...nel.org>, Stas Sergeev <stsp@...t.ru>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org,
Brian Gerst <brgerst@...il.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Borislav Petkov <bp@...en8.de>,
Pavel Emelyanov <xemul@...allels.com>
Subject: Re: [RFC 3/4] x86/signal/64: Re-add support for SS in the 64-bit
signal context
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 <stsp@...t.ru>
> Cc: Linus Torvalds <torvalds@...ux-foundation.org>
> Cc: Cyrill Gorcunov <gorcunov@...il.com>
> Cc: Pavel Emelyanov <xemul@...allels.com>
> Signed-off-by: Andy Lutomirski <luto@...nel.org>
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 majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists