mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: suresh.b.siddha@intel.com
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	Eric Anholt <eric@anholt.net>,
	lkml <linux-kernel@vger.kernel.org>,
	airlied@gmail.com
Subject: Re: PAGE_CACHE_WC strikes again
Date: Tue, 31 Mar 2009 18:57:12 -0700	[thread overview]
Message-ID: <20090331185712.482877d6@hobbes> (raw)
In-Reply-To: <1238549424.27006.7757.camel@localhost.localdomain>

On Tue, 31 Mar 2009 17:30:24 -0800
Suresh Siddha <suresh.b.siddha@intel.com> wrote:

> On Tue, 2009-03-31 at 18:12 -0700, Jesse Barnes wrote:
> > Right, the drm driver code went in before we had
> > pgprot_writecombine. Now that it's available we should definitely
> > use it.  I'm not sure about the set_memory_* routines though; we
> > create io mappings in i915_dma.c at init time, and I thought we
> > took care of things in i915_gem.c but we may need updates there.
> 
> Jesse, yes i915_gem.c seems to be doing the right thing.
> 
> What about various fault handlers in drm_vm.c like
> drm_do_vm_shm_fault() etc. None of these fault handlers require
> special attributes like wc/uc etc?

Those are legacy.  I don't think they need anything changed...  Dave
could correct me though.

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2009-04-01  1:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01  0:10 Eric Anholt
2009-04-01  0:14 ` Jesse Barnes
2009-04-01  0:29   ` Pallipadi, Venkatesh
2009-04-01  0:49     ` Jesse Barnes
2009-04-01  1:03     ` Suresh Siddha
2009-04-01  1:12       ` Jesse Barnes
2009-04-01  1:30         ` Suresh Siddha
2009-04-01  1:57           ` Jesse Barnes [this message]
2009-04-01  3:18             ` Dave Airlie
2009-04-01  3:17         ` Pallipadi, Venkatesh
2009-04-01  1:22       ` 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=20090331185712.482877d6@hobbes \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@gmail.com \
    --cc=eric@anholt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=venkatesh.pallipadi@intel.com \
    /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®