From: Andrea Arcangeli <andrea@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: flush_tlb_all in vmalloc_area_pages
Date: Fri, 21 Sep 2001 00:52:25 +0200 [thread overview]
Message-ID: <20010921005225.K729@athlon.random> (raw)
In-Reply-To: <20010907165612.T11329@athlon.random> <20010920.142638.68040129.davem@redhat.com> <20010921002547.G729@athlon.random> <20010920.152919.35356833.davem@redhat.com> <20010921003845.J729@athlon.random>
In-Reply-To: <20010921003845.J729@athlon.random>; from andrea@suse.de on Fri, Sep 21, 2001 at 12:38:45AM +0200
On Fri, Sep 21, 2001 at 12:38:45AM +0200, Andrea Arcangeli wrote:
> On Thu, Sep 20, 2001 at 03:29:19PM -0700, David S. Miller wrote:
> > Please, I would heavily suggest leaving this area until 2.5.x there
>
> ok
Linus please apply to next pre patch, I understood from David that for
him the direct mapping can overlap the vmalloc virtual address space, it
really doesn't make much sense to me but since this is a noop for me and
I trust him, we can really delay this to 2.5:
--- 2.4.10pre12aa2/mm/vmalloc.c.~1~ Thu Sep 20 01:44:20 2001
+++ 2.4.10pre12aa2/mm/vmalloc.c Fri Sep 21 00:40:48 2001
@@ -144,6 +144,7 @@
int ret;
dir = pgd_offset_k(address);
+ flush_cache_all();
spin_lock(&init_mm.page_table_lock);
do {
pmd_t *pmd;
And btw, now I suspect David can have also have an arguments for the
tlb_flush removal (infact the problem is the same, if the address space
is shared by direct mapping and vmalloc we'd also need to flush the
tlb), but such one isn't really a noop for the other archs so I will be
more concerned not to reintroduce it and to at least just put an #ifndef
__i386__ around it (safe for both parts).
Andrea
prev parent reply other threads:[~2001-09-20 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 14:56 flush_tlb_all in vmalloc_area_pages Andrea Arcangeli
2001-09-20 21:26 ` David S. Miller
2001-09-20 22:25 ` Andrea Arcangeli
2001-09-20 22:29 ` David S. Miller
2001-09-20 22:38 ` Andrea Arcangeli
2001-09-20 22:52 ` Andrea Arcangeli [this message]
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=20010921005225.K729@athlon.random \
--to=andrea@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@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