[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrUvTC8DzYjv+bmScP7nDaBaZHkivAXmahC7zePzX3xypg@mail.gmail.com>
Date: Wed, 31 Aug 2016 08:08:10 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Dmitry Safonov <dsafonov@...tuozzo.com>
Cc: Dmitry Safonov <0x7f454c46@...il.com>,
Andy Lutomirski <luto@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Oleg Nesterov <oleg@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>, X86 ML <x86@...nel.org>,
Cyrill Gorcunov <gorcunov@...nvz.org>,
Pavel Emelyanov <xemul@...tuozzo.com>
Subject: Re: [PATCHv4 3/6] x86/arch_prctl/vdso: add ARCH_MAP_VDSO_*
On Wed, Aug 31, 2016 at 8:01 AM, Dmitry Safonov <dsafonov@...tuozzo.com> wrote:
> On 08/31/2016 05:56 PM, Andy Lutomirski wrote:
>>
>> On Wed, Aug 31, 2016 at 7:04 AM, Dmitry Safonov <0x7f454c46@...il.com>
>> wrote:
>>>
>>> Hi Andy,
>>> can I have your acks for 2-3 patches, or should I fix something else
>>> in those patches?
>>>
>>> 2016-08-31 16:59 GMT+03:00 Dmitry Safonov <dsafonov@...tuozzo.com>:
>>>>
>>>> Add API to change vdso blob type with arch_prctl.
>>>> As this is usefull only by needs of CRIU, expose
>>>> this interface under CONFIG_CHECKPOINT_RESTORE.
>>
>>
>>
>> I thought the vm_file stuff was still being iterated on. Did I
>> misunderstand?
>
>
> Yep, vm_file is being iterated, separately from vdso-map/compatible
> patches.
OK
--
Andy Lutomirski
AMA Capital Management, LLC
Powered by blists - more mailing lists