[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <F2CBF3009FA73547804AE4C663CAB28E3A0FB527@shsmsx102.ccr.corp.intel.com>
Date: Tue, 25 Oct 2016 01:24:47 +0000
From: "Li, Liang Z" <liang.z.li@...el.com>
To: "Hansen, Dave" <dave.hansen@...el.com>,
"mst@...hat.com" <mst@...hat.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"qemu-devel@...gnu.org" <qemu-devel@...gnu.org>,
"quintela@...hat.com" <quintela@...hat.com>,
"dgilbert@...hat.com" <dgilbert@...hat.com>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"cornelia.huck@...ibm.com" <cornelia.huck@...ibm.com>,
"amit.shah@...hat.com" <amit.shah@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mgorman@...hsingularity.net>
Subject: RE: [RESEND PATCH v3 kernel 3/7] mm: add a function to get the max
pfn
> On 10/20/2016 11:24 PM, Liang Li wrote:
> > Expose the function to get the max pfn, so it can be used in the
> > virtio-balloon device driver. Simply include the 'linux/bootmem.h'
> > is not enough, if the device driver is built to a module, directly
> > refer the max_pfn lead to build failed.
>
> I'm not sure the rest of the set is worth reviewing. I think a lot of it will
> change pretty fundamentally once you have those improved data structures
> in place.
That's true. I will send out the v4 as soon as possible.
Liang
Powered by blists - more mailing lists