From: Daniel Kiper <daniel.kiper@oracle.com>
To: <jgross@suse.com>
Cc: <ptesarik@suse.com>, <konrad.wilk@oracle.com>,
<boris.ostrovsky@oracle.com>, <xen-devel@lists.xenproject.org>,
<eric.devolder@oracle.com>, <dkiper@net-space.pl>,
<andrew.cooper3@citrix.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH v2] xen, kdump: handle pv domain in paddr_vmcoreinfo_note()
Date: Tue, 4 Apr 2017 12:42:53 -0700 (PDT) [thread overview]
Message-ID: <0106a5b2-7c66-41bd-9a43-42974242b3af@default> (raw)
> On 03/04/17 14:42, Daniel Kiper wrote:
> > On Fri, Mar 31, 2017 at 12:14:38PM +0200, Juergen Gross wrote:
> >> For kdump to work correctly it needs the physical address of
> >> vmcoreinfo_note. When running as dom0 this means the virtual address
> >> has to be translated to the related machine address.
> >>
> >> paddr_vmcoreinfo_note() is meant to do the translation via
> >> __pa_symbol() only, but being attributed "weak" it can be replaced
> >> easily in Xen case.
> >>
> >> Signed-off-by: Juergen Gross <jgross@suse.com>
> >
> > Have you tested this patch with latest crash tool? Do dom0 and Xen
> > hypervisor analysis work without any issue (at least basic commands
> > like dmesg, bt, ps, etc.)? If yes for both you can add:
> >
> > Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
>
> This patch isn't for dump analysis, but for dump creation. Petr has
I know that. However, it may have impact on crash analysis. So,
I would expect that you or anybody else in your behalf will do
at least minimal crash tool tests.
> verified that the dump is in the expected format. Please ask Petr
> for further details, e.g. user side modifications being necessary.
So, if Petr did relevant tests that is nice. However, then, IMO, this
patch begs Petr Tested-by.
Daniel
next reply other threads:[~2017-04-04 19:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 19:42 Daniel Kiper [this message]
2017-04-05 11:13 ` Petr Tesarik
2017-04-07 9:16 ` Petr Tesarik
2017-04-10 20:49 ` Daniel Kiper
2017-04-11 10:49 ` Petr Tesarik
-- strict thread matches above, loose matches on Subject: below --
2017-03-31 10:14 [PATCH v2] xen,kdump: " Juergen Gross
2017-04-03 12:42 ` [Xen-devel] [PATCH v2] xen, kdump: " Daniel Kiper
2017-04-04 11:55 ` Juergen Gross
2017-04-11 12:45 ` Juergen Gross
2017-04-11 13:00 ` Daniel Kiper
2017-04-11 14:59 ` Petr Tesarik
2017-04-11 17:20 ` Daniel Kiper
2017-04-14 16:53 ` Petr Tesarik
2017-04-14 22:26 ` Daniel Kiper
2017-04-15 14:35 ` Petr Tesarik
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=0106a5b2-7c66-41bd-9a43-42974242b3af@default \
--to=daniel.kiper@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dkiper@net-space.pl \
--cc=eric.devolder@oracle.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ptesarik@suse.com \
--cc=xen-devel@lists.xenproject.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 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®