All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: mtosatti@redhat.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] KVM: Enable async page fault processing.
Date: Thu, 24 Mar 2011 15:23:37 +0200	[thread overview]
Message-ID: <4D8B45D9.10400@redhat.com> (raw)
In-Reply-To: <20110324122206.GE32408@redhat.com>

On 03/24/2011 02:22 PM, Gleb Natapov wrote:
> On Tue, Feb 01, 2011 at 01:21:47PM +0200, Gleb Natapov wrote:
> >  If asynchronous hva_to_pfn() is requested call GUP with FOLL_NOWAIT to
> >  avoid sleeping on IO. Check for hwpoison is done at the same time,
> >  otherwise check_user_page_hwpoison() will call GUP again and will put
> >  vcpu to sleep.
> >
> FOLL_NOWAIT is now in Linus tree, so this patch can be applied now. I
> verified that it still applies and works.

Thanks, applied and queued for 2.6.39.

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: mtosatti@redhat.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] KVM: Enable async page fault processing.
Date: Thu, 24 Mar 2011 15:23:37 +0200	[thread overview]
Message-ID: <4D8B45D9.10400@redhat.com> (raw)
In-Reply-To: <20110324122206.GE32408@redhat.com>

On 03/24/2011 02:22 PM, Gleb Natapov wrote:
> On Tue, Feb 01, 2011 at 01:21:47PM +0200, Gleb Natapov wrote:
> >  If asynchronous hva_to_pfn() is requested call GUP with FOLL_NOWAIT to
> >  avoid sleeping on IO. Check for hwpoison is done at the same time,
> >  otherwise check_user_page_hwpoison() will call GUP again and will put
> >  vcpu to sleep.
> >
> FOLL_NOWAIT is now in Linus tree, so this patch can be applied now. I
> verified that it still applies and works.

Thanks, applied and queued for 2.6.39.

-- 
error compiling committee.c: too many arguments to function

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-03-24 13:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 11:21 [PATCH 0/2] KVM: enable asynchronous page faults Gleb Natapov
2011-02-01 11:21 ` Gleb Natapov
2011-02-01 11:21 ` [PATCH 1/2] Allow GUP to fail instead of waiting on a page Gleb Natapov
2011-02-01 11:21   ` Gleb Natapov
2011-02-01 16:48   ` Rik van Riel
2011-02-01 16:48     ` Rik van Riel
2011-02-02  0:42   ` Andrew Morton
2011-02-02  0:42     ` Andrew Morton
2011-02-02 13:31     ` Gleb Natapov
2011-02-02 13:31       ` Gleb Natapov
2011-02-02 19:37       ` Andrew Morton
2011-02-02 19:37         ` Andrew Morton
2011-02-01 11:21 ` [PATCH 2/2] KVM: Enable async page fault processing Gleb Natapov
2011-02-01 11:21   ` Gleb Natapov
2011-02-22  8:38   ` Lai Jiangshan
2011-02-22  8:38     ` Lai Jiangshan
2011-03-24 12:22   ` Gleb Natapov
2011-03-24 12:22     ` Gleb Natapov
2011-03-24 13:23     ` Avi Kivity [this message]
2011-03-24 13:23       ` Avi Kivity

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=4D8B45D9.10400@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mtosatti@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.