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] pv-on-hvm kexec, howto reregister timer interrupt

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] pv-on-hvm kexec, howto reregister timer interrupt
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Sat, 23 Jul 2011 10:55:06 +0100
Cc: Olaf Hering <olaf@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sat, 23 Jul 2011 02:56:07 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=QZM03o3rS4CzyMeCsRkXglX9cUxuB9QJhZE92J2eetQ=; b=WCmBZBmSqNyaRhZbX4ZIhcfiz01+d8IHpzHKHZEKNpbFCs2OsfopXCkcWrByKNB4fr 5Eo7GWLwf8/y8djeHPKPfEfgTy00K8STovu1eqXaypoOzNadOO7Ho2pLE76DKQwj1MwG 9IYwfx35dUVqyqq/lbiRxoU/nE9nnaj7EaseE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1311408105.4027.80.camel@xxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcxJHpl/lBnSEsrYRkWzvrJZYPLFFA==
Thread-topic: [Xen-devel] pv-on-hvm kexec, howto reregister timer interrupt
User-agent: Microsoft-Entourage/
On 23/07/2011 09:01, "Ian Campbell" <Ian.Campbell@xxxxxxxxxx> wrote:

>> Sounbds like it's simply some Linux-guest issue here to be untangled. All
>> Xen requires you to do is EVTCHNOP_close the old virq-evtchn binding.
> That might be tricky to do in the target kernel, which may not know what
> needs closing. There's EVTCHNOP_reset which looks like it would be a
> sensible thing to call early on in the target but seems like it would
> close to much -- e.g. the xenstore evtchn?

If you can't do it in the source kernel (e.g., because it's crashed) the
best bet is to call EVTCHN_status on every port to find the channels you
want to clobber. Which is what Olaf hacked up already I believe, just needs
integrating cleanly.

 -- Keir

Xen-devel mailing list