[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTi=RWG_iiyd1f_aGEpqk9Cbh1dT7iw@mail.gmail.com>
Date: Mon, 30 May 2011 01:33:26 +0400
From: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
To: David Rientjes <rientjes@...gle.com>
Cc: Nicolas Pitre <nicolas.pitre@...aro.org>,
Russell King <rmk+kernel@....linux.org.uk>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Eric Miao <eric.y.miao@...il.com>,
Samuel Ortiz <samuel@...tiz.org>
Subject: Re: IrDA driver fails on PXA255
On Mon, May 30, 2011 at 1:17 AM, David Rientjes <rientjes@...gle.com> wrote:
> On Sun, 29 May 2011, Dmitry Eremin-Solenikov wrote:
>
>> What about changing your patch for less intrusive one (to emit a
>> WARN_ON) for at least one
>> or two major releases and only then changing it back to the current state?
>>
>
> That would return memory that is not guaranteed to be within the first
> 16MB of address space, so a GFP_DMA allocation would succeed with memory
> not from ZONE_DMA. That's an invalid configuration, so users, including
> you, should at least edit their .config by hand to enable CONFIG_ZONE_DMA
> as a workaround. Then, we should try to fix up the Kconfig entries for
> drivers requiring DMA allocations to select CONFIG_ZONE_DMA or fix
> defconfigs when DMA is known to be needed for a device.
Am I right that this was the previous behaviour for GFP_DMA allocations
w/o CONFIG_ZONE_DMA? If so, we can have it (probably) for one more
major release to get all warnings.
--
With best wishes
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists