From: Borislav Petkov <bp@alien8.de>
To: Yunfeng Ye <yeyunfeng@huawei.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, luto@kernel.org, riel@surriel.com,
dave.hansen@intel.com, longman@redhat.com, mtosatti@redhat.com,
linux-kernel@vger.kernel.org,
"hushiyuan@huawei.com" <hushiyuan@huawei.com>,
"linfeilong@huawei.com" <linfeilong@huawei.com>
Subject: Re: [PATCH] x86/process: remove unused variable in __switch_to_xtra()
Date: Tue, 17 Dec 2019 13:29:22 +0100 [thread overview]
Message-ID: <20191217122922.GD28788@zn.tnic> (raw)
In-Reply-To: <0efac42a-1631-d93d-d8a2-e6cf65cdf16b@huawei.com>
On Tue, Dec 17, 2019 at 08:09:08PM +0800, Yunfeng Ye wrote:
> After the commit ecc7e37d4dad ("x86/io: Speedup schedule out of I/O
> bitmap user") and commit 22fe5b0439dd ("x86/ioperm: Move TSS bitmap
> update to exit to user work"), warning is found:
>
> arch/x86/kernel/process.c: In function ‘__switch_to_xtra’:
> arch/x86/kernel/process.c:618:31: warning: variable ‘next’ set but not
> used [-Wunused-but-set-variable]
> struct thread_struct *prev, *next;
> ^~~~
> arch/x86/kernel/process.c:618:24: warning: variable ‘prev’ set but not
> used [-Wunused-but-set-variable]
> struct thread_struct *prev, *next;
> ^~~~
> Fix this by removing the unused variable @prev and @next;
>
> Signed-off-by: Yunfeng Ye <yeyunfeng@huawei.com>
> ---
> arch/x86/kernel/process.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c
> index 61e93a318983..839b5244e3b7 100644
> --- a/arch/x86/kernel/process.c
> +++ b/arch/x86/kernel/process.c
> @@ -615,12 +615,8 @@ void speculation_ctrl_update_current(void)
>
> void __switch_to_xtra(struct task_struct *prev_p, struct task_struct *next_p)
> {
> - struct thread_struct *prev, *next;
> unsigned long tifp, tifn;
>
> - prev = &prev_p->thread;
> - next = &next_p->thread;
> -
> tifn = READ_ONCE(task_thread_info(next_p)->flags);
> tifp = READ_ONCE(task_thread_info(prev_p)->flags);
>
> --
Let me introduce you to your colleague yu kuai:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/cleanups&id=27353d5785bca61bb49cfd7c78e14f1d21e66ec5
:-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2019-12-17 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 12:09 Yunfeng Ye
2019-12-17 12:29 ` Borislav Petkov [this message]
2019-12-17 12:30 ` Yunfeng Ye
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=20191217122922.GD28788@zn.tnic \
--to=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=hushiyuan@huawei.com \
--cc=linfeilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=riel@surriel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yeyunfeng@huawei.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®