[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180410135429.d1aeeb91d7f2754ffe7fb80e@linux-foundation.org>
Date: Tue, 10 Apr 2018 13:54:29 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Wei Wang <wei.w.wang@...el.com>, virtio-dev@...ts.oasis-open.org,
linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org,
linux-mm@...ck.org, mhocko@...nel.org, pbonzini@...hat.com,
liliang.opensource@...il.com, yang.zhang.wz@...il.com,
quan.xu0@...il.com, nilal@...hat.com, riel@...hat.com,
huangzhichao@...wei.com
Subject: Re: [PATCH v29 1/4] mm: support reporting free page blocks
On Tue, 10 Apr 2018 21:19:31 +0300 "Michael S. Tsirkin" <mst@...hat.com> wrote:
>
> Andrew, were your questions answered? If yes could I bother you for an ack on this?
>
Still not very happy that readers are told that "this function may
sleep" when it clearly doesn't do so. If we wish to be able to change
it to sleep in the future then that should be mentioned. And even put a
might_sleep() in there, to catch people who didn't read the comments...
Otherwise it looks OK.
Powered by blists - more mailing lists