From: Robin Murphy <robin.murphy@arm.com>
To: Arnd Bergmann <arnd@arndb.de>, Arnd Bergmann <arnd@kernel.org>,
Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>
Cc: Mostafa Saleh <smostafa@google.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Rob Clark <robdclark@chromium.org>,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/io-pgtable-arm: dynamically allocate selftest device struct
Date: Fri, 11 Apr 2025 17:28:50 +0100 [thread overview]
Message-ID: <ab75a444-22a1-47f5-b3c0-253660395b5a@arm.com> (raw)
In-Reply-To: <9c010a5d-a2a7-4002-9411-58009c1a21c8@app.fastmail.com>
On 11/04/2025 2:44 pm, Arnd Bergmann wrote:
> On Fri, Apr 11, 2025, at 15:19, Robin Murphy wrote:
>> On 11/04/2025 1:54 pm, Arnd Bergmann wrote:
>>> @@ -1433,15 +1434,17 @@ static int __init arm_lpae_do_selftests(void)
>>> };
>>>
>>> int i, j, k, pass = 0, fail = 0;
>>> - struct device dev;
>>
>> Could we not simply make this static? Per the comment it's only here to
>> serve a NUMA node lookup buried deep in the pagetable allocator (TBH my
>> first thought was to just put an int on the stack and contrive a pointer
>> as the inverse of dev_to_node(), but I decided that would probably be
>> too contentious...)
>
> A static device would work here, but that has other (small)
> downsides:
>
> - static devices are discouraged for any real purpose because
> of the problematic lifetime rules. I think Greg would still
> want to eliminate these entirely.
>
> - there is slightly more memory usage: the __init function
> gets eliminated after boot, while a static allocation says
> around. It could perhaps be made __initdata.
>
> - If we ever need anything beyond the NUMA node from it, the
> dynamic allocation is probably close enough to make that
> work.
>
>>> + struct platform_device *pdev;
>>> struct io_pgtable_cfg cfg = {
>>> .tlb = &dummy_tlb_ops,
>>> .coherent_walk = true,
>>> - .iommu_dev = &dev,
>>> };
>>>
>>> - /* __arm_lpae_alloc_pages() merely needs dev_to_node() to work */
>>> - set_dev_node(&dev, NUMA_NO_NODE);
>>> + pdev = platform_device_alloc("io-pgtable-test", 0);
>>
>> Otherwise, this would seem to be another perfect case for the new
>> faux_device.
>
> Good point, that is clearly better than platform_device in this
> case. Shall I send a new version with that?
Sure, I'm happy to consciously err on the side of caution and
robustness, just making sure :)
Thanks,
Robin.
prev parent reply other threads:[~2025-04-11 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 12:54 Arnd Bergmann
2025-04-11 13:19 ` Robin Murphy
2025-04-11 13:44 ` Arnd Bergmann
2025-04-11 16:28 ` Robin Murphy [this message]
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=ab75a444-22a1-47f5-b3c0-253660395b5a@arm.com \
--to=robin.murphy@arm.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=smostafa@google.com \
--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®