From: "H. Peter Anvin" <hpa@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
stable@kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Avi Kivity <avi@redhat.com>, Brian Gerst <brgerst@gmail.com>,
Glauber Costa <glommer@redhat.com>, Greg KH <gregkh@suse.de>,
Ingo Molnar <mingo@elte.hu>, Jeff Dike <jdike@addtoit.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Peter Palfrader <peter@palfrader.org>,
Thomas Gleixner <tglx@linutronix.de>,
Zachary Amsden <zamsden@redhat.com>
Subject: Re: [GIT PULL] x86/asm for 2.6.36
Date: Fri, 06 Aug 2010 11:03:38 -0700 [thread overview]
Message-ID: <4C5C4E7A.8040603@kernel.org> (raw)
In-Reply-To: <4C5C4A23.6070006@zytor.com>
On 08/06/2010 10:45 AM, H. Peter Anvin wrote:
>
> It's worth noting that in this particular case the code itself looks
> like this:
>
> set_64bit((unsigned long *)&irte->low, irte_modified->low);
> set_64bit((unsigned long *)&irte->high, irte_modified->high);
>
> ... where the existing cast is there because irte->low and irte->high
> are types __u64. In other words, with the "more logical" u64 prototype
> the casts should just get removed.
>
Looking through the build I'm currently running, so far, it is smoking
out a bunch of unnecessary casts and wrappers, for example, in kvm/mmu.c:
static void __set_spte(u64 *sptep, u64 spte)
{
#ifdef CONFIG_X86_64
set_64bit((unsigned long *)sptep, spte);
#else
set_64bit((unsigned long long *)sptep, spte);
#endif
}
... which just becomes the much cleaner ...
static void __set_spte(u64 *sptep, u64 spte)
{
set_64bit(sptep, spte);
}
I'll go through all these as this build finishes and give you an updated
tree to pull, ok?
-hpa
prev parent reply other threads:[~2010-08-06 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 20:37 [GIT PULL] x86/asm for 2.6.36 H. Peter Anvin
2010-08-06 17:17 ` Linus Torvalds
2010-08-06 17:45 ` H. Peter Anvin
2010-08-06 17:56 ` Linus Torvalds
2010-08-06 18:03 ` H. Peter Anvin [this message]
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=4C5C4E7A.8040603@kernel.org \
--to=hpa@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=avi@redhat.com \
--cc=brgerst@gmail.com \
--cc=glommer@redhat.com \
--cc=gregkh@suse.de \
--cc=hpa@linux.intel.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=penberg@cs.helsinki.fi \
--cc=peter@palfrader.org \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=zamsden@redhat.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