All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: kexec@lists.infradead.org, Keir Fraser <keir@xen.org>,
	David Vrabel <david.vrabel@citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xen.org
Subject: Re: [Xen-devel] [PATCHv10 0/9] Xen: extend kexec hypercall for use with pv-ops kernels
Date: Fri, 8 Nov 2013 14:01:59 +0000	[thread overview]
Message-ID: <527CEED7.4040807@citrix.com> (raw)
In-Reply-To: <20131108134829.GE11159@olila.local.net-space.pl>

On 08/11/13 13:48, Daniel Kiper wrote:
> On Fri, Nov 08, 2013 at 01:13:59PM +0000, David Vrabel wrote:
>> Keir,
>>
>> Sorry, forgot to CC you on this series.
>>
>> Can we have your opinion on whether this kexec series can be merged?
>> And if not, what further work and/or testing is required?
>>
>> On 07/11/13 21:16, Daniel Kiper wrote:
>>> On Wed, Nov 06, 2013 at 02:49:37PM +0000, David Vrabel wrote:
>>>> The series (for Xen 4.4) improves the kexec hypercall by making Xen
>>>> responsible for loading and relocating the image.  This allows kexec
>>>> to be usable by pv-ops kernels and should allow kexec to be usable
>>>> from a HVM or PVH privileged domain.
>>>>
>>>> I have now tested this with a Linux kernel image using the VGA console
>>>> which was what was causing problems in v9 (this turned out to be a
>>>> kexec-tools bug).
>>>>
>>>> The required patch series for kexec-tools will be posted shortly and
>>>> are available from the xen-v7 branch of:
>>> In general it works. However, quite often I am not able to execute panic
>>> kernel. Machine hangs with following message:
>> I cannot reproduce any failures, neither on my dev box nor on any of the
>> automated XenServer tests that run on a range of different hardware
>> platforms.  I find kexec to be very reliable and an earlier version of
>> this series has been in production within XenServer for a while now and
>> has seen real use in the field.
>>
>> None of the issues reported so far have been regressions but failures in
>> specific uses of the new support for pv-ops kernels.
>>
>> I really can't see how I can do anything else to make this series
>> acceptable for merging.
> I think that in general it is OK. However, we must solve discovered
> issues or confirm that it is not a problem of current implementation.
> That is all. I hope that we finally do that next week (FYI, Monday
> is public holiday in Poland).

What outstanding issues do you think are present then?

~Andrew

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  parent reply	other threads:[~2013-11-08 14:02 UTC|newest]

Thread overview: 99+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 14:49 [PATCHv10 0/9] Xen: extend kexec hypercall for use with pv-ops kernels David Vrabel
2013-11-06 14:49 ` [PATCH 1/9] x86: give FIX_EFI_MPF its own fixmap entry David Vrabel
2013-11-06 14:49 ` David Vrabel
2013-11-06 18:49   ` Don Slutz
2013-11-06 18:49   ` [Xen-devel] " Don Slutz
2013-11-06 14:49 ` [PATCH 2/9] kexec: add public interface for improved load/unload sub-ops David Vrabel
2013-11-07 20:38   ` Don Slutz
2013-11-07 20:38   ` Don Slutz
2013-11-06 14:49 ` David Vrabel
2013-11-06 14:49 ` [PATCH 3/9] kexec: add infrastructure for handling kexec images David Vrabel
2013-11-06 14:49 ` David Vrabel
2013-11-07 20:40   ` [Xen-devel] " Don Slutz
2013-11-07 23:51     ` Don Slutz
2013-11-07 23:51       ` Don Slutz
2013-11-07 20:40   ` Don Slutz
2013-11-08 12:50   ` [PATCHv11 " David Vrabel
2013-11-11 14:37     ` Don Slutz
2013-11-15 14:35     ` Jan Beulich
2013-11-15 18:31       ` David Vrabel
2013-11-18  8:07         ` Jan Beulich
2013-11-18 11:04           ` David Vrabel
2013-11-18 11:34             ` Jan Beulich
2013-11-18 12:25               ` Daniel Kiper
2013-11-18 12:53                 ` Jan Beulich
2013-11-18 13:24                   ` Daniel Kiper
2013-11-18 13:43                     ` Jan Beulich
2013-11-18 14:23                       ` Daniel Kiper
2013-11-18 15:24                         ` Jan Beulich
2013-11-18 21:50                           ` Daniel Kiper
2013-11-19 12:40                             ` Jan Beulich
2013-11-20 19:59                               ` Daniel Kiper
2013-11-21 16:19                                 ` Jan Beulich
2013-11-18 11:43             ` Daniel Kiper
2013-11-06 14:49 ` [PATCH 4/9] kexec: extend hypercall with improved load/unload ops David Vrabel
2013-11-06 14:49   ` David Vrabel
2013-11-07 20:56   ` [Xen-devel] " Don Slutz
2013-11-07 20:56     ` Don Slutz
2013-11-06 14:49 ` [PATCH 5/9] xen: kexec crash image when dom0 crashes David Vrabel
2013-11-07 20:44   ` [Xen-devel] " Don Slutz
2013-11-07 20:44   ` Don Slutz
2013-11-06 14:49 ` David Vrabel
2013-11-06 14:49 ` [PATCH 6/9] libxc: add hypercall buffer arrays David Vrabel
2013-11-07 20:46   ` [Xen-devel] " Don Slutz
2013-11-07 20:46   ` Don Slutz
2013-11-06 14:49 ` David Vrabel
2013-11-06 14:49 ` [PATCH 7/9] libxc: add API for kexec hypercall David Vrabel
2013-11-06 14:49 ` David Vrabel
2013-11-07 20:48   ` Don Slutz
2013-11-07 20:48   ` Don Slutz
2013-11-06 14:49 ` [PATCH 8/9] x86: check kexec relocation code fits in a page David Vrabel
2013-11-06 18:51   ` Don Slutz
2013-11-06 18:51   ` [Xen-devel] " Don Slutz
2013-11-06 14:49 ` David Vrabel
2013-11-06 14:49 ` [PATCH 9/9] MAINTAINERS: Add KEXEC maintainer David Vrabel
2013-11-06 14:49 ` David Vrabel
2013-11-06 18:50   ` Don Slutz
2013-11-06 18:50   ` Don Slutz
2013-11-07 21:16 ` [PATCHv10 0/9] Xen: extend kexec hypercall for use with pv-ops kernels Daniel Kiper
2013-11-07 21:25   ` [Xen-devel] " Andrew Cooper
2013-11-07 21:41     ` Daniel Kiper
2013-11-07 21:57       ` Andrew Cooper
2013-11-07 21:57       ` [Xen-devel] " Andrew Cooper
2013-11-08 13:20       ` David Vrabel
2013-11-08 13:20       ` [Xen-devel] " David Vrabel
2013-11-07 21:41     ` Daniel Kiper
2013-11-07 21:25   ` Andrew Cooper
2013-11-08 13:13   ` David Vrabel
2013-11-08 13:13   ` David Vrabel
2013-11-08 13:19     ` Jan Beulich
2013-11-08 13:19     ` Jan Beulich
2013-11-08 14:01       ` Andrew Cooper
2013-11-08 14:01       ` [Xen-devel] " Andrew Cooper
2013-11-08 14:22         ` Don Slutz
2013-11-08 14:22         ` [Xen-devel] " Don Slutz
2013-11-08 14:36         ` Jan Beulich
2013-11-08 14:36         ` Jan Beulich
2013-11-08 15:15         ` Daniel Kiper
2013-11-08 15:15         ` [Xen-devel] " Daniel Kiper
2013-11-08 15:42           ` Konrad Rzeszutek Wilk
2013-11-08 16:28             ` Daniel Kiper
2013-11-08 16:28             ` [Xen-devel] " Daniel Kiper
2013-11-08 15:42           ` Konrad Rzeszutek Wilk
2013-11-08 15:48           ` [Xen-devel] " Andrew Cooper
2013-11-08 15:48           ` Andrew Cooper
2013-11-08 13:48     ` Daniel Kiper
2013-11-08 13:48     ` Daniel Kiper
2013-11-08 14:01       ` Andrew Cooper
2013-11-08 14:01       ` Andrew Cooper [this message]
2013-11-08 15:04     ` Daniel Kiper
2013-11-08 15:04     ` Daniel Kiper
2013-11-09 19:18   ` Daniel Kiper
2013-11-09 19:18   ` Daniel Kiper
2013-11-11 14:34     ` Don Slutz
2013-11-11 14:34     ` Don Slutz
2013-11-11 15:09     ` David Vrabel
2013-11-11 15:09     ` David Vrabel
2013-11-07 21:16 ` Daniel Kiper
2013-11-11 17:18 ` Keir Fraser
2013-11-11 17:18 ` [Xen-devel] " 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=527CEED7.4040807@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=daniel.kiper@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=kexec@lists.infradead.org \
    --cc=xen-devel@lists.xen.org \
    /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.