From: Bob Montgomery <bob.montgomery@hp.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Dave Jones <davej@redhat.com>, Yinghai Lu <yinghai@kernel.org>,
Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vojtech@suse.cz" <vojtech@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
"chandru@in.ibm.com" <chandru@in.ibm.com>,
Joerg Roedel <joerg.roedel@amd.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] disable CPU side GART accesses
Date: Wed, 19 Nov 2008 15:12:14 -0700 [thread overview]
Message-ID: <1227132734.3428.142.camel@amd.troyhebe> (raw)
In-Reply-To: <21d7e9970811031555y2e8187c5q5b8768800e176bd4@mail.gmail.com>
On Mon, 2008-11-03 at 23:55 +0000, Dave Airlie wrote:
> On Tue, Nov 4, 2008 at 9:36 AM, Bob Montgomery <bob.montgomery@hp.com> wrote:
> > We're specifically talking about AMD64, and we're not using an IOMMU for
> > AGP, we're using the AMD64 implementation of the GART for an IOMMU.
> > The (possible) danger is that some old AMD64 system could also (or
> > instead) try using the GART for AGP and run into a problem since my
> > patch wants to disable CPU side access to the aperture, which is fine
> > when we're using it as an IOMMU.
> >
> > In drivers/gpu/drm/drm_memory.c:agp_remap(), there are these comments
> > about the part of the code that deals with "cant_use_aperture":
> >
> > /*
> > * OK, we're mapping AGP space on a chipset/platform on which
> > * memory accesses by the CPU do not get remapped by the GART.
> > * We fix this by using the kernel's page-table instead (that's
> > * probably faster anyhow...).
> > */
> >
> > So that's encouraging. Now the question is this: Can I just go into
> > amd64-agp.c and add ".cant_use_aperture=true" to the agp_bridge_driver
> > struct? Who's brave enough to say that will just work? :-)
>
> I have serious doubts about including such a patch without testing on
> a large range of AMD64 systems
> with a large range of distro/X servers.
>
> Dave.
Well, since I hate it when kernel discussion threads just end with no
resolution...
I don't have access to a large range of AMD64 systems that use AGP
graphics. In fact, I can't find any around here. So testing my way to
resolving this potential problem in these drivers is probably not going
to work.
I've seen references to systems that had Opterons, and AGP graphics, and
could hold more than 4GB of RAM, but I don't know how many are out
there. So since I can't do a bunch of distro/X server testing, I'm not
sure how to proceed to get as simple a fix for this problem on real
systems that do exist now.
Bob Montgomery
prev parent reply other threads:[~2008-11-19 22:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 21:48 Bob Montgomery
2008-10-15 23:40 ` Linus Torvalds
2008-10-16 19:17 ` Bob Montgomery
2008-10-15 23:48 ` Ingo Molnar
2008-10-16 0:22 ` Yinghai Lu
2008-10-16 17:00 ` Bob Montgomery
2008-10-16 17:43 ` Yinghai Lu
2008-10-16 19:26 ` Bob Montgomery
2008-10-27 22:42 ` Bob Montgomery
2008-10-27 23:06 ` Yinghai Lu
2008-10-29 20:52 ` Bob Montgomery
2008-10-29 21:24 ` Dave Airlie
2008-10-29 21:32 ` Dave Jones
2008-10-29 21:40 ` Dave Airlie
2008-11-03 23:36 ` Bob Montgomery
2008-11-03 23:55 ` Dave Airlie
2008-11-19 22:12 ` Bob Montgomery [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=1227132734.3428.142.camel@amd.troyhebe \
--to=bob.montgomery@hp.com \
--cc=airlied@gmail.com \
--cc=chandru@in.ibm.com \
--cc=davej@redhat.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jbarnes@virtuousgeek.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=torvalds@linux-foundation.org \
--cc=vojtech@suse.cz \
--cc=yinghai@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
Powered by JetHome