From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -rt] 2.6.19-4c6-rt9 build problem
Date: Wed, 29 Nov 2006 15:15:07 -0800 [thread overview]
Message-ID: <20061129231507.GG2335@us.ibm.com> (raw)
In-Reply-To: <20061129224451.GC2335@us.ibm.com>
On Wed, Nov 29, 2006 at 02:44:52PM -0800, Paul E. McKenney wrote:
> On Wed, Nov 29, 2006 at 09:03:07PM +0100, Ingo Molnar wrote:
> >
> > * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> >
> > > Hello!
> > >
> > > Got a compiler error building 1.6.19-rc6-rt9 on NUMA-Q, admittedly
> > > with unusual config. The patch below solves it, though I cannot say
> > > that I am an ACPI expert.
> >
> > thanks, applied. Have you tried to boot the resulting kernel as well?
And with these two changes, it does boot!
Thanx, Paul
> Hit another build error. :-/
>
> The following combined (crude) patch makes the build succeed. Rebooting now,
> with fingers firmly crossed...
>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>
> include/linux/acpi_pmtmr.h | 2 ++
> mm/page_alloc.c | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff -urpNa -X dontdiff linux-2.6.19-rc6-rt9/include/linux/acpi_pmtmr.h linux-2.6.19-rc6-rt9.tscbug/include/linux/acpi_pmtmr.h
> --- linux-2.6.19-rc6-rt9/include/linux/acpi_pmtmr.h 2006-11-28 17:21:55.000000000 -0800
> +++ linux-2.6.19-rc6-rt9.tscbug/include/linux/acpi_pmtmr.h 2006-11-29 08:09:07.000000000 -0800
> @@ -27,6 +27,8 @@ static inline u32 acpi_pm_read_early(voi
>
> #else
>
> +#define pmtmr_ioport 0
> +
> static inline u32 acpi_pm_read_early(void)
> {
> return 0;
> diff -urpNa -X dontdiff linux-2.6.19-rc6-rt9/mm/page_alloc.c linux-2.6.19-rc6-rt9.tscbug/mm/page_alloc.c
> --- linux-2.6.19-rc6-rt9/mm/page_alloc.c 2006-11-28 17:21:56.000000000 -0800
> +++ linux-2.6.19-rc6-rt9.tscbug/mm/page_alloc.c 2006-11-29 14:14:09.000000000 -0800
> @@ -2790,7 +2790,9 @@ static int page_alloc_cpu_notify(struct
> __lock_cpu_pcp(&flags, cpu);
> WARN_ON_ONCE(cpu == raw_smp_processor_id());
>
> +#ifdef CONFIG_PM
> __drain_pages(cpu);
> +#endif /* #ifdef CONFIG_PM */
> vm_events_fold_cpu(cpu);
> refresh_cpu_vm_stats(cpu);
> unlock_cpu_pcp(flags, cpu);
next prev parent reply other threads:[~2006-11-29 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 19:48 [PATCH -rt] 2.6.19-4c6-rt9 build problem Paul E. McKenney
2006-11-29 20:03 ` Ingo Molnar
2006-11-29 22:44 ` Paul E. McKenney
2006-11-29 23:15 ` Paul E. McKenney [this message]
2006-11-30 7:19 ` 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=20061129231507.GG2335@us.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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