[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200604150643.GA29193@infradead.org>
Date: Thu, 4 Jun 2020 08:06:43 -0700
From: Christoph Hellwig <hch@...radead.org>
To: David Hildenbrand <david@...hat.com>
Cc: Miles Chen <miles.chen@...iatek.com>, wsd_upstream@...iatek.com,
Joerg Roedel <joro@...tes.org>, linux-kernel@...r.kernel.org,
Chao Hao <chao.hao@...iatek.com>,
iommu@...ts.linux-foundation.org,
linux-mediatek@...ts.infradead.org, Yong Wu <yong.wu@...iatek.com>,
Matthias Brugger <matthias.bgg@...il.com>,
yingjoe.chen@...iatek.com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] iommu/mediatek: Use totalram_pages to setup enable_4GB
On Thu, Jun 04, 2020 at 01:32:40PM +0200, David Hildenbrand wrote:
> Just a thought: If memory hotplug is applicable as well, you might
> either want to always assume data->enable_4GB, or handle memory hotplug
> events from the memory notifier, when new memory gets onlined (not sure
> how tricky that is).
We probably want a highest_pfn_possible() or similar API instead of
having drivers poking into random VM internals.
Powered by blists - more mailing lists