public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: andrea@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: flush_tlb_all in vmalloc_area_pages
Date: Thu, 20 Sep 2001 15:29:19 -0700 (PDT)	[thread overview]
Message-ID: <20010920.152919.35356833.davem@redhat.com> (raw)
In-Reply-To: <20010921002547.G729@athlon.random>
In-Reply-To: <20010907165612.T11329@athlon.random> <20010920.142638.68040129.davem@redhat.com> <20010921002547.G729@athlon.random>

   From: Andrea Arcangeli <andrea@suse.de>
   Date: Fri, 21 Sep 2001 00:25:47 +0200

   The only question I'd like to get a answer is "what is actually the
   data that can be virtually indexed) in the vmalloc range at the time we
   run vmalloc?" Where does it cames from?
   
>From the the direct PAGE_OFFSET mappings.

   Furthmore I recall on sparc you cannot flush the cache if you don't have
   a mapping in place,

This is only true of Hypersparc sparc32 chips for page based flushes,
not whole flushes.

   If anybody is using at boot time the vmalloc range for whatever purpuse
   it should be its own business to flush the cache before dropping the
   mappings from there.
   
That isn't the problem, it's dirty cache lines left over from the
usual access addresses for physical memory (ie. via PAGE_OFFSET linear
mappings).

Please, I would heavily suggest leaving this area until 2.5.x there
are already a traumatic amount of changes going on in 2.4.x

Later,
David S. Miller
davem@redhat.com

   

  reply	other threads:[~2001-09-20 22:29 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 [this message]
2001-09-20 22:38       ` Andrea Arcangeli
2001-09-20 22:52         ` Andrea Arcangeli

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=20010920.152919.35356833.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=andrea@suse.de \
    --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