public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jesse.barnes@intel.com>
To: Keith Packard <keithp@keithp.com>
Cc: Dave Airlie <airlied@skynet.ie>,
	linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: [RFC] AGP initial support for chipset flushing..
Date: Mon, 29 Oct 2007 13:28:09 -0700	[thread overview]
Message-ID: <200710291328.10763.jesse.barnes@intel.com> (raw)
In-Reply-To: <1193688778.4723.35.camel@koto.keithp.com>

On Monday, October 29, 2007 1:12 pm Keith Packard wrote:
> On Mon, 2007-10-29 at 12:47 -0700, Jesse Barnes wrote:
> > In this case, we're performing basically a
> > dma_sync*(...DMA_TO_DEVICE) right?
>
> But this is just for the GPU; every other DMA device in the system is
> cache-coherent.

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?
>
> An uncached write to this page will not complete until the buffers
> are completely flushed.

Yeah, so we should be safe.

> > 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.
>
> This isn't a hidden mapping; the i965 doesn't allocate space for it
> in the BIOS.

I know, that's what I'm worried about.  If the BIOS is broken enough to 
not allocate MMIO space for the flush page, it may also be broken 
enough that our hand crafted MMIO space allocation will end up 
conflicting with some unreported BIOS area, which would be bad.

Jesse

      reply	other threads:[~2007-10-29 20:32 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
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 [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=200710291328.10763.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