From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Andy Lutomirski <luto@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Stas Sergeev <stsp@list.ru>, X86 ML <x86@kernel.org>,
Pavel Emelyanov <xemul@parallels.com>,
kvm list <kvm@vger.kernel.org>
Subject: Re: [RFC/PATCH 3/3] x86/signal/64: Add explicit controls for sigcontext SS handling
Date: Sat, 15 Aug 2015 00:05:02 +0300 [thread overview]
Message-ID: <20150814210502.GE2129@uranus> (raw)
In-Reply-To: <CALCETrWF3EgrQU_6eudj2iNitgSFAOOdZPEcBEtP+DuossMyOQ@mail.gmail.com>
On Fri, Aug 14, 2015 at 01:57:42PM -0700, Andy Lutomirski wrote:
>
> Don't bother testing yet. I'm waffling between trying something like
> this and adding SA_SAVE_SS. I have partially written patches for the
> latter.
ok, ping me if anything
prev parent reply other threads:[~2015-08-14 21:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 20:18 [RFC/PATCH 0/3] x86/signal/64: A better attempt at SS cleanup Andy Lutomirski
2015-08-13 20:18 ` [RFC/PATCH 1/3] x86/kvm: Rename VMX's segment access rights defines Andy Lutomirski
2015-08-14 22:47 ` Paolo Bonzini
2015-08-13 20:18 ` [RFC/PATCH 2/3] x86/signal/64: Try to preserve hardware SS across 64-bit signal delivery Andy Lutomirski
2015-08-13 20:25 ` Andy Lutomirski
2015-08-13 21:26 ` Andy Lutomirski
2015-08-13 21:41 ` Linus Torvalds
2015-08-13 21:49 ` Andy Lutomirski
2015-08-13 22:03 ` Andy Lutomirski
2015-08-13 20:18 ` [RFC/PATCH 3/3] x86/signal/64: Add explicit controls for sigcontext SS handling Andy Lutomirski
2015-08-14 20:55 ` Cyrill Gorcunov
2015-08-14 20:57 ` Andy Lutomirski
2015-08-14 21:05 ` Cyrill Gorcunov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150814210502.GE2129@uranus \
--to=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=stsp@list.ru \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=xemul@parallels.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).