From: Reinette Chatre <reinette.chatre@intel.com>
To: Uros Bizjak <ubizjak@gmail.com>,
linux-kernel@vger.kernel.org, x86@kernel.org, acme@kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH] x86/resctrl: Use _ASM_BX to avoid #ifdef CONFIG_X86_64
Date: Mon, 10 Jun 2019 10:31:31 -0700 [thread overview]
Message-ID: <14baa8db-1989-4d9b-d6fb-ada9a9f1137b@intel.com> (raw)
In-Reply-To: <20190606200044.5730-1-ubizjak@gmail.com>
Hi Uros,
On 6/6/2019 1:00 PM, Uros Bizjak wrote:
> Depending on CONFIG_X86_64 _ASM_BX expands to either rbx or ebx.
>
> Cc: Fenghua Yu <fenghua.yu@intel.com>
> Cc: Reinette Chatre <reinette.chatre@intel.com>
> Cc: x86@kernel.org
> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> ---
> arch/x86/kernel/cpu/resctrl/pseudo_lock.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/resctrl/pseudo_lock.c b/arch/x86/kernel/cpu/resctrl/pseudo_lock.c
> index 604c0e3bcc83..09408794eab2 100644
> --- a/arch/x86/kernel/cpu/resctrl/pseudo_lock.c
> +++ b/arch/x86/kernel/cpu/resctrl/pseudo_lock.c
> @@ -431,11 +431,7 @@ static int pseudo_lock_fn(void *_rdtgrp)
> #else
> register unsigned int line_size asm("esi");
> register unsigned int size asm("edi");
> -#ifdef CONFIG_X86_64
> - register void *mem_r asm("rbx");
> -#else
> - register void *mem_r asm("ebx");
> -#endif /* CONFIG_X86_64 */
> + register void *mem_r asm(_ASM_BX);
> #endif /* CONFIG_KASAN */
>
> /*
>
Thank you very much for catching this. I was not aware of this macro.
Acked-by: Reinette Chatre <reinette.chatre@intel.com>
Reinette
next prev parent reply other threads:[~2019-06-10 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 20:00 Uros Bizjak
2019-06-10 17:31 ` Reinette Chatre [this message]
2019-06-10 20:52 ` [tip:x86/cache] x86/resctrl: Use _ASM_BX to avoid ifdeffery tip-bot for Uros Bizjak
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=14baa8db-1989-4d9b-d6fb-ada9a9f1137b@intel.com \
--to=reinette.chatre@intel.com \
--cc=acme@kernel.org \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=ubizjak@gmail.com \
--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
all inboxes | Powered by JetHome®