[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110526185045.GA3476@elte.hu>
Date: Thu, 26 May 2011 20:50:45 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Valdis.Kletnieks@...edu
Cc: Avi Kivity <avi@...hat.com>, James Morris <jmorris@...ei.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Kees Cook <kees.cook@...onical.com>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Will Drewry <wad@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>,
linux-kernel@...r.kernel.org, gnatapov@...hat.com,
Chris Wright <chrisw@...s-sol.org>,
Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: [PATCH 3/5] v2 seccomp_filters: Enable ftrace-based system call
filtering
* Valdis.Kletnieks@...edu <Valdis.Kletnieks@...edu> wrote:
> On Thu, 26 May 2011 20:36:35 +0200, Ingo Molnar said:
>
> > I suspect we are really offtopic here, but an initial rsync, then
> > stopping the guest, final rsync + restart the guest at the target
> > would work with minimal interruption.
>
> Actually, after you kick off the migrate, you really want to be
> tracking in real time what pages get dirtied while you're doing the
> initial copy, so that the second rsync doesn't have to walk through
> the file finding the differences. But that requires some extra
> instrumentation.
Yeah, and that's how socket based live migration works - it's
completely seemless.
But note that the rsync re-scan should not be an issue: both the
source and the target system will obviously have a *lot* more RAM
than the guest RAM image size.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists