From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH v3] xen/hvm: add kexec/kdump support
Date: Mon, 1 Aug 2011 15:28:19 +0200 [thread overview]
Message-ID: <20110801132819.GA10226@aepfle.de> (raw)
In-Reply-To: <20110801124637.GA9564@aepfle.de>
On Mon, Aug 01, Olaf Hering wrote:
> - add xs_introduce() in xs_init() to shutdown all open watches that the
> previous kernel had registered. Without this change the kexec may
> crash due to unexpected watch events.
> This depends on a xenstored change which has to allow the XS_INTRODUCE
> from a guest.
> And this part may need more work because the xs_introduce may hang
> forever on an old dom0 tool stack
The hang I encountered last week was due to a bug in the new
xs_introduce() function. "iov[2].iov_len" was by accident written as
"iov[3].iov_len", which left the iov_len uninitialized. Then xenstored
got a huge iov_len, returned an error which the kernel received. But the
process_msg() did not wakeup read_reply() for some reason.
Today an unmodified sles11sp1 dom0 can boot a 3.0 kernel with the
kexec/kdump patch applied.
Olaf
prev parent reply other threads:[~2011-08-01 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 12:46 [PATCH v3] xen/hvm: add kexec/kdump support Olaf Hering
2011-08-01 13:28 ` Olaf Hering [this message]
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=20110801132819.GA10226@aepfle.de \
--to=olaf@aepfle.de \
--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.