LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Cc: LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.24-rc7-rt1: macro "put_cpu_var" passed 2 arguments, but takes just 1
Date: Sun, 13 Jan 2008 15:37:33 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.58.0801131519410.9934@gandalf.stny.rr.com> (raw)
In-Reply-To: <200801132053.22830.m.kozlowski@tuxland.pl>
On Sun, 13 Jan 2008, Mariusz Kozlowski wrote:
> [... snip ...]
>
> @@ -56,12 +64,13 @@ static inline void __quicklist_free(int
> struct page *page)
> {
> struct quicklist *q;
> + int cpu;
>
> - q = &get_cpu_var(quicklist)[nr];
> + q = &get_cpu_var_locked(quicklist, &cpu)[nr];
> *(void **)p = q->page;
> q->page = p;
> q->nr_pages++;
> - put_cpu_var(quicklist);
> + put_cpu_var(quicklist, cpu); <------------- should that be put_cpu_var_locked()?
> }
>
Ouch! <looks at rejs>
*************** static inline void __quicklist_free(int
*** 76,86 ****
return;
}
- q = &get_cpu_var(quicklist)[nr];
*(void **)p = q->page;
q->page = p;
q->nr_pages++;
- put_cpu_var(quicklist);
}
static inline void quicklist_free(int nr, void (*dtor)(void *), void *pp)
--- 73,83 ----
return;
}
+ q = &get_cpu_var_locked(quicklist, &cpu)[nr];
*(void **)p = q->page;
q->page = p;
q->nr_pages++;
+ put_cpu_var_locked(quicklist, cpu);
}
static inline void quicklist_free(int nr, void (*dtor)(void *), void *pp)
************
Darn, that was my fault. OK, will release a -rt2 soon.
Thanks,
-- Steve
next prev parent reply other threads:[~2008-01-13 20:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 19:00 2.6.24-rc7-rt1 Steven Rostedt
2008-01-13 19:53 ` 2.6.24-rc7-rt1: macro "put_cpu_var" passed 2 arguments, but takes just 1 Mariusz Kozlowski
2008-01-13 20:37 ` Steven Rostedt [this message]
2008-01-13 20:25 ` 2.6.24-rc7-rt1 Robert Schwebel
2008-01-13 20:48 ` 2.6.24-rc7-rt1 Steven Rostedt
2008-01-14 19:49 ` 2.6.24-rc7-rt1 Robert Schwebel
2008-01-13 20:43 ` 2.6.24-rc7-rt1 Mariusz Kozlowski
2008-01-13 20:54 ` 2.6.24-rc7-rt1 Steven Rostedt
2008-01-14 8:27 ` 2.6.24-rc7-rt1 Mike Galbraith
2008-01-14 12:13 ` 2.6.24-rc7-rt1 Gregory Haskins
2008-01-14 13:25 ` 2.6.24-rc7-rt1 Mike Galbraith
2008-01-14 14:29 ` 2.6.24-rc7-rt1 Mike Galbraith
2008-01-15 8:07 ` 2.6.24-rc7-rt1 Mike Galbraith
2008-01-15 9:28 ` 2.6.24-rc7-rt1 Mike Galbraith
2008-01-15 16:50 ` 2.6.24-rc7-rt1 Gregory Haskins
2008-01-14 18:39 ` 2.6.24-rc7-rt1 S.Çağlar Onur
2008-01-14 16:52 ` 2.6.24-rc7-rt1 Steven Rostedt
2008-01-13 22:56 ` 2.6.24-rc7-rt1 Mark Knecht
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=Pine.LNX.4.58.0801131519410.9934@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).