[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <70ab19eb-c41a-980d-46f6-2bb02163974e@infradead.org>
Date: Thu, 26 Jan 2023 16:57:18 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Dave Hansen <dave.hansen@...el.com>,
Georgi Djakov <quic_c_gdjako@...cinc.com>,
catalin.marinas@....com, will@...nel.org
Cc: dave.hansen@...ux.intel.com, luto@...nel.org, peterz@...radead.org,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, hpa@...or.com,
hch@....de, m.szyprowski@...sung.com, robin.murphy@....com,
linux-arm-kernel@...ts.infradead.org, iommu@...ts.linux.dev,
linux-kernel@...r.kernel.org, djakov@...nel.org
Subject: Re: [RFC] mm: Allow ZONE_DMA32 to be disabled via kernel command line
On 1/26/23 10:51, Dave Hansen wrote:
> On 1/26/23 08:43, Georgi Djakov wrote:
>> From: Chris Goldsworthy <quic_cgoldswo@...cinc.com>
>> +static int __init early_disable_dma32(char *buf)
>> +{
>> + if (!buf)
>> + return -EINVAL;
>> +
>> + if (!strcmp(buf, "on"))
>> + disable_dma32 = true;
>> +
>> + return 0;
>> +}
>> +early_param("disable_dma32", early_disable_dma32);
>
> Ick. Is there no way to do this other than a cross-arch copy/paste?
I think that using __setup() instead of early_param() would allow that.
--
~Randy
Powered by blists - more mailing lists