From: Daniel Kiper <email@example.com> To: Petr Tesarik <firstname.lastname@example.org> Cc: Juergen Gross <email@example.com>, Daniel Kiper <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org Subject: Re: [Xen-devel] [PATCH v2] xen, kdump: handle pv domain in paddr_vmcoreinfo_note() Date: Sat, 15 Apr 2017 00:26:05 +0200 [thread overview] Message-ID: <20170414222605.GA16658@olila.local.net-space.pl> (raw) In-Reply-To: <email@example.com> On Fri, Apr 14, 2017 at 06:53:36PM +0200, Petr Tesarik wrote: > On Tue, 11 Apr 2017 19:20:08 +0200 > Daniel Kiper <firstname.lastname@example.org> wrote: > > On Tue, Apr 11, 2017 at 04:59:16PM +0200, Petr Tesarik wrote: > >[...] > > > Tested-by: Petr Tesarik <email@example.com> > > > > > > I copied the complete /proc/vmcore to a directory on disk. Exactly > > > as expected, crash works both without the patch and with the patch, as > > > it does not use VMCOREINFO at all (instead, crash obtains the > > > information from kernel debuginfo directly). > > > > Thanks for doing the tests. I suppose that you have tested HVM guests. > > Not really. I crashed Dom0, which is in turn sent to the hypervisor, so > the result is a complete host dump, including Xen hypervisor data and > all domains. OK. > > IIRC, PV guests are not supported by crash right now due to p2m VMA > > mapping. At least it was an issue some time ago. Is it still valid? > > Yes, this is correct. I tested this behaviour a few weeks ago. Thanks for update. > > Anyway, one guy in Oracle works on fix for that issue and I do review. > > We are going to post it in 2-3 weeks. > > All right. FYI I do not plan to put much effort into it, as my focus has OK. > 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? Daniel
next prev parent reply other threads:[~2017-04-14 22:26 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-03-31 10:14 [PATCH v2] xen,kdump: " 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 [this message] 2017-04-15 14:35 ` Petr Tesarik 2017-04-15 14:35 ` Petr Tesarik 2017-04-14 22:26 ` Daniel Kiper 2017-04-11 14:59 ` Petr Tesarik 2017-04-11 13:00 ` Daniel Kiper 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-10 20:49 ` Daniel Kiper 2017-04-11 10:49 ` 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=20170414222605.GA16658@olila.local.net-space.pl \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [Xen-devel] [PATCH v2] xen, kdump: handle pv domain in paddr_vmcoreinfo_note()' \ /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
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.