mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Zhao Forrest" <forrest.zhao@gmail.com>
To: discuss@x86-64.org
Cc: linux-kernel@vger.kernel.org
Subject: A question about GART aperture unmap
Date: Thu, 10 May 2007 13:59:35 +0800	[thread overview]
Message-ID: <ac8af0be0705092259p65f057bcoe5e1b9abb963d5e3@mail.gmail.com> (raw)

Hi,

The following is extracted from function gart_iommu_init()
......
/*
* Unmap the IOMMU part of the GART. The alias of the page is
* always mapped with cache enabled and there is no full cache
* coherency across the GART remapping. The unmapping avoids
* automatic prefetches from the CPU allocating cache lines in
* there. All CPU accesses are done via the direct mapping to
* the backing memory. The GART address is only used by PCI
* devices.
*/
clear_kernel_mapping((unsigned long)__va(iommu_bus_base), iommu_size);
......

On my AMD-based system, the GART aperture is reserved as:
Mapping aperture over 65536 KB of RAM @ 4000000

After commenting out clear_kernel_mapping() line, the system would
have sync flood and reset from time to time. However when with this
clear_kernel_mapping() line, no system reset happened.

As we know that CPU prefetch never cross the page boundary, in this
case the page boundary is 4M. Aperture starting address is 4000000,
which is aligned with 4M. So I think CPU prefetch can not touch this
range reserved by GART aperture.

My question is: in which cases would CPU prefetch touch the address
range reserved by GART aperture?

Thanks,
Forrest

             reply	other threads:[~2007-05-10  5:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10  5:59 Zhao Forrest [this message]
2007-05-10  9:49 ` [discuss] " Andi Kleen
2007-05-10 10:00   ` Zhao Forrest
2007-05-10 10:09   ` Zhao Forrest
2007-05-10 10:14   ` Zhao Forrest
2007-05-10 11:06     ` Andi Kleen

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=ac8af0be0705092259p65f057bcoe5e1b9abb963d5e3@mail.gmail.com \
    --to=forrest.zhao@gmail.com \
    --cc=discuss@x86-64.org \
    --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

all inboxes | Powered by JetHome®