From: Ingo Molnar <mingo@elte.hu>
To: venkatesh.pallipadi@intel.com
Cc: ak@muc.de, ebiederm@xmission.com, rdreier@cisco.com,
torvalds@linux-foundation.org, gregkh@suse.de, airlied@skynet.ie,
davej@redhat.com, tglx@linutronix.de, hpa@zytor.com,
akpm@linux-foundation.org, arjan@infradead.org,
jesse.barnes@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 00/13] x86: PAT support updated - v3
Date: Fri, 21 Mar 2008 14:24:17 +0100 [thread overview]
Message-ID: <20080321132417.GJ27245@elte.hu> (raw)
In-Reply-To: <20080319000012.439150000@intel.com>
* venkatesh.pallipadi@intel.com <venkatesh.pallipadi@intel.com> wrote:
> Follow up on earlier PAT patch series here:
> http://lkml.org/lkml/2008/1/10/312
>
> This patch series adds Page Attribute Table (PAT) support on x86.
> There have been few changes based on comments for earlier patches and
> also issues that was seen while the earlier patchset was in mm. The
> main changes include:
>
> * Unlike earlier patchset, there are no changes to identity mapping of
> reserved regions.
> * Unlike earlier patches, there are no chanegs to early ioremap.
> * We look at MTRR setting and PAT request and track the resultant type
> to avoid aliasing.
> * UC_MINUS in PAT to provide backward compatibility to /dem/mem mmap users.
>
> In general, we have tried to make patches more simpler and cleaner.
> Hope is to cause less disruption along the way. The changes/cleaups
> that went into x86/mm (specifically pageattr.c) has helped us along
> the way.
>
> The patchset is against x86 testing from couple of days back.
thanks Venki, i've queued this up so that we can see how well it goes.
It now looks a lot less dangerous and more compatible than it did before
- but i'm sure there'll be issues nevertheless :-/
> There are two issues that we are leaving out at the moment to make the patch
> simple. We will be addressing them with incremental patches soon:
> * FB/DRM drivers using pgprot_val and changing protection on their own
> without using any proper APIs like ioremap. There are few such usages and
> each one will be addressed separately.
> * To change attributes from WC to WB in a "perfect way", one has to follow
> certain sequence like make page non-present etc.
hm, until this is done correctly i guess we should disallow WC to WB
transitions? A good number of erratas apply i suspect :-/
Ingo
next prev parent reply other threads:[~2008-03-21 13:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 0:00 [patch 00/13] x86: PAT support updated - v3 venkatesh.pallipadi
2008-03-19 0:00 ` [patch 01/13] x86: PAT documentation venkatesh.pallipadi
2008-03-19 0:00 ` [patch 02/13] x86: PAT infrastructure patch venkatesh.pallipadi
2008-03-19 20:06 ` Randy Dunlap
2008-03-24 21:22 ` Venki Pallipadi
2008-03-19 0:00 ` [patch 03/13] x86: PAT Avoid aliasing in /dev/mem read/write venkatesh.pallipadi
2008-03-19 0:00 ` [patch 04/13] x86: PAT make ioremap_change_attr non-static venkatesh.pallipadi
2008-03-19 0:00 ` [patch 05/13] x86: PAT use reserve free memtype in ioremap and iounmap venkatesh.pallipadi
2008-03-19 0:00 ` [patch 06/13] x86: PAT use reserve free memtype in set_memory_uc venkatesh.pallipadi
2008-03-19 0:00 ` [patch 07/13] x86: PAT use reserve free memtype in pci_mmap_page_range venkatesh.pallipadi
2008-03-19 0:00 ` [patch 08/13] x86: PAT phys_mem_access_prot_allowed for dev/mem mmap venkatesh.pallipadi
2008-03-19 0:00 ` [patch 09/13] x86: PAT use reserve free memtype in mmap of /dev/mem venkatesh.pallipadi
2008-03-19 0:00 ` [patch 10/13] x86: PAT export resource_wc in pci sysfs venkatesh.pallipadi
2008-03-19 0:00 ` [patch 11/13] x86: PAT Add set_memory_wc() interface venkatesh.pallipadi
2008-03-19 0:00 ` [patch 12/13] x86: PAT Add ioremap_wc() interface venkatesh.pallipadi
2008-03-19 0:00 ` [patch 13/13] x86: PAT Patch to add PAT related debug prints venkatesh.pallipadi
2008-03-21 13:24 ` Ingo Molnar [this message]
2008-03-21 14:55 ` [patch 00/13] x86: PAT support updated - v3 Ingo Molnar
2008-03-21 19:26 ` Venki Pallipadi
2008-03-21 13:29 ` H. Peter Anvin
2008-03-21 19:19 ` Venki Pallipadi
2008-03-21 19:59 ` H. Peter Anvin
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=20080321132417.GJ27245@elte.hu \
--to=mingo@elte.hu \
--cc=airlied@skynet.ie \
--cc=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=jesse.barnes@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
--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