From: "H. Peter Anvin" <hpa@zytor.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Use wrmsrl in kprobes.c, step.c
Date: Thu, 10 Jan 2008 11:49:02 -0800 [thread overview]
Message-ID: <478676AE.9000101@zytor.com> (raw)
In-Reply-To: <1199994043.19760.31.camel@brick>
Harvey Harrison wrote:
> Where x86_32 passed zero in the high 32 bits, use wrmsrl which
> will zero extend for us. This allows ifdefs for 32/64 bit to
> be eliminated.
>
> Eliminate ifdef in step.c. Similar cleanup was done when unifying
> kprobes_32|64.c and wrmsr() was chosen there over wrmsrl(). This
> patch changes these to wrmsrl.
>
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> ---
> arch/x86/kernel/kprobes.c | 4 ++--
> arch/x86/kernel/step.c | 4 ----
> 2 files changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/arch/x86/kernel/kprobes.c b/arch/x86/kernel/kprobes.c
> index 53ba6a5..34becd1 100644
> --- a/arch/x86/kernel/kprobes.c
> +++ b/arch/x86/kernel/kprobes.c
> @@ -410,13 +410,13 @@ static void __kprobes set_current_kprobe(struct kprobe *p, struct pt_regs *regs,
> static void __kprobes clear_btf(void)
> {
> if (test_thread_flag(TIF_DEBUGCTLMSR))
> - wrmsr(MSR_IA32_DEBUGCTLMSR, 0, 0);
> + wrmsrl(MSR_IA32_DEBUGCTLMSR, 0L);
> }
Drop the L. It doesn't buy you anything, and gcc will sign-extend for
you anyway. It's just visual clutter.
-hpa
next prev parent reply other threads:[~2008-01-10 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 7:18 [PATCH] x86: Remove ifdef from step.c Harvey Harrison
2008-01-10 12:40 ` Ingo Molnar
2008-01-10 19:29 ` Harvey Harrison
2008-01-10 19:40 ` [PATCH] x86: Use wrmsrl in kprobes.c, step.c Harvey Harrison
2008-01-10 19:49 ` H. Peter Anvin [this message]
2008-01-10 20:15 ` [PATCHv2] " Harvey Harrison
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=478676AE.9000101@zytor.com \
--to=hpa@zytor.com \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.