From: "Yinghai Lu" <yinghai@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"KOSAKI Motohiro" <kosaki.motohiro@gmail.com>,
linux-kernel@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Jesse Barnes" <jbarnes@virtuousgeek.org>,
"Kamalesh Babulal" <kamalesh@linux.vnet.ibm.com>
Subject: Re: [git pull] sparseirq / irq updates for v2.6.29
Date: Sun, 28 Dec 2008 16:06:09 -0800 [thread overview]
Message-ID: <86802c440812281606o6e8fbde1ub2e5055f83fea47@mail.gmail.com> (raw)
In-Reply-To: <4958120F.4060804@zytor.com>
On Sun, Dec 28, 2008 at 3:55 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> Ingo Molnar wrote:
>>
>> ok, agreed. I was hoping for some more generic workaround but nothing
>> seemed to keep gcc from inlining such functions.
>>
>
> Other than blacklisting those gcc versions. It's pretty easy to
> understand how a bug like that could creep in, since one of the main
> improvements of the early gcc4 series was better inlining as an
> optimization.
1. one time path add one dummy printk
2. multi path, could move it to another file.
could add one like kernel/weak.c to collect those ...
>
> --
> H. Peter Anvin, Intel Open Source Technology Center
> I work for Intel. I don't speak on their behalf.
good to know.
YH
next prev parent reply other threads:[~2008-12-29 0:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-25 16:07 Ingo Molnar
2008-12-27 13:32 ` Ingo Molnar
2008-12-27 17:27 ` KOSAKI Motohiro
2008-12-27 17:38 ` Ingo Molnar
2008-12-28 23:11 ` Linus Torvalds
2008-12-28 23:23 ` Yinghai Lu
2008-12-28 23:27 ` Ingo Molnar
2008-12-28 23:30 ` Ingo Molnar
2008-12-29 0:01 ` Yinghai Lu
2008-12-29 8:39 ` KOSAKI Motohiro
2008-12-29 11:09 ` Ingo Molnar
2008-12-29 11:20 ` KOSAKI Motohiro
2008-12-29 0:28 ` Yinghai Lu
2008-12-29 0:53 ` Yinghai Lu
2008-12-29 9:44 ` Ingo Molnar
2008-12-29 9:52 ` Ingo Molnar
2008-12-29 11:00 ` Kamalesh Babulal
2008-12-29 11:05 ` Ingo Molnar
2008-12-29 16:05 ` Kamalesh Babulal
2008-12-29 16:20 ` Ingo Molnar
2008-12-29 16:22 ` KOSAKI Motohiro
2008-12-29 16:36 ` Ingo Molnar
2008-12-28 23:55 ` H. Peter Anvin
2008-12-29 0:06 ` Yinghai Lu [this message]
2008-12-29 0:38 ` H. Peter Anvin
2008-12-29 9:34 ` Ingo Molnar
2008-12-28 23:10 ` [git pull] sparseirq / irq fixes Ingo Molnar
2008-12-29 12:52 ` Ingo Molnar
2008-12-31 0:22 ` Linus Torvalds
2008-12-31 6:48 ` Ingo Molnar
2008-12-31 12:00 ` [sparseirq] remove debug printks (io_apic.c) Markus Trippelsdorf
2009-01-02 22:21 ` Ingo Molnar
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=86802c440812281606o6e8fbde1ub2e5055f83fea47@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®