From: Daniel Kiper <daniel.kiper@oracle.com>
To: Don Slutz <dslutz@verizon.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xen.org, kexec@lists.infradead.org,
crash-utility@redhat.com
Subject: Re: [PATCH 0/4] Enable use of crash on xen 4.4.0 vmcore
Date: Wed, 8 Jan 2014 21:16:59 +0100 [thread overview]
Message-ID: <20140108201659.GB3633@olila.local.net-space.pl> (raw)
In-Reply-To: <1388862686-1832-1-git-send-email-dslutz@verizon.com>
On Sat, Jan 04, 2014 at 02:11:22PM -0500, Don Slutz wrote:
> With the addition on PVH code to xen 4.4, domain.is_hvm no longer
> exists. This prevents crash from using a xen 4.4.0 vmcore.
>
> Patch 1 "fixes" this.
>
> Patch 2 is a minor fix in that outputing the offset in hex for
> domain_domain_flags is different.
>
> Patch 3 is a bug fix to get all "domain_flags" set, not just the 1st
> one found.
>
> Patch 4 is a quick way to add domain.guest_type support.
Sorry for late reply but I was on holiday.
Nice work. Thanks. I have done some tests with old
and new Xen versions and it looks that it works
without any issue.
Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
Tested-by: Daniel Kiper <daniel.kiper@oracle.com>
Daniel
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2014-01-08 20:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 19:11 [PATCH 0/4] Enable use of crash on xen 4.4.0 vmcore Don Slutz
2014-01-04 19:11 ` [PATCH 1/4] Make domian.is_hvm optional Don Slutz
2014-01-04 21:13 ` [Xen-devel] " Konrad Rzeszutek Wilk
2014-01-04 21:26 ` Don Slutz
2014-01-04 19:11 ` [PATCH 2/4] xen: Fix offset output to be decimal Don Slutz
2014-01-04 19:11 ` [PATCH 3/4] xen: set all domain_flags, not just the 1st Don Slutz
2014-01-04 19:11 ` [PATCH 4/4] Add basic domain.guest_type support Don Slutz
2014-01-06 17:05 ` [Crash-utility] [PATCH 0/4] Enable use of crash on xen 4.4.0 vmcore Dave Anderson
2014-01-06 19:45 ` Don Slutz
2014-01-06 20:28 ` Dave Anderson
2014-01-08 20:16 ` Daniel Kiper [this message]
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=20140108201659.GB3633@olila.local.net-space.pl \
--to=daniel.kiper@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=crash-utility@redhat.com \
--cc=dslutz@verizon.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox