From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Hellstrom <thellstrom@vmware.com>,
Dave Airlie <airlied@linux.ie>,
Arjan van de Ven <arjan@infradead.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"dri-devel@lists.sourceforge.net"
<dri-devel@lists.sourceforge.net>
Subject: Re: [PATCH] x86: Fix CPA memtype reserving in the set_pages_array cases
Date: Mon, 03 Aug 2009 09:58:25 -0700 [thread overview]
Message-ID: <1249318705.27006.10777.camel@localhost.localdomain> (raw)
In-Reply-To: <20090803104454.GB18165@elte.hu>
On Mon, 2009-08-03 at 03:44 -0700, Ingo Molnar wrote:
> ok - thanks for the explanation. Since you intentionally want to use
> highmem pages (and your use is safe) i concur with your original
> patch in its entirety - even if that planned highmem use is not
> upstream yet. Will get it .31-wards ASAP.
Acked-by: Suresh Siddha <suresh.b.siddha@intel.com>
While none of the drivers in 2.6.30 use this interface, it will be good
if we backport this to 2.6.30-stable aswell.
Also, now that we have set_pages_array interface, do we still need the
set_memory_array_uc interface? Removing that should clean up the cpa
code a bit.
thanks,
suresh
next prev parent reply other threads:[~2009-08-03 17:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 7:25 Thomas Hellstrom
2009-08-03 8:11 ` Ingo Molnar
2009-08-03 8:29 ` Dave Airlie
2009-08-03 8:39 ` Thomas Hellstrom
2009-08-03 9:19 ` Ingo Molnar
2009-08-03 10:18 ` Thomas Hellstrom
2009-08-03 10:44 ` Ingo Molnar
2009-08-03 16:58 ` Suresh Siddha [this message]
2009-08-03 19:31 ` CPA interfaces WAS " Thomas Hellström
2009-08-03 9:18 ` [PATCH] " Ingo Molnar
2009-08-03 10:51 ` [tip:x86/urgent] x86: Fix CPA memtype reserving in the set_pages_array*() cases tip-bot for Thomas Hellstrom
2009-08-03 17:39 ` tip-bot for Thomas Hellstrom
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=1249318705.27006.10777.camel@localhost.localdomain \
--to=suresh.b.siddha@intel.com \
--cc=airlied@linux.ie \
--cc=arjan@infradead.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=thellstrom@vmware.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®