From: Dave Anderson <anderson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Daniel Kiper <daniel.kiper-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: olaf-QOLJcTWqO2uzQB+pC5nmwQ@public.gmane.org,
xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
konrad wilk <konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
andrew cooper3
<andrew.cooper3-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>,
ptesarik-AlSwsSmVLrQ@public.gmane.org,
jbeulich-IBi9RG/b67k@public.gmane.org,
kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
crash-utility-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH v2 0/6] crash: Bundle of fixes for Xen
Date: Fri, 10 Aug 2012 15:11:57 -0400 (EDT) [thread overview]
Message-ID: <1568927206.9177777.1344625917898.JavaMail.root@redhat.com> (raw)
In-Reply-To: <20120810132357.GA2576-UojuW/CpjwpdUOLzJiIvSsFoITBeLw/klGfBN0aaEZ+lPcVs/6D9LQ@public.gmane.org>
----- Original Message -----
> Hi,
>
> It looks that Xen support for crash have not been maintained
> since 2009. I am trying to fix this. Here it is bundle of fixes:
> - xen: Always calculate max_cpus value,
> - xen: Read only crash notes for onlined CPUs,
> - x86/xen: Read variables from dynamically allocated per_cpu data,
> - xen: Get idle data from alternative source,
> - xen: Read data correctly from dynamically allocated console ring, too
> (fixed in this release),
> - xen: Add support for 3 level P2M tree (new patch in this release).
>
> Daniel
>
Hi Daniel,
The original 5 updates specific to the Xen hypervisor look OK,
but new patch 6/6 is going to take some studying/testing to
alleviate my backwards-compatibility worries. Can I ask whether
you fully tested it with older 2-level P2M tree kernels?
Thanks,
Dave
next prev parent reply other threads:[~2012-08-10 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 13:23 [PATCH v2 0/6] crash: Bundle of fixes for Xen Daniel Kiper
[not found] ` <20120810132357.GA2576-UojuW/CpjwpdUOLzJiIvSsFoITBeLw/klGfBN0aaEZ+lPcVs/6D9LQ@public.gmane.org>
2012-08-10 19:11 ` Dave Anderson [this message]
[not found] ` <1568927206.9177777.1344625917898.JavaMail.root-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-13 7:37 ` Daniel Kiper
[not found] ` <20120813073754.GA2482-UojuW/CpjwpdUOLzJiIvSsFoITBeLw/klGfBN0aaEZ+lPcVs/6D9LQ@public.gmane.org>
2012-08-13 19:16 ` Dave Anderson
[not found] ` <1827880283.12350529.1344885413402.JavaMail.root-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-14 6:14 ` Daniel Kiper
[not found] ` <20120814061408.GA2471-UojuW/CpjwpdUOLzJiIvSsFoITBeLw/klGfBN0aaEZ+lPcVs/6D9LQ@public.gmane.org>
2012-08-14 14:04 ` Dave Anderson
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=1568927206.9177777.1344625917898.JavaMail.root@redhat.com \
--to=anderson-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=andrew.cooper3-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org \
--cc=crash-utility-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=daniel.kiper-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=jbeulich-IBi9RG/b67k@public.gmane.org \
--cc=kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=olaf-QOLJcTWqO2uzQB+pC5nmwQ@public.gmane.org \
--cc=ptesarik-AlSwsSmVLrQ@public.gmane.org \
--cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.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;
as well as URLs for NNTP newsgroup(s).