From: Daniel Kiper <daniel.kiper@oracle.com>
To: Matt Wilson <msw@amazon.com>
Cc: Daniel Kiper <dkiper@net-space.pl>,
gregkh@linuxfoundation.org, abyde@acunu.com, brandon@ifup.org,
ebiederm@xmission.com, grzegorz.milos@gmail.com,
konrad.wilk@oracle.com, tim@acunu.com,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
xen-devel@lists.xensource.com, kexec@lists.infradead.org
Subject: Re: [PATCH] kexec/kdump implementation for Xen PV domU
Date: Tue, 30 Jul 2013 14:12:32 +0200 [thread overview]
Message-ID: <20130730121232.GB3712@debian70-amd64.local.net-space.pl> (raw)
In-Reply-To: <20130729214419.GA4239@u109add4315675089e695.ant.amazon.com>
On Mon, Jul 29, 2013 at 02:44:19PM -0700, Matt Wilson wrote:
> On Mon, Jul 29, 2013 at 07:15:43PM +0200, Daniel Kiper wrote:
> > Hi all,
> >
> > Here I am sending as attachments patches enabling kexec/kdump
> > support in Xen PV domU. Only x84_64 architecture is supported.
> > There is no support for i386 but some code could be easily reused.
> > Here is a description of patches:
>
> [...]
>
> > - kexec-kernel-only_20121203.patch: this patch fixes timer
> > issue on Amazon EC2 machines.
>
> Hi Daniel,
>
> Do you know the cause of this issue? Does it have something to do with
> singleshot timer migration when offlining/onlining SMP CPUs?
Sadly, no. I was not able to replicate this on my machines (I did test
on Xen 4.1). However, as I saw this issue appears on Xen 3.4 and 4.0
(IIRC version numbers used on your machines). Additionally, it does not
depend on CPU models. And it appears quite often but not always.
Maybe it is linked with singleshot timer migration.
Daniel
prev parent reply other threads:[~2013-07-30 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 17:15 Daniel Kiper
2013-07-29 17:42 ` Greg KH
2013-07-29 21:44 ` Matt Wilson
2013-07-30 12:12 ` Daniel Kiper [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=20130730121232.GB3712@debian70-amd64.local.net-space.pl \
--to=daniel.kiper@oracle.com \
--cc=abyde@acunu.com \
--cc=brandon@ifup.org \
--cc=dkiper@net-space.pl \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=grzegorz.milos@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=msw@amazon.com \
--cc=tim@acunu.com \
--cc=virtualization@lists.linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®