This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Trigger code in domU from dom0

To: "Christopher Head" <chead@xxxxxxxxx>
Subject: Re: [Xen-devel] Trigger code in domU from dom0
From: Asim <linkasim@xxxxxxxxx>
Date: Fri, 22 Aug 2008 17:02:48 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 22 Aug 2008 15:03:11 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=pEAj2Dtiqi7gEpqjUn0UpzfgkaDS/z8MuR19U13NHfE=; b=W9ueJ14GVsiHFPCBrD5X0nNAEiSpEeQpSpqF+UUlpJTHQEVTtU+wzpJycKTIAcuZXY vR1hnaCH2X6ikWs4SAgwcXFCuIp7a9+eveWdmEn8yfkHAvgKg404Jvxlo5/NRJJ0sJ8k m5YdnBgcqzgRGU1CeTFOtRh9NwhhgJqcTU6aQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=P8SI4SB1pDHBLVw9k04V5SsuXxy0BGD5aoMT+08TwYn4UL63bnLf+NvogVSIEievGp /XnDHmqBNuklD+Z/Cl925Nm6IQNbjZSmyeqWoL9FDT0GUbfY+vGTDA1KVWTyWSX8Mw9t C/kPQVf68bkXziOMYWNv0GTyZn7mnw0lcfqq8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48AE3CD4.4030006@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <7ef321c10808211607j2d561064rfdcbd56aee589b66@xxxxxxxxxxxxxx> <48AE2AA4.9000104@xxxxxxxxx> <7ef321c10808212014n1db69d6ej124a13431ab13bfb@xxxxxxxxxxxxxx> <48AE3CD4.4030006@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thanks a lot Chris -- I can see it working fine. I have placed my
calls after the hypercall in take_machine_down in
linux/drivers/xen/core/machine_reboot.c (if suspend is successful) and
it looks to be working good.

Thanks again.


On 8/21/08, Christopher Head <chead@xxxxxxxxx> wrote:
> Hash: SHA1
> As far as live migration, this should work perfectly as long as you want
> your code to run **after** migration and not before. Live migration
> differs from regular migration only in that the tools copy a pile of
> memory pages without suspending the domain (meaning domU doesn't know
> when this starts happening), then suspend the domain and copy the last
> few pages. The event channel (or xenstore) mechanism used to trigger the
> suspend is the same, though, meaning you can hook your code in and be
> notified either between the mass copying and the copying of the last few
> pages (before the hypercall), or after all migration is done (after the
> hypercall).
> I didn't see any documentation on the code, I just browsed the source.
> For my purposes I'm not so much interested in IRQs, I'm more interested
> in running before userspace gets a chance to run - so I'm not sure about
> what you need for your project.
> Chris
> Asim wrote:
> | Thanks a lot Chris for the response. I have some followup questions:-
> |
> | 1. Does this hold for "live" migration as well?
> |
> | 2. I want to run my code when all devices/irqs are available. The
> | post_suspend looks like a good place to me. Did you get this
> | information via mere source code browsing or there is a reference to
> | it. It would be great for me to know where this is in migration stage
> | in terms of dom0 - Is it after dom0 declared migration finished?
> |
> | 3. Thanks a lot for your help.
> |
> Version: GnuPG v2.0.9 (GNU/Linux)
> Comment: GnuPT 2.7.2
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> DAcAnR9D4LweqxryduJdpLRheROVqFEO
> =8mEz

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>