From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 07 Feb 2005 22:16:57 +0900 (JST) Message-Id: <20050207.221657.66177955.taka@valinux.co.jp> Subject: Re: migration cache, updated From: Hirokazu Takahashi In-Reply-To: <42014605.4060707@sgi.com> References: <41FE79EF.8040204@sgi.com> <20050131184422.GD15694@logos.cnet> <42014605.4060707@sgi.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: raybry@sgi.com Cc: marcelo.tosatti@cyclades.com, linux-mm@kvack.org, iwamoto@valinux.co.jp, haveblue@us.ibm.com, hugh@veritas.com List-ID: Hi Ray, > >>(This message comes from ia64_do_page_fault() and appears to because > >>handle_mm_fault() returned FAULT_OOM....) > >> > >>I haven't looked into this further, but was wondering if perhaps one of > >>you would understand why the migrate cache patch would fail in this way? > > > > > > I can't think of anything right now - probably do_wp_page() is returning FAULT_OOM, > > can you confirm that? > > > No, it doesn't appear to be do_wp_page(). It looks like get_swap_page() > returns FAULT_OOM followed by get_user_pages() returning FAULT_OOM. > For the page that causes the VM to kill the process, there is no return > from get_user_pages() that returns FAULT_OOM. Not sure yet what is going > on here. Is get_swap_page() typo of do_swap_page()? How did you make sure do_swap_page() returned VM_FAULT_OOM? I feel do_wp_page() might have returned VM_FAULT_OOM. Would you please insert printks into the code everywhere VM_FAULT_OOM is handled and let's see what's going on? Thanks, Hirokazu Takahashi. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org