From: Andrew Morton <akpm@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: Re: periodically-drain-non-local-pagesets-fix.patch added to -mm
Date: Fri, 03 Jun 2005 07:35:44 +0000 [thread overview]
Message-ID: <20050603003544.3deb0ec2.akpm@osdl.org> (raw)
In-Reply-To: <20050602231057.580dcaa3.akpm@osdl.org>
Keith Owens <kaos@sgi.com> wrote:
>
> On Fri, 3 Jun 2005 00:22:10 -0700,
> Andrew Morton <akpm@osdl.org> wrote:
> >Keith Owens <kaos@sgi.com> wrote:
> >> Does this fix the problem? Compiled but not tested.
> >
> >Well it'll make the warning go away but I think there's a more fundamental
> >problem, in that:
> >
> > get_cpu();
> > cond = something_which_uses_smp_processor_id();
> > put_cpu();
> >
> > /* `cond' can become false at any time from here */
>
> Good point. The entire fpu load/restore logic on ia64 needs reviewing
> for preemption. There is an implicit assumption that the fpu state is
> atomically saved and restored on the current cpu, while under the
> control of psr->mfh. Preempt has the potential to migrate a task while
> it is in the middle of save/restore fpu, breaking that assumption.
> Other ia64 register save/restore code might have similar problems.
OK, thanks. Could someone please spin up a disable-preempt-on-ia64 patch
for the 2.6.12 release?
> Leaving this one to the rest of the list.
Sensible man ;)
next prev parent reply other threads:[~2005-06-03 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 6:10 periodically-drain-non-local-pagesets-fix.patch added to -mm Andrew Morton
2005-06-03 7:15 ` periodically-drain-non-local-pagesets-fix.patch added to -mm tree Keith Owens
2005-06-03 7:22 ` periodically-drain-non-local-pagesets-fix.patch added to -mm Andrew Morton
2005-06-03 7:31 ` periodically-drain-non-local-pagesets-fix.patch added to -mm tree Keith Owens
2005-06-03 7:35 ` Andrew Morton [this message]
2005-06-03 7:52 ` periodically-drain-non-local-pagesets-fix.patch added to -mm Christoph Lameter
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=20050603003544.3deb0ec2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-ia64@vger.kernel.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