From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [rfc] generic allocator and mspec driver
Date: Thu, 03 Feb 2005 17:06:53 +0000 [thread overview]
Message-ID: <200502030906.54144.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <16897.9640.160896.31584@jaguar.mkp.net>
On Thursday, February 3, 2005 12:38 am, Jes Sorensen wrote:
> Jack> ... + printk(KERN_WARNING "smp_call_function failed for " +
> Jack> "mspec_ipi_visibility! (%i)\n", status); + } + +
> Jack> sn_flush_all_caches((unsigned long)tmp, IA64_GRANULE_SIZE);
>
> Jack> Don't the TLBs need to be flushed before you flush
> Jack> caches. Otherwise, the cpu may reload data via speculation.
>
> Jack> I dont see any TLB flushing of the kernel TLB entries that map
> Jack> the chunks. That needs to be done. ...
>
> I thought about this one a fair bit after reading your comments and I
> don't think it's an issue. The pages in the kernel's cached mapping
> are identity mapped which means we shouldn't see any tlbs for this,
> which leaves us with just tlbs for pages that have explicitly been
> mapped somewhere - user tlbs should be removed when a process is shot
> down or pages unmapped and vfree() calls flush_tlb_all(). Or, am I
> missing something?
Even identity mapped regions have TLB entries associated with them. The
translation registers only cover the code and static data section, afaik.
When we take a miss on an identity mapped region, the kernel still does an
'itc', so you'll still need to purge the TLB.
Jesse
next prev parent reply other threads:[~2005-02-03 17:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 19:10 [rfc] generic allocator and mspec driver Jes Sorensen
2005-02-02 19:46 ` Jesse Barnes
2005-02-02 23:33 ` Jack Steiner
2005-02-03 7:47 ` Jes Sorensen
2005-02-03 8:38 ` Jes Sorensen
2005-02-03 11:19 ` Robin Holt
2005-02-03 14:55 ` Jes Sorensen
2005-02-03 17:06 ` Jesse Barnes [this message]
2005-02-03 17:31 ` Dean Roe
2005-02-03 17:31 ` Robin Holt
2005-02-03 17:41 ` Jesse Barnes
2005-02-03 18:54 ` Jack Steiner
2005-02-03 19:39 ` David Mosberger
2005-02-03 20:58 ` Jes Sorensen
2005-02-03 21:40 ` Luck, Tony
2005-02-04 1:00 ` David Mosberger
2005-02-13 21:57 ` Jes Sorensen
2005-02-14 19:12 ` Luck, Tony
2005-02-14 19:17 ` David Mosberger
2005-02-15 8:43 ` Jes Sorensen
2005-02-15 8:44 ` Jes Sorensen
2005-02-15 17:35 ` Grant Grundler
2005-02-15 18:04 ` David Mosberger
2005-02-15 18:05 ` David Mosberger
2005-02-15 19:11 ` Robin Holt
2005-02-15 19:19 ` David Mosberger
2005-02-15 19:49 ` Robin Holt
2005-02-15 19:59 ` Jes Sorensen
2005-02-15 20:02 ` Jes Sorensen
2005-02-15 20:24 ` Robin Holt
2005-02-16 7:32 ` Jes Sorensen
2005-02-16 14:17 ` Jes Sorensen
2005-02-16 17:50 ` Luck, Tony
2005-02-16 18:18 ` Luck, Tony
2005-02-16 19:10 ` Jes Sorensen
2005-02-16 21:02 ` David Mosberger
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=200502030906.54144.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--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