From: Pavel Machek <pavel@ucw.cz>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] don't use flush_tlb_all in suspend time
Date: Thu, 18 May 2006 10:31:47 +0200 [thread overview]
Message-ID: <20060518083146.GA12724@elf.ucw.cz> (raw)
In-Reply-To: <1147922973.32046.13.camel@sli10-desk.sh.intel.com>
Hi!
> > > In which case, how's about this?
> >
> > Certainly better, I'd say.
> >
> > > @@ -420,7 +421,14 @@ void zap_low_mappings (void)
> > > #else
> > > set_pgd(swapper_pg_dir+i, __pgd(0));
> > > #endif
> > > - if (cpus_weight(cpu_online_map) == 1)
> > > + /*
> > > + * We can be called at suspend/resume time, with local interrupts
> > > + * disabled. But flush_tlb_all() requires that local interrupts be
> > > + * enabled.
> > > + *
> > > + * Happily, the APs are not yet started, so we can use local_flush_tlb() * in that case
> > > + */
> > > + if (num_online_cpus() == 1)
> > > local_flush_tlb();
> > > else
> > > flush_tlb_all();
> >
> > But this still scares. It means calling convention is "may enable
> > interrupts with >1 cpu, may not with == 1 cpu".
> Below patch should make things clean. How do you think?
Nice...
Could we perhaps reuse swsusp_pg_dir (just make it used for swsusp &
suspend-to-ram) to save a bit more code? It is in arch/i386/mm/init.c
.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-05-18 8:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-30 3:24 [PATCH] don't use flush_tlb_all in suspend time Shaohua Li
2006-04-30 6:45 ` Pavel Machek
2006-04-30 6:46 ` Shaohua Li
2006-04-30 6:57 ` Andrew Morton
2006-04-30 7:19 ` Shaohua Li
2006-04-30 12:04 ` Pavel Machek
2006-05-08 2:27 ` Shaohua Li
2006-05-18 3:29 ` Shaohua Li
2006-05-18 8:31 ` Pavel Machek [this message]
2006-05-18 8:38 ` Shaohua Li
2006-05-18 8:46 ` Pavel Machek
2006-05-19 1:15 ` Shaohua Li
2006-05-20 15:50 ` Pavel Machek
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=20060518083146.GA12724@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
/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.