From: Andrea Arcangeli <aarcange@redhat.com>
To: Dominik Dingel <dingel@linux.vnet.ibm.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
linux-s390@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Eric B Munson <emunson@akamai.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Mel Gorman <mgorman@suse.de>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Allow gmap fault to retry
Date: Mon, 4 Jan 2016 18:08:57 +0100 [thread overview]
Message-ID: <20160104170857.GA3702@redhat.com> (raw)
In-Reply-To: <1451906395-80878-1-git-send-email-dingel@linux.vnet.ibm.com>
On Mon, Jan 04, 2016 at 12:19:53PM +0100, Dominik Dingel wrote:
> Hello,
>
> sorry for the delay since the last version.
>
> During Jasons work with postcopy migration support for s390 a problem regarding
> gmap faults was discovered.
>
> The gmap code will call fixup_user_fault which will end up always in
> handle_mm_fault. Till now we never cared about retries, but as the userfaultfd
> code kind of relies on it. this needs some fix.
>
> This patchset does not take care of the futex code. I will now look closer at
> this.
>
> Thanks,
> Dominik
>
> v2 -> v3:
> - In case of retrying check vma again
> - Do the accounting of major/minor faults once
Reviewed-by: Andrea Arcangeli <aarcange@redhat.com>
>
> v1 -> v2:
> - Instread of passing the VM_FAULT_RETRY from fixup_user_fault we do retries
> within fixup_user_fault, like get_user_pages_locked do.
> - gmap code will now take retry if fixup_user_fault drops the lock.
>
> Dominik Dingel (2):
> mm: bring in additional flag for fixup_user_fault to signal unlock
> s390/mm: enable fixup_user_fault retrying
>
> arch/s390/mm/pgtable.c | 31 ++++++++++++++++++++++++++++---
> include/linux/mm.h | 5 +++--
> kernel/futex.c | 2 +-
> mm/gup.c | 30 +++++++++++++++++++++++++-----
> 4 files changed, 57 insertions(+), 11 deletions(-)
>
> --
> 2.3.0
>
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-01-04 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 11:19 [PATCH v3 0/2] Allow gmap fault to retry Dominik Dingel
2016-01-04 11:19 ` [PATCH 1/2] mm: bring in additional flag for fixup_user_fault to signal unlock Dominik Dingel
2016-01-04 11:19 ` [PATCH 2/2] s390/mm: enable fixup_user_fault retrying Dominik Dingel
2016-01-04 17:08 ` Andrea Arcangeli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160104170857.GA3702@redhat.com \
--to=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=dingel@linux.vnet.ibm.com \
--cc=emunson@akamai.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=pbonzini@redhat.com \
--cc=rientjes@google.com \
--cc=schwidefsky@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).