mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jinjie Ruan <ruanjinjie@huawei.com>
To: "H. Peter Anvin" <hpa@zytor.com>, <tglx@linutronix.de>,
	<mingo@redhat.com>, <bp@alien8.de>, <dave.hansen@linux.intel.com>,
	<xin3.li@intel.com>, <krisman@collabora.com>, <x86@kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Remove unused _TIF_SINGLESTEP
Date: Wed, 30 Oct 2024 09:46:24 +0800	[thread overview]
Message-ID: <986c6fc8-b88c-347c-f599-283b34cf34b8@huawei.com> (raw)
In-Reply-To: <D75E52D0-2C84-410A-BF59-4E0CDFF67237@zytor.com>



On 2024/10/30 9:44, H. Peter Anvin wrote:
> On October 29, 2024 6:24:38 PM PDT, Jinjie Ruan <ruanjinjie@huawei.com> wrote:
>> Since following commit, _TIF_SINGLESTEP is not used by x86 anymore,
>> remove it.
>>
>> Fixes: 6342adcaa683 ("entry: Ensure trap after single-step on system call return")

This commit, sorry, the message is not so clear.

>> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
>> ---
>> arch/x86/include/asm/thread_info.h | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/arch/x86/include/asm/thread_info.h b/arch/x86/include/asm/thread_info.h
>> index 12da7dfd5ef1..734db7221613 100644
>> --- a/arch/x86/include/asm/thread_info.h
>> +++ b/arch/x86/include/asm/thread_info.h
>> @@ -110,7 +110,6 @@ struct thread_info {
>> #define _TIF_NOTIFY_RESUME	(1 << TIF_NOTIFY_RESUME)
>> #define _TIF_SIGPENDING		(1 << TIF_SIGPENDING)
>> #define _TIF_NEED_RESCHED	(1 << TIF_NEED_RESCHED)
>> -#define _TIF_SINGLESTEP		(1 << TIF_SINGLESTEP)
>> #define _TIF_SSBD		(1 << TIF_SSBD)
>> #define _TIF_SPEC_IB		(1 << TIF_SPEC_IB)
>> #define _TIF_SPEC_L1D_FLUSH	(1 << TIF_SPEC_L1D_FLUSH)
> 
> "Following commit"?
> 

  reply	other threads:[~2024-10-30  1:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30  1:24 Jinjie Ruan
2024-10-30  1:44 ` H. Peter Anvin
2024-10-30  1:46   ` Jinjie Ruan [this message]
2025-03-03 12:33 ` Ingo Molnar

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=986c6fc8-b88c-347c-f599-283b34cf34b8@huawei.com \
    --to=ruanjinjie@huawei.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=krisman@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xin3.li@intel.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

all inboxes | Powered by JetHome®