From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 4/4] add 2nd stage page fault handling during live migration
Date: Thu, 29 May 2014 10:42:06 +0200 [thread overview]
Message-ID: <20140529084206.GA61607@lvm> (raw)
In-Reply-To: <53862DF8.80709@samsung.com>
On Wed, May 28, 2014 at 11:42:00AM -0700, Mario Smarduch wrote:
>
> >emslot dirty_bitmap during and after write protect.
> >
> >>
> >> -Christoffer
>
> Regarding huge pud that's causing some design problems, should huge PUD
> pages be considered at all?
>
I'm not sure if there is any support for this on aarch64 or anyone
planning to work on this.
Steve?
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Mario Smarduch <m.smarduch@samsung.com>
Cc: kvm@vger.kernel.org, sungjinn.chung@samsung.com,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org,
Steve Capper <steve.capper@linaro.org>
Subject: Re: [PATCH v6 4/4] add 2nd stage page fault handling during live migration
Date: Thu, 29 May 2014 10:42:06 +0200 [thread overview]
Message-ID: <20140529084206.GA61607@lvm> (raw)
In-Reply-To: <53862DF8.80709@samsung.com>
On Wed, May 28, 2014 at 11:42:00AM -0700, Mario Smarduch wrote:
>
> >emslot dirty_bitmap during and after write protect.
> >
> >>
> >> -Christoffer
>
> Regarding huge pud that's causing some design problems, should huge PUD
> pages be considered at all?
>
I'm not sure if there is any support for this on aarch64 or anyone
planning to work on this.
Steve?
-Christoffer
next prev parent reply other threads:[~2014-05-29 8:42 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 18:27 [PATCH v6 0/4] live migration dirty bitmap support for ARMv7 Mario Smarduch
2014-05-15 18:27 ` Mario Smarduch
2014-05-15 18:27 ` [PATCH v6 1/4] add ARMv7 HYP API to flush VM TLBs without address param Mario Smarduch
2014-05-15 18:27 ` Mario Smarduch
2014-05-27 19:51 ` Christoffer Dall
2014-05-27 19:51 ` Christoffer Dall
2014-05-15 18:27 ` [PATCH v6 2/4] live migration support for initial write protect of VM Mario Smarduch
2014-05-15 18:27 ` Mario Smarduch
2014-05-27 19:58 ` Christoffer Dall
2014-05-27 19:58 ` Christoffer Dall
2014-05-27 20:15 ` Mario Smarduch
2014-05-27 20:15 ` Mario Smarduch
2014-05-27 20:20 ` Christoffer Dall
2014-05-27 20:20 ` Christoffer Dall
2014-05-15 18:27 ` [PATCH v6 3/4] live migration support for VM dirty log management Mario Smarduch
2014-05-15 18:27 ` Mario Smarduch
2014-05-27 20:12 ` Christoffer Dall
2014-05-27 20:12 ` Christoffer Dall
2014-05-27 21:55 ` Mario Smarduch
2014-05-27 21:55 ` Mario Smarduch
2014-05-28 9:08 ` Christoffer Dall
2014-05-28 9:08 ` Christoffer Dall
2014-05-28 17:59 ` Mario Smarduch
2014-05-28 17:59 ` Mario Smarduch
2014-05-15 18:27 ` [PATCH v6 4/4] add 2nd stage page fault handling during live migration Mario Smarduch
2014-05-15 18:27 ` Mario Smarduch
2014-05-27 20:19 ` Christoffer Dall
2014-05-27 20:19 ` Christoffer Dall
2014-05-28 1:30 ` Mario Smarduch
2014-05-28 1:30 ` Mario Smarduch
2014-05-28 8:09 ` Christoffer Dall
2014-05-28 8:09 ` Christoffer Dall
2014-05-28 17:55 ` Mario Smarduch
2014-05-28 17:55 ` Mario Smarduch
2014-05-28 18:42 ` Mario Smarduch
2014-05-28 18:42 ` Mario Smarduch
2014-05-29 2:02 ` Mario Smarduch
2014-05-29 2:02 ` Mario Smarduch
2014-05-29 8:42 ` Christoffer Dall [this message]
2014-05-29 8:42 ` Christoffer Dall
2014-05-29 8:51 ` Christoffer Dall
2014-05-29 8:51 ` Christoffer Dall
2014-05-29 17:08 ` Mario Smarduch
2014-05-29 17:08 ` Mario Smarduch
2014-05-29 17:57 ` Christoffer Dall
2014-05-29 17:57 ` Christoffer Dall
2014-05-29 19:10 ` Mario Smarduch
2014-05-29 19:10 ` Mario Smarduch
2014-05-15 18:51 ` [PATCH v6 0/4] live migration dirty bitmap support for ARMv7 Christoffer Dall
2014-05-15 18:51 ` Christoffer Dall
2014-05-15 22:53 ` Mario Smarduch
2014-05-15 22:53 ` 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=20140529084206.GA61607@lvm \
--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 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.