From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Andreas Schwab <schwab@linux-m68k.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mike Galbraith <efault@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] scheduler changes for v3.3
Date: Sat, 7 Jan 2012 19:43:48 +0100 [thread overview]
Message-ID: <20120107194348.77b42573@de.ibm.com> (raw)
In-Reply-To: <CA+55aFwNzNSd2B57XYLC5r9sg=+GD=dP-UPZQDxmLXyLODS6+w@mail.gmail.com>
On Fri, 6 Jan 2012 08:58:55 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Thu, Jan 5, 2012 at 6:08 AM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > Please pull the latest sched-core-for-linus git tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-core-for-linus
>
> Ugh. So I got conflicts on this one. Big deal, fix them up.
>
> But as I was fixing them up, I hit two problems that I wanted people
> to take a look at:
>
> - some of the code was utter crap. Look at my fixup for
> include/asm-generic/cputime.h, for example. Notice how I had to change
> __msecs to __usec, and notice the bogus semicolons that I removed?
Yes, the semicolons had been crap and the parameter name suboptimal.
> This came in through commit 648616343cdb ("[S390] cputime: add
> sparse checking and cleanup") which is also mis-named: it's not
> S390-specific. Martin, please take a look.
Yeah, I had that patch in the s390 tree before it got moved to a tip tree.
I tend to tag everything in my tree with [S390].
> - I did not do the right thing for the "usecs_to_cputime64()" fixup.
> Please take a look at commit 34845636a184 ("procfs: do not confuse
> jiffies with cputime64_t") which introduced that "usecs_to_cputime64()
> thing, and which clashes badly with the sparse cleanups.
There had been some fallout from the two changes.
> And by "clashes badly", I mean it. The sparse cleanups added a lot of
> casts between the types, which means that the mindless
>
> +#define usecs_to_cputime64(us) usecs_to_cputime(us)
>
> introduced by that commit 34845636a184 is now likely *wrong*, because
> "usecs_to_cputime()" now explicitly casts to a non-64-bit cputime_t.
Surprisingly sparse does not give a warning if the base type of two
__nowarn types is the same. All three VIRT_CPU_ACCOUNTING architectures
use u64 or unsigned long long for cputime_t and cputime64_t. It does
work but I agree that an explicit cast to cputime64_t would be better.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2012-01-07 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 14:08 [GIT PULL] scheduler changes for v3.3 Ingo Molnar
2012-01-06 16:58 ` Linus Torvalds
2012-01-06 17:30 ` Frederic Weisbecker
2012-01-06 18:00 ` Linus Torvalds
2012-01-06 17:49 ` Andreas Schwab
2012-01-06 19:17 ` Ingo Molnar
2012-01-07 18:43 ` Martin Schwidefsky [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=20120107194348.77b42573@de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=schwab@linux-m68k.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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