linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bae, Chang Seok" <chang.seok.bae@intel.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Andy Lutomirski <luto@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>, "H . Peter Anvin" <hpa@zytor.com>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"Metzger, Markus T" <markus.t.metzger@intel.com>,
	"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 04/13] x86/fsgsbase/64: Add intrinsics/macros for FSGSBASE instructions
Date: Thu, 17 Jan 2019 18:04:52 +0000	[thread overview]
Message-ID: <0E0B43A0-76AC-440B-A592-F4940C1028CF@intel.com> (raw)
In-Reply-To: <20190117050920.GJ6118@tassilo.jf.intel.com>


> On Jan 16, 2019, at 21:09, Andi Kleen <ak@linux.intel.com> wrote:
> 
>> +#ifdef CONFIG_X86_64
>> +
>> +#include <asm/inst.h>
>> +
>> +.macro RDGSBASE opd
> 
> The caller can now use the assembler instructions directly, so the macros
> are not needed anymore.
> 
> -Andi

Yeah, you’re right, since GAS is included in the binutils.

Thanks

  reply	other threads:[~2019-01-17 18:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 22:48 [PATCH v4 00/13] x86: Enable FSGSBASE instructions Chang S. Bae
2019-01-16 22:48 ` [PATCH v4 01/13] taint: Introduce a new taint flag (insecure) Chang S. Bae
2019-01-16 22:48 ` [PATCH v4 02/13] x86/fsgsbase/64: Add 'unsafe_fsgsbase' to enable CR4.FSGSBASE Chang S. Bae
2019-01-16 22:48 ` [PATCH v4 03/13] kbuild: Raise the minimum required binutils version to 2.21 Chang S. Bae
2019-01-16 22:48 ` [PATCH v4 04/13] x86/fsgsbase/64: Add intrinsics/macros for FSGSBASE instructions Chang S. Bae
2019-01-17  5:09   ` Andi Kleen
2019-01-17 18:04     ` Bae, Chang Seok [this message]
2019-01-16 22:48 ` [PATCH v4 05/13] x86/fsgsbase/64: Enable FSGSBASE instructions in the helper functions Chang S. Bae
2019-01-16 22:48 ` [PATCH v4 06/13] x86/fsgsbase/64: Preserve FS/GS state in __switch_to() if FSGSBASE is on Chang S. Bae
2019-01-16 22:48 ` [PATCH v4 07/13] x86/fsgsbase/64: When copying a thread, use the FSGSBASE instructions if available Chang S. Bae
2019-01-16 22:48 ` [PATCH v4 08/13] x86/fsgsbase/64: Introduce the FIND_PERCPU_BASE macro Chang S. Bae
2019-01-16 22:48 ` [PATCH v4 09/13] x86/fsgsbase/64: Use the per-CPU base as GSBASE at the paranoid_entry Chang S. Bae
2019-01-16 22:48 ` [PATCH v4 10/13] selftests/x86/fsgsbase: Test WRGSBASE Chang S. Bae
2019-01-16 22:48 ` [PATCH v4 11/13] x86/fsgsbase/64: Enable FSGSBASE by default and add a chicken bit Chang S. Bae
2019-01-16 22:48 ` [PATCH v4 12/13] x86/elf: Enumerate kernel FSGSBASE capability in AT_HWCAP2 Chang S. Bae
2019-01-16 22:48 ` [PATCH v4 13/13] x86/fsgsbase/64: Add documentation for FSGSBASE Chang S. Bae

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=0E0B43A0-76AC-440B-A592-F4940C1028CF@intel.com \
    --to=chang.seok.bae@intel.com \
    --cc=ak@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=markus.t.metzger@intel.com \
    --cc=mingo@kernel.org \
    --cc=ravi.v.shankar@intel.com \
    --cc=tglx@linutronix.de \
    /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).