public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Borisov <nik.borisov@suse.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: stable@vger.kernel.org, "H. Peter Anvin (Intel)" <hpa@zytor.com>
Subject: Re: [PATCH v2 1/7] x86/asm: Add _ASM_RIP() macro for x86-64 (%rip) suffix
Date: Tue, 12 Mar 2024 07:57:19 +0200	[thread overview]
Message-ID: <9055ecec-e5d5-4f12-928e-7c58d5a25de1@suse.com> (raw)
In-Reply-To: <20240312013317.7k6vlhs6iqgxbbru@desk>



On 12.03.24 г. 3:33 ч., Pawan Gupta wrote:
> On Mon, Feb 26, 2024 at 02:22:31PM +0200, Nikolay Borisov wrote:
>> From: "H. Peter Anvin (Intel)" <hpa@zytor.com>
>>
>> [ Upstream commit 0576d1ed1e153bf34b54097e0561ede382ba88b0 ]
> 
> Looks like the correct sha is f87bc8dc7a7c438c70f97b4e51c76a183313272e

Indeed, 0576d1ed1e153bf34b54097e0561ede382ba88b0 is my local shaid of 
the backported commit. Thanks for catching it!

> 
>> Add a macro _ASM_RIP() to add a (%rip) suffix on 64 bits only. This is
>> useful for immediate memory references where one doesn't want gcc
>> to possibly use a register indirection as it may in the case of an "m"
>> constraint.
>>
>> Signed-off-by: H. Peter Anvin (Intel) <hpa@zytor.com>
>> Signed-off-by: Borislav Petkov <bp@suse.de>
>> Link: https://lkml.kernel.org/r/20210910195910.2542662-3-hpa@zytor.com
>> Signed-off-by: Nikolay Borisov <nik.borisov@suse.com>

  reply	other threads:[~2024-03-12  5:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 12:22 [PATCH v2 0/7] 5.4 backport of recent mds improvement patches Nikolay Borisov
2024-02-26 12:22 ` [PATCH v2 1/7] x86/asm: Add _ASM_RIP() macro for x86-64 (%rip) suffix Nikolay Borisov
2024-03-12  1:33   ` Pawan Gupta
2024-03-12  5:57     ` Nikolay Borisov [this message]
2024-03-29 12:46       ` Greg KH
2024-02-26 12:22 ` [PATCH v2 2/7] x86/bugs: Add asm helpers for executing VERW Nikolay Borisov
2024-02-26 12:22 ` [PATCH v2 3/7] x86/entry_64: Add VERW just before userspace transition Nikolay Borisov
2024-02-26 12:22 ` [PATCH v2 4/7] x86/entry_32: " Nikolay Borisov
2024-02-26 12:22 ` [PATCH v2 5/7] x86/bugs: Use ALTERNATIVE() instead of mds_user_clear static key Nikolay Borisov
2024-02-26 12:22 ` [PATCH v2 6/7] KVM/VMX: Use BT+JNC, i.e. EFLAGS.CF to select VMRESUME vs. VMLAUNCH Nikolay Borisov
2024-02-26 12:22 ` [PATCH v2 7/7] KVM/VMX: Move VERW closer to VMentry for MDS mitigation Nikolay Borisov
2024-02-26 13:30 ` [PATCH v2 0/7] 5.4 backport of recent mds improvement patches Greg KH

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=9055ecec-e5d5-4f12-928e-7c58d5a25de1@suse.com \
    --to=nik.borisov@suse.com \
    --cc=hpa@zytor.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=stable@vger.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