From: Gleb Natapov <gleb@kernel.org>
To: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: Andres Lagar-Cavilla <andreslc@google.com>,
Gleb Natapov <gleb@redhat.com>, Rik van Riel <riel@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@suse.de>,
Andy Lutomirski <luto@amacapital.net>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Sasha Levin <sasha.levin@oracle.com>,
Jianyu Zhan <nasa4836@gmail.com>,
Paul Cassella <cassella@cray.com>,
Hugh Dickins <hughd@google.com>,
Peter Feiner <pfeiner@google.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] kvm: Faults which trigger IO release the mmap_sem
Date: Wed, 17 Sep 2014 14:42:15 +0300 [thread overview]
Message-ID: <20140917114214.GB30733@minantech.com> (raw)
In-Reply-To: <20140917112713.GB1273@potion.brq.redhat.com>
On Wed, Sep 17, 2014 at 01:27:14PM +0200, Radim Krčmář wrote:
> 2014-09-17 13:26+0300, Gleb Natapov:
> > For async_pf_execute() you do not need to even retry. Next guest's page fault
> > will retry it for you.
>
> Wouldn't that be a waste of vmentries?
This is how it will work with or without this second gup. Page is not
mapped into a shadow page table on this path, it happens on a next fault.
--
Gleb.
--
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>
next prev parent reply other threads:[~2014-09-17 11:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 20:11 [PATCH] kvm: Faults which trigger IO release the mmap_sem Andres Lagar-Cavilla
2014-09-16 13:51 ` Paolo Bonzini
2014-09-16 16:52 ` Andres Lagar-Cavilla
2014-09-16 16:55 ` Andres Lagar-Cavilla
2014-09-16 18:29 ` Paolo Bonzini
2014-09-16 18:42 ` Andres Lagar-Cavilla
2014-09-17 7:43 ` Paolo Bonzini
2014-09-17 16:58 ` Andres Lagar-Cavilla
2014-09-17 20:01 ` Paolo Bonzini
2014-09-16 20:51 ` Radim Krčmář
2014-09-16 21:01 ` Andres Lagar-Cavilla
2014-09-16 22:34 ` Radim Krčmář
2014-09-17 4:15 ` Andres Lagar-Cavilla
2014-09-17 11:35 ` Radim Krčmář
2014-09-17 10:26 ` Gleb Natapov
2014-09-17 11:27 ` Radim Krčmář
2014-09-17 11:42 ` Gleb Natapov [this message]
2014-09-17 17:00 ` Andres Lagar-Cavilla
2014-09-17 17:08 ` Gleb Natapov
2014-09-17 17:13 ` Andres Lagar-Cavilla
2014-09-17 17:21 ` Gleb Natapov
2014-09-17 17:41 ` Andres Lagar-Cavilla
2014-09-17 17:51 ` [PATCH v2] " Andres Lagar-Cavilla
2014-09-18 0:29 ` Wanpeng Li
2014-09-18 6:13 ` Gleb Natapov
2014-09-19 0:32 ` Wanpeng Li
2014-09-19 3:58 ` Andres Lagar-Cavilla
2014-09-19 6:08 ` Paolo Bonzini
2014-09-22 20:49 ` Andres Lagar-Cavilla
2014-09-22 21:32 ` Paolo Bonzini
2014-09-22 21:53 ` Andrew Morton
2014-09-18 6:15 ` Gleb Natapov
2014-09-25 21:16 ` Andrea Arcangeli
2014-09-25 21:50 ` Andres Lagar-Cavilla
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=20140917114214.GB30733@minantech.com \
--to=gleb@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andreslc@google.com \
--cc=cassella@cray.com \
--cc=gleb@redhat.com \
--cc=hughd@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mgorman@suse.de \
--cc=nasa4836@gmail.com \
--cc=peterz@infradead.org \
--cc=pfeiner@google.com \
--cc=riel@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sasha.levin@oracle.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).