linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Andy Lutomirski <luto@kernel.org>
Cc: "Bae, Chang Seok" <chang.seok.bae@intel.com>,
	X86 ML <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Borislav Petkov <bpetkov@suse.de>,
	Brian Gerst <brgerst@gmail.com>, Stas Sergeev <stsp@list.ru>
Subject: Re: FSGSBASE ABI considerations
Date: Mon, 31 Jul 2017 13:55:40 +0300	[thread overview]
Message-ID: <20170731105540.tovjhththy2u2dtb@node.shutemov.name> (raw)
In-Reply-To: <CALCETrVSm9tLiHKf-BKaYknEfko1bd_2i+4U7cqELG5iiFDygg@mail.gmail.com>

On Sun, Jul 30, 2017 at 08:05:43PM -0700, Andy Lutomirski wrote:
> Hi all-
> 
> Chang wants to get the FSGSBASE patches in.  Here's a bit on a brain
> dump on what I think the relevant considerations are and why I haven't
> sent out my patches.

I'm not sure if it would be relevant input for the descussion, but there's
another issue with FSGSBASE vs LA57:

http://lkml.kernel.org/r/9ddf602b-6c8b-8c1e-ab46-07ed12366593@redhat.com

-- 
 Kirill A. Shutemov

  parent reply	other threads:[~2017-07-31 10:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31  3:05 FSGSBASE ABI considerations Andy Lutomirski
2017-07-31  4:38 ` Linus Torvalds
2017-07-31 14:14   ` Andy Lutomirski
2017-07-31 10:55 ` Kirill A. Shutemov [this message]
2017-07-31 14:16   ` Andy Lutomirski
2017-07-31 21:23 ` Bae, Chang Seok
2017-08-07 16:14   ` Andy Lutomirski
2017-08-07  8:06 ` Stas Sergeev
2017-08-07 16:20   ` Andy Lutomirski
2017-08-07 16:49     ` Christopher Lameter
2017-08-07 17:35     ` Linus Torvalds
2017-08-07 19:07       ` Andy Lutomirski
2017-08-07 21:32     ` Stas Sergeev

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=20170731105540.tovjhththy2u2dtb@node.shutemov.name \
    --to=kirill@shutemov.name \
    --cc=bpetkov@suse.de \
    --cc=brgerst@gmail.com \
    --cc=chang.seok.bae@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=stsp@list.ru \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /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).