From: Ingo Molnar <mingo@elte.hu>
To: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@redhat.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Eric Anholt <eric@anholt.net>,
Thomas Gleixner <tglx@linutronix.de>,
H Peter Anvin <hpa@zytor.com>, Keith Packard <keithp@keithp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 0/4] gpu/drm, x86, PAT: Add PAT support for io_mapping_* interface
Date: Wed, 25 Feb 2009 13:08:39 +0100 [thread overview]
Message-ID: <20090225120839.GC14279@elte.hu> (raw)
In-Reply-To: <20090225013510.010493000@intel.com>
* Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> wrote:
> io_mapping_create_wc(), io_mapping_free() and associated map/unmap routines
> are relatively new set of APIs for drivers, that change memory type.
>
> Currently, these interfaces hardcode WC type on x86 and does not go through
> "PAT enforcement". This patchset adds PAT support for this interface.
>
> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
hm, the patches look sane and clean and mostly factor out
existing code and checks and apply them to the io_mapping_*()
interfaces - so it's something worth having for .29.
But it's all rather awfully late in the cycle and ioremap type
of bugs typically have 1-2 rc's of latency to be fully
discovered.
They will probably fix a few regressions and are easy to revert,
plus they affect the one driver whose authors wrote these
facilities:
drivers/gpu/drm/i915/i915_dma.c
drivers/gpu/drm/i915/i915_gem.c
so maybe we should try it as it's all a clear step forward. I'll
give them a spin in tip:x86/urgent. Dunno.
Linus, do you have any preference?
Ingo
next parent reply other threads:[~2009-02-25 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090225013510.010493000@intel.com>
2009-02-25 12:08 ` Ingo Molnar [this message]
2009-02-25 14:06 ` Pallipadi, Venkatesh
2009-02-25 15:41 ` Ingo Molnar
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=20090225120839.GC14279@elte.hu \
--to=mingo@elte.hu \
--cc=airlied@redhat.com \
--cc=eric@anholt.net \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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®