From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751053AbdGYJ3Y (ORCPT ); Tue, 25 Jul 2017 05:29:24 -0400 Received: from mga14.intel.com ([192.55.52.115]:26627 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750768AbdGYJ3X (ORCPT ); Tue, 25 Jul 2017 05:29:23 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.40,411,1496127600"; d="scan'208";a="291108089" Message-ID: <59771010.6080108@intel.com> Date: Tue, 25 Jul 2017 17:32:00 +0800 From: Wei Wang User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Michal Hocko CC: "Michael S. Tsirkin" , linux-kernel@vger.kernel.org, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, kvm@vger.kernel.org, linux-mm@kvack.org, david@redhat.com, cornelia.huck@de.ibm.com, akpm@linux-foundation.org, mgorman@techsingularity.net, aarcange@redhat.com, amit.shah@redhat.com, pbonzini@redhat.com, liliang.opensource@gmail.com, virtio-dev@lists.oasis-open.org, yang.zhang.wz@gmail.com, quan.xu@aliyun.com Subject: Re: [PATCH v12 6/8] mm: support reporting free page blocks References: <1499863221-16206-1-git-send-email-wei.w.wang@intel.com> <1499863221-16206-7-git-send-email-wei.w.wang@intel.com> <20170714123023.GA2624@dhcp22.suse.cz> <20170714181523-mutt-send-email-mst@kernel.org> <20170717152448.GN12888@dhcp22.suse.cz> <596D6E7E.4070700@intel.com> <20170719081311.GC26779@dhcp22.suse.cz> <596F4A0E.4010507@intel.com> <20170724090042.GF25221@dhcp22.suse.cz> In-Reply-To: <20170724090042.GF25221@dhcp22.suse.cz> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/24/2017 05:00 PM, Michal Hocko wrote: > On Wed 19-07-17 20:01:18, Wei Wang wrote: >> On 07/19/2017 04:13 PM, Michal Hocko wrote: > [... >>> All you should need is the check for the page reference count, no? I >>> assume you do some sort of pfn walk and so you should be able to get an >>> access to the struct page. >> Not necessarily - the guest struct page is not seen by the hypervisor. The >> hypervisor only gets those guest pfns which are hinted as unused. From the >> hypervisor (host) point of view, a guest physical address corresponds to a >> virtual address of a host process. So, once the hypervisor knows a guest >> physical page is unsued, it knows that the corresponding virtual memory of >> the process doesn't need to be transferred in the 1st round. > I am sorry, but I do not understand. Why cannot _guest_ simply check the > struct page ref count and send them to the hypervisor? Were you suggesting the following? 1) get a free page block from the page list using the API; 2) if page->ref_count == 0, send it to the hypervisor Btw, ref_count may also change at any time. > Is there any > documentation which describes the workflow or code which would use your > new API? > It's used in the balloon driver (patch 8). We don't have any docs yet, but I think the high level workflow is the two steps above. Best, Wei