[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170410204933.GZ4372@olila.local.net-space.pl>
Date: Mon, 10 Apr 2017 22:49:33 +0200
From: Daniel Kiper <daniel.kiper@...cle.com>
To: Petr Tesarik <ptesarik@...e.com>
Cc: jgross@...e.com, konrad.wilk@...cle.com,
boris.ostrovsky@...cle.com, xen-devel@...ts.xenproject.org,
eric.devolder@...cle.com, dkiper@...-space.pl,
andrew.cooper3@...rix.com, linux-kernel@...r.kernel.org
Subject: Re: [Xen-devel] [PATCH v2] xen, kdump: handle pv domain in
paddr_vmcoreinfo_note()
On Fri, Apr 07, 2017 at 11:16:22AM +0200, Petr Tesarik wrote:
> On Wed, 5 Apr 2017 13:13:00 +0200
> Petr Tesarik <ptesarik@...e.com> wrote:
>
> > On Tue, 4 Apr 2017 12:42:53 -0700 (PDT)
> > Daniel Kiper <daniel.kiper@...cle.com> wrote:
> >
> >[...]
> > > So, if Petr did relevant tests that is nice. However, then, IMO, this
> > > patch begs Petr Tested-by.
> >
> > Actually, I tested with this patch applied on top of kernel 4.4 (SLES
> > 12 SP2). It matches what traditional Xen had always done, so I am quite
> > confident it will work with a later kernel, but to give my Tested-by,
> > let me first re-run the test on master, hopefully until today EOB.
>
> It took me much longer than anticipated (I had some trouble setting up
> the host again), but I can confirm that the patch works as expected on
No problem. I know how it works.
> top of 4.11-rc5.
Great!
> Without the patch, makedumpfile in the crash kernel complains:
>
> /proc/vmcore doesn't contain vmcoreinfo.
Though, I would like to ask you to do crash tool tests too.
Could you do that?
> With the patch applied, dumping still fails later because of an
> unrelated bug in makedumpfile, but I was able to extract the kernel
> message buffer with "makedumpfile --dump-dmesg". This already confirms
> VMCOREINFO presence and usability.
Is it Xen specific issue or more generic one?
Daniel
Powered by blists - more mailing lists