All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Tesarik <ptesarik@suse.com>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: Juergen Gross <jgross@suse.com>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
	Daniel Kiper <dkiper@net-space.pl>
Subject: Re: [PATCH v2] xen, kdump: handle pv domain in paddr_vmcoreinfo_note()
Date: Sat, 15 Apr 2017 16:35:27 +0200	[thread overview]
Message-ID: <20170415163527.0a38cb16__39167.9591652521$1492267031$gmane$org@hananiah.suse.cz> (raw)
In-Reply-To: <20170414222605.GA16658@olila.local.net-space.pl>

On Sat, 15 Apr 2017 00:26:05 +0200
Daniel Kiper <daniel.kiper@oracle.com> wrote:

> On Fri, Apr 14, 2017 at 06:53:36PM +0200, Petr Tesarik wrote:
>[...]
> > shifted towards libkdumpfile (https://github.com/ptesarik/libkdumpfile),
> > and this library can open PV guest dump files without any issues.
> 
> Great! AIUI, it reminds my idea to make such think. However, I have not
> have time to make it happen. Is it based on makedumpfile or written from
> scratch? Do you plan support for Linux kernel dumps and/or Xen ones?

Some ideas are borrowed from existing tools (makedumpfile, crash). All
code is written from scratch, however.

The kdumpfile library itself is designed for use with any platform and
operating system. Xen is treated as just another type of operating
system. Based on which OS type is initialized, the library is able to
provide a hypervisor view or a Dom0 view.

There is another project led by Jeff Mahoney, which extends standard
gdb with semantic commands. This project supports only x86_64 Linux
right now. See https://github.com/jeffmahoney/crash-python.

Petr T

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-04-15 14:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 10:14 [PATCH v2] xen,kdump: handle pv domain in paddr_vmcoreinfo_note() Juergen Gross
2017-03-31 14:02 ` Boris Ostrovsky
2017-03-31 14:02   ` [PATCH v2] xen, kdump: " Boris Ostrovsky
2017-04-03 12:42 ` [Xen-devel] " Daniel Kiper
2017-04-03 12:42   ` Daniel Kiper
2017-04-04 11:55   ` [Xen-devel] " Juergen Gross
2017-04-04 11:55   ` Juergen Gross
2017-04-11 12:45   ` Juergen Gross
2017-04-11 12:45   ` [Xen-devel] " 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-11 17:20         ` [Xen-devel] " Daniel Kiper
2017-04-14 16:53           ` Petr Tesarik
2017-04-14 16:53           ` [Xen-devel] " Petr Tesarik
2017-04-14 22:26             ` Daniel Kiper
2017-04-15 14:35               ` Petr Tesarik
2017-04-15 14:35               ` Petr Tesarik [this message]
2017-04-14 22:26             ` Daniel Kiper
2017-04-11 14:59       ` Petr Tesarik
2017-04-11 13:00     ` Daniel Kiper
  -- strict thread matches above, loose matches on Subject: below --
2017-04-04 19:42 [Xen-devel] " Daniel Kiper
2017-04-05 11:13 ` Petr Tesarik
2017-04-07  9:16   ` Petr Tesarik
2017-04-07  9:16   ` [Xen-devel] " Petr Tesarik
2017-04-10 20:49     ` Daniel Kiper
2017-04-11 10:49       ` Petr Tesarik
2017-04-05 11:13 ` Petr Tesarik
2017-04-04 19:42 Daniel Kiper
2017-03-31 10:14 Juergen Gross

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='20170415163527.0a38cb16__39167.9591652521$1492267031$gmane$org@hananiah.suse.cz' \
    --to=ptesarik@suse.com \
    --cc=daniel.kiper@oracle.com \
    --cc=dkiper@net-space.pl \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.