From: Rusty Russell <rusty@rustcorp.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-rt-users@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [patch] paravirt: disable Kbuild option for now
Date: Tue, 09 Jan 2007 23:05:26 +1100 [thread overview]
Message-ID: <1168344326.19646.124.camel@localhost.localdomain> (raw)
In-Reply-To: <20070109084520.GA444@elte.hu>
On Tue, 2007-01-09 at 09:45 +0100, Ingo Molnar wrote:
> * Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
> > In include/linux/irqflags.h safe_halt changed from a macro to a static
> > inline function which results in tons of warnings for architectures
> > other than x86[-64]:
> >
> > include/linux/irqflags.h:99: warning: implicit declaration of function
> > 'raw_safe_halt'
>
> ok, this is still not fixed in rt2 - which is using Rusty's
> paravirt-unexport patch.
>
> Andrew, we need to fix this before v2.6.20 is released. Simplest
> upstream fix is to just disable the CONFIG_PARAVIRT Kbuild option, as
> per the patch below. Rusty's unexport patch is promising in many ways,
> but it's v2.6.21 stuff IMO.
No. Just drop the whole "don't export paravirt_ops" idea, and we'll
work on that for 2.6.21.
I don't see a problem with exporting paravirt_ops, I was just trying to
keep you happy. I'm happy to remove the export in 2.6.21, but as we've
seen it's non-trivial to ensure all configs still work.
Rusty.
next prev parent reply other threads:[~2007-01-09 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 16:30 2.6.20-rc4-rt0: i386 assembler in kernel/sys.c Sascha Hauer
2007-01-09 8:45 ` [patch] paravirt: disable Kbuild option for now Ingo Molnar
2007-01-09 12:05 ` Rusty Russell [this message]
2007-01-09 12:11 ` Ingo Molnar
2007-01-09 12:39 ` Rusty Russell
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=1168344326.19646.124.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=s.hauer@pengutronix.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.