From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Keir Fraser <keir.xen@gmail.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: pv-on-hvm kexec, howto reregister timer interrupt
Date: Sat, 23 Jul 2011 10:52:29 +0200 [thread overview]
Message-ID: <20110723085229.GA14838@aepfle.de> (raw)
In-Reply-To: <1311408105.4027.80.camel@dagon.hellion.org.uk>
On Sat, Jul 23, Ian Campbell wrote:
> On Sat, 2011-07-23 at 07:57 +0100, Keir Fraser wrote:
> > On 22/07/2011 19:49, "Olaf Hering" <olaf@aepfle.de> wrote:
> >
> > > What is the best way to reregister the timer interrupt in the kexec
> > > kernel in a pv-on-hvm guest? Right now the crash shown below happens
> > > because EVTCHNOP_bind_virq returns -EEXIST. Can the timer on the cpus be
> > > unregistered during shutdown? xen_teardown_timer() does not allow that
> > > for cpu #0. I added some silly loop which tries to match vcpu/cpu in
> > > bind_virq_to_irq() using EVTCHNOP_status to find the currently used port
> > > number. This helps and booting proceeds, but I feel that cant be the
> > > right approach.
> >
> > 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?
After some more poking around in the reboot code path I have figured it
out, a syscore_ops has to be registerd to shutdown the irqs.
I will post some patches for review.
Olaf
next prev parent reply other threads:[~2011-07-23 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 18:49 pv-on-hvm kexec, howto reregister timer interrupt Olaf Hering
2011-07-23 6:57 ` Keir Fraser
2011-07-23 8:01 ` Ian Campbell
2011-07-23 8:52 ` Olaf Hering [this message]
2011-07-23 9:55 ` Keir Fraser
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=20110723085229.GA14838@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=keir.xen@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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.