From: Timur Tabi <ttabi@interactivesi.com>
To: Linux Kernel Mailing list <linux-kernel@vger.kernel.org>
Cc: Linux MM mailing list <linux-mm@kvack.org>
Subject: Re: Page Attribute Table (PAT) support?
Date: Wed, 24 Jan 2001 15:31:37 -0600 [thread overview]
Message-ID: <20010124212848Z131205-223+51@kanga.kvack.org> (raw)
In-Reply-To: <3A6F45F4.8020004@valinux.com>
** Reply to message from Jeff Hartmann <jhartmann@valinux.com> on Wed, 24 Jan
2001 14:15:32 -0700
> Pages with multiple mappings aren't really supported by the Intel ia32
> architecture. The trick you do above works, but is strongly discouraged
> by the Intel documentation. The documentation says that if you do this
> with UCWC memory, it won't work (and will result in undefined processor
> behavior.) My experiments with the PAT seem to agree with the
> documentation.
Is it still a problem even we never access the memory through the non-UCWC
memory?
> We have to remove the kernel page table mappings. (Convert the 4MB pages
> to individual pte's, then change the individual pte so its pgprot value
> is correct.)
That sounds like an incredible amount of work! Are you going to support this
in your code? I wouldn't even know how to begin implementing that.
> When you allocate memory in the kernel, you OWN it. Its not mapped into
> a user space process unless you put it there. I have to point out that
> this interface requires the user to insure these pages are never ever
> swapped, or mapped cached. This isn't a huge restriction, since we
> aren't providing a user land interface. If we try to handle all/some of
> these cases in the kernel, it becomes a very large problem. We would
> have to add arch specific bits for special cache handling, Do smp cache
> flushes all over the place, etc. Its really not worth it.
Ok, so what are you going to provide? All I need is a method to access a
particular physical page, whether it's part of real RAM or not, in an UCWC
manner. Can you give me a hint as to how that cability can be provided?
--
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com
When replying to a mailing-list message, please direct the reply to the mailing list only. Don't send another copy to me.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-01-24 21:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010124174824Z129401-18594+948@vger.kernel.org>
2001-01-24 18:45 ` Jeff Hartmann
2001-01-24 18:50 ` Timur Tabi
2001-01-24 20:30 ` Timur Tabi
2001-01-24 20:41 ` Jeff Hartmann
2001-01-24 20:48 ` Timur Tabi
[not found] ` <20010124204811Z129375-18594+1059@vger.kernel.org>
2001-01-24 21:15 ` Jeff Hartmann
2001-01-24 21:31 ` Timur Tabi [this message]
2001-01-24 20:30 ` Timur Tabi
[not found] ` <20010124185046Z131368-18595+642@vger.kernel.org>
2001-01-24 19:30 ` Jeff Hartmann
2001-01-24 17:48 Timur Tabi
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=20010124212848Z131205-223+51@kanga.kvack.org \
--to=ttabi@interactivesi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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