From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: if p2m_is_paging then p2m_mem_paging_populate
Date: Tue, 31 Aug 2010 22:32:26 +0200
Message-ID: <20100831203226.GA28275@aepfle.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Patrick Colp <pjcolp@cs.ubc.ca>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org


Patrick,

when should p2m_mem_paging_populate() get called?
Currently there is a mix of p2m_is_paged and p2m_is_paging in
xen-unstable. The latter would mean that any of the paging states will
reset the flag to p2m_ram_paging_in_start. Well, unless its
p2m_ram_paging_out which is checked in p2m_mem_paging_populate itself.

I could prepare a patch to convert all callers to if p2m_is_paged() then
p2m_mem_paging_populate().

My guess is that the busy loop I see in my testing is caused by some
race where p2mt is reset to p2m_ram_paging_in_start so that xen itself
doesnt make any progress after a while. I'm currently debug that sort of
hang.


Olaf