[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190614064313.GM7246@lst.de>
Date: Fri, 14 Jun 2019 08:43:13 +0200
From: Christoph Hellwig <hch@....de>
To: Ira Weiny <ira.weiny@...el.com>
Cc: Jason Gunthorpe <jgg@...lanox.com>,
Ralph Campbell <rcampbell@...dia.com>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
"nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Jérôme Glisse <jglisse@...hat.com>,
Ben Skeggs <bskeggs@...hat.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH 18/22] mm: mark DEVICE_PUBLIC as broken
On Thu, Jun 13, 2019 at 05:43:15PM -0700, Ira Weiny wrote:
> <sigh> yes but the earlier patch:
>
> [PATCH 03/22] mm: remove hmm_devmem_add_resource
>
> Removes the only place type is set to MEMORY_DEVICE_PUBLIC.
>
> So I think it is ok. Frankly I was wondering if we should remove the public
> type altogether but conceptually it seems ok. But I don't see any users of it
> so... should we get rid of it in the code rather than turning the config off?
That was my original idea. But then again Jerome spent a lot of effort
putting hooks for it all over the mm and it would seem a little root
to just rip this out ASAP. I'll give it some more time, but it it doesn't
get used after a few more kernel releases we should nuke it.
Powered by blists - more mailing lists