From: Andi Kleen <ak@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: preempt bug in set_pmd_pfn?
Date: Wed, 5 Mar 2008 01:16:45 +0100 [thread overview]
Message-ID: <200803050116.46119.ak@suse.de> (raw)
In-Reply-To: <47CDE42F.8080400@goop.org>
On Wednesday 05 March 2008 01:07:11 Jeremy Fitzhardinge wrote:
> Andi Kleen wrote:
> >> Won't this leave a stale tlb on the old processor?
> >>
> >
> > __set_fixmap should be only used in early boot, so it's always
> > on CPU 0
>
> vdso32-setup.c:map_compat_vdso() uses it to create the compat vdso
> mapping, which typically happens on the first execve(),
First execve for 32bit binaries?
Anyways __set_fixmap is __init and at the first execve (unless you have initramfs)
init.text should be already freed.
-Andi
next prev parent reply other threads:[~2008-03-05 0:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 21:13 preempt bug in set_pmd_pfn? Jeremy Fitzhardinge
2008-03-04 21:28 ` Ingo Molnar
2008-03-04 21:27 ` Jeremy Fitzhardinge
2008-03-05 6:48 ` Ingo Molnar
2008-03-05 14:29 ` Hugh Dickins
2008-03-05 16:48 ` Jeremy Fitzhardinge
2008-03-05 17:38 ` Hugh Dickins
2008-03-05 19:18 ` Jeremy Fitzhardinge
2008-03-05 20:40 ` Hugh Dickins
2008-03-06 12:52 ` Ingo Molnar
2008-03-06 18:19 ` Jeremy Fitzhardinge
2008-03-05 16:45 ` Jeremy Fitzhardinge
2008-03-05 0:06 ` Andi Kleen
2008-03-05 0:07 ` Jeremy Fitzhardinge
2008-03-05 0:16 ` Andi Kleen [this message]
2008-03-05 0:19 ` Jeremy Fitzhardinge
2008-03-05 1:28 ` Andi Kleen
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=200803050116.46119.ak@suse.de \
--to=ak@suse.de \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--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 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.