From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: swsusp_restore crap
Date: Tue, 15 Mar 2005 23:23:27 +0100 [thread overview]
Message-ID: <200503152323.27793.rjw@sisk.pl> (raw)
In-Reply-To: <20050315204652.GA20521@elf.ucw.cz>
On Tuesday, 15 of March 2005 21:46, Pavel Machek wrote:
> Hi!
>
> > > > > x86-64 needs this, too.... Otherwise it looks okay.
> > > >
> > > > It breaks compilation on i386 either, because nr_copy_pages_check
> > > > is static in swsusp.c. May I propose the following patch instead (tested on
> > > > x86-64 and i386)?
> > >
> > >
> > > > +asmlinkage int __swsusp_flush_tlb(void)
> > > > +{
> > > > + swsusp_restore_check();
> > >
> > > Someone will certainly forget this one, and it is probably
> > > nicer/easier to just move BUG_ON into swsusp_suspend(), just after
> > > restore_processor_state() or something like that...
> >
> > ... in which case __swsusp_flush_tlb() would only contain a "call" to
> > __flush_tlb_global(), but this is a macro on both x86-64 and i386, so we can
> > drop the __swsusp_flush_tlb() altogether and do it in assembly (before the
> > GPRs are restored, perhaps). Patch follows.
> >
> > Greets,
> > Rafael
> >
> >
> > Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
>
> > diff -Nrup linux-2.6.11-bk10-a/arch/x86_64/kernel/suspend_asm.S linux-2.6.11-bk10-b/arch/x86_64/kernel/suspend_asm.S
> > --- linux-2.6.11-bk10-a/arch/x86_64/kernel/suspend_asm.S 2005-03-15 09:20:53.000000000 +0100
> > +++ linux-2.6.11-bk10-b/arch/x86_64/kernel/suspend_asm.S 2005-03-15 15:36:29.000000000 +0100
> > @@ -69,6 +69,14 @@ loop:
> > movq pbe_next(%rdx), %rdx
> > jmp loop
> > done:
> > + /* Flush TLB, including "global" things (vmalloc) */
> > + movq %rax, %rdx; # mmu_cr4_features(%rip)
>
> I somehow don't think %rax contains mmu_cr4_features at this
> point. Otherwise it seems to look ok.
Yes, it does, because on x86-64 the TLBs are flushed before the loop,
right after %cr3 is loaded with init_level4_pgt. %rax is not touched
afterwards, so it contains the right value. Here's the relevant code
from suspend_asm.S (with the patch applied):
ENTRY(swsusp_arch_resume)
/* set up cr3 */
leaq init_level4_pgt(%rip),%rax
subq $__START_KERNEL_map,%rax
movq %rax,%cr3
movq mmu_cr4_features(%rip), %rax
movq %rax, %rdx
andq $~(1<<7), %rdx # PGE
movq %rdx, %cr4; # turn off PGE
movq %cr3, %rcx; # flush TLB
movq %rcx, %cr3;
movq %rax, %cr4; # turn PGE back on
movq pagedir_nosave(%rip), %rdx
loop:
testq %rdx, %rdx
jz done
/* get addresses from the pbe and copy the page */
movq pbe_address(%rdx), %rsi
movq pbe_orig_address(%rdx), %rdi
movq $512, %rcx
rep
movsq
/* progress to the next pbe */
movq pbe_next(%rdx), %rdx
jmp loop
done:
/* Flush TLB, including "global" things (vmalloc) */
movq %rax, %rdx; # mmu_cr4_features(%rip)
andq $~(1<<7), %rdx; # PGE
movq %rdx, %cr4; # turn off PGE
movq %cr3, %rcx; # flush TLB
movq %rcx, %cr3
movq %rax, %cr4; # turn PGE back on
Greets,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
next prev parent reply other threads:[~2005-03-15 22:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 3:24 Benjamin Herrenschmidt
2005-03-15 3:31 ` Benjamin Herrenschmidt
2005-03-15 11:03 ` Pavel Machek
2005-03-15 11:51 ` Rafael J. Wysocki
2005-03-15 12:02 ` Pavel Machek
2005-03-15 13:27 ` Benjamin Herrenschmidt
2005-03-15 14:55 ` Rafael J. Wysocki
2005-03-15 20:46 ` Pavel Machek
2005-03-15 22:23 ` Rafael J. Wysocki [this message]
2005-03-15 23:39 ` Pavel Machek
2005-03-16 0:08 ` Rafael J. Wysocki
2005-03-15 13:26 ` Benjamin Herrenschmidt
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=200503152323.27793.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®