[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220923144804.GA18477@lst.de>
Date: Fri, 23 Sep 2022 16:48:04 +0200
From: Christoph Hellwig <hch@....de>
To: Robin Murphy <robin.murphy@....com>
Cc: Nate Drude <nate.d@...iscite.com>, iommu@...ts.linux.dev,
Jonathan Corbet <corbet@....net>,
Christoph Hellwig <hch@....de>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Borislav Petkov <bp@...e.de>,
"Paul E. McKenney" <paulmck@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Neeraj Upadhyay <quic_neeraju@...cinc.com>,
Randy Dunlap <rdunlap@...radead.org>,
Damien Le Moal <damien.lemoal@...nsource.wdc.com>,
Muchun Song <songmuchun@...edance.com>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
eran.m@...iscite.com
Subject: Re: [PATCH] dma-contiguous: add optional cma_name for cma= kernel
parameter
On Tue, Sep 13, 2022 at 11:45:17AM +0100, Robin Murphy wrote:
> If userspace expects the CMA heap driver to expose a consistent name for
> CMA heaps, shouldn't it be the CMA heap driver's responsibility to expose a
> consistent name for CMA heaps? Tinkering with the core CMA code doesn't
> feel like the right approach.
Agreed. In fact I think exposing this name in a uapi seems like a really
bad idea that is asking for a lot of trouble.
Powered by blists - more mailing lists