From: Randy Dunlap <rdunlap@infradead.org>
To: Dave Hansen <dave.hansen@intel.com>,
Georgi Djakov <quic_c_gdjako@quicinc.com>,
catalin.marinas@arm.com, will@kernel.org
Cc: dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, hch@lst.de,
m.szyprowski@samsung.com, robin.murphy@arm.com,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, djakov@kernel.org
Subject: Re: [RFC] mm: Allow ZONE_DMA32 to be disabled via kernel command line
Date: Thu, 26 Jan 2023 16:57:18 -0800 [thread overview]
Message-ID: <70ab19eb-c41a-980d-46f6-2bb02163974e@infradead.org> (raw)
In-Reply-To: <dca84e05-e376-c593-74fa-37c58f30767a@intel.com>
On 1/26/23 10:51, Dave Hansen wrote:
> On 1/26/23 08:43, Georgi Djakov wrote:
>> From: Chris Goldsworthy <quic_cgoldswo@quicinc.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
next prev parent reply other threads:[~2023-01-27 0:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 16:43 Georgi Djakov
2023-01-26 18:51 ` Dave Hansen
2023-01-26 22:56 ` Georgi Djakov
2023-01-27 0:57 ` Randy Dunlap [this message]
2023-01-27 6:35 ` Christoph Hellwig
2023-01-27 6:52 ` H. Peter Anvin
2023-01-27 7:07 ` Christoph Hellwig
2023-01-26 19:15 ` Robin Murphy
2023-01-27 2:20 ` Chris Goldsworthy
[not found] ` <20230127085553.5120-1-hdanton@sina.com>
2023-02-01 4:09 ` Chris Goldsworthy
2023-01-30 5:26 ` kernel test robot
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=70ab19eb-c41a-980d-46f6-2bb02163974e@infradead.org \
--to=rdunlap@infradead.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=djakov@kernel.org \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=quic_c_gdjako@quicinc.com \
--cc=robin.murphy@arm.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
/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®