From: Thomas Schlichter <thomas.schlichter@web.de>
To: linux-kernel@vger.kernel.org
Subject: some questions about flush_map() in pageattr.c
Date: Wed, 8 Jan 2003 19:29:02 +0100 [thread overview]
Message-ID: <200301081929.02202.thomas.schlichter@web.de> (raw)
Hello,
currently I am writing a patch to be able to make TLBs on any IO-devices
coherent to the CPUs TLBs. So I was looking in the kernel-sources for places
where not only the local but all TLBs are flushed. So I came up with
flush_map() in the arch/i386/mm/ and the arch/x86_64/mm/ directories.
Now my questions:
1. In the x86_64 part of code the flush_kernel_map() does a
local_flush_tlb_one() but in the i386 parts a local_flush_tlb_all(). Is the
mentioned athlon bug the cause or can it be changed to work as in the x86_64
code?
2. Can the flush_map() function be replaced by a flush_tlb_all() respective
flush_tlb_page(). If I can do so, what would be the correct value for the
first argument 'vma'?
If it is not posible could you please tell me why not...?
Thank you very much!
Thomas Schlichter
reply other threads:[~2003-01-08 18:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200301081929.02202.thomas.schlichter@web.de \
--to=thomas.schlichter@web.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