[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190328002525.GA17122@richard>
Date: Thu, 28 Mar 2019 08:25:25 +0800
From: Wei Yang <richardw.yang@...ux.intel.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Wei Yang <richard.weiyang@...il.com>,
Wei Yang <richardw.yang@...ux.intel.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, dave.hansen@...ux.intel.com,
luto@...nel.org, peterz@...radead.or
Subject: Re: [PATCH 4/6] x86, mm: make split_mem_range() more easy to read
On Thu, Mar 28, 2019 at 01:16:08AM +0100, Thomas Gleixner wrote:
>Wei,
>
>On Wed, 27 Mar 2019, Wei Yang wrote:
>> On Sun, Mar 24, 2019 at 03:29:04PM +0100, Thomas Gleixner wrote:
>> >Note, it's a combo of changes (including your patch 1/6) and needs to be
>> >split up. It would be nice if you have time to split it up into separate
>> >patches, add proper changelogs and test the heck out of it on both 32 and
>> >64 bit. If you don't have time, please let me know.
>> >
>>
>> Thanks for your suggestions :-)
>>
>> Just get my head up, will try to understand the code and test on both
>> arch.
>>
>> BTW, do you have some suggestions in the test? Currently I just use
>> bootup test. Basicly I think this is fine to cover the cases. Maybe you
>> would have some better idea.
>
>This is about bootup in the first place. After that memory hotplug which
>you can emulate with qemu/kvm IIRC.
>
Ok, this is not difficult.
>The important part about testing is to have systems which expose a wide
>variety memory layouts.
>
May be I can add some test with nvdimm.
>Thanks,
>
> tglx
--
Wei Yang
Help you, Help me
Powered by blists - more mailing lists