From: Jesse Barnes <jesse.barnes@intel.com>
To: dri-devel@lists.sourceforge.net
Cc: Dave Airlie <airlied@skynet.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net,
keithp@keithp.com
Subject: Re: [RFC] AGP initial support for chipset flushing..
Date: Mon, 29 Oct 2007 12:47:23 -0700 [thread overview]
Message-ID: <200710291247.24791.jesse.barnes@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710290811070.1170@skynet.skynet.ie>
On Monday, October 29, 2007 1:15 am Dave Airlie wrote:
> Hi,
>
> We've uncovered a need when using the new memory manager to flush the
> chipset global write buffers on certain intel chipset due to a lack
> of coherency..
>
> The attached patches add a new AGP interface for this purpose and
> implements this in the Intel AGP driver. This stuff is based of some
> guesswork in the 915 case from comments in the documentation :).
In this case, we're performing basically a dma_sync*(...DMA_TO_DEVICE)
right? Can we be sure that a single flush is sufficient? Is there any
window between when we flush and when we start accessing memory with
the device that we could get into more caching trouble?
> Unfortuantely the 965 BIOS doesn't set this stuff up properly and it
> doesn't use a standard BAR address, so I have to do it by hand, I'd
> appreciate any commentary particularly in the setting up of the
> resource stuff.
Looks reasonable, I'm not sure we can do much better. The only concern
I have is that allocating some more PCI space like that may end up
clobbering some *other* hidden BIOS mapping, but there's not a whole
lot we can do about that.
Jesse
next prev parent reply other threads:[~2007-10-29 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 8:15 [RFC] AGP initial support for chipset flushing Dave Airlie
2007-10-29 15:50 ` Keith Packard
2007-10-29 19:47 ` Jesse Barnes [this message]
2007-10-29 19:52 ` Dave Airlie
2007-10-29 20:12 ` Jesse Barnes
2007-10-29 20:12 ` Keith Packard
2007-10-29 20:28 ` Jesse Barnes
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=200710291247.24791.jesse.barnes@intel.com \
--to=jesse.barnes@intel.com \
--cc=airlied@skynet.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=keithp@keithp.com \
--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