From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 6/6] arm: KVM: ARMv7 dirty page logging 2nd stage page fault
Date: Mon, 29 Sep 2014 15:35:09 +0200 [thread overview]
Message-ID: <20140929133509.GH3095@cbox> (raw)
In-Reply-To: <1411433690-8104-7-git-send-email-m.smarduch@samsung.com>
On Mon, Sep 22, 2014 at 05:54:50PM -0700, Mario Smarduch wrote:
> This patch adds support for handling 2nd stage page faults during migration,
> it disables faulting in huge pages, and dissolves huge pages to page tables.
> In case migration is canceled huge pages may be used again.
>
>
> Signed-off-by: Mario Smarduch <m.smarduch@samsung.com>
It seems here and in a bunch of the other patches you didn't apply my
Reviewed-by tags. Did you change the patches in other ways than
addressed by the review comments?
Thanks,
-Christoffer
next prev parent reply other threads:[~2014-09-29 13:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 0:54 [PATCH v11 0/6] arm: dirty page logging support for ARMv7 Mario Smarduch
2014-09-23 0:54 ` [PATCH v11 1/6] KVM: Add architecture-specific TLB flush implementations Mario Smarduch
2014-10-15 11:17 ` Alexander Graf
2014-09-23 0:54 ` [PATCH v11 2/6] KVM: Add generic implementation of kvm_vm_ioctl_get_dirty_log Mario Smarduch
2014-09-29 13:36 ` Christoffer Dall
2014-09-29 17:18 ` Cornelia Huck
2014-09-29 18:02 ` Mario Smarduch
2014-10-15 11:21 ` Alexander Graf
2014-09-23 0:54 ` [PATCH v11 3/6] arm: KVM: Add ARMv7 API to flush TLBs Mario Smarduch
2014-09-23 0:54 ` [PATCH v11 4/6] arm: KVM: Add initial dirty page locking infrastructure Mario Smarduch
2014-09-23 0:54 ` [PATCH v11 5/6] arm: KVM: dirty log read write protect support Mario Smarduch
2014-09-23 0:54 ` [PATCH v11 6/6] arm: KVM: ARMv7 dirty page logging 2nd stage page fault Mario Smarduch
2014-09-29 13:35 ` Christoffer Dall [this message]
2014-09-29 21:03 ` Mario Smarduch
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=20140929133509.GH3095@cbox \
--to=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).