From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: olaf@aepfle.de, xen-devel@lists.xensource.com,
andrew cooper3 <andrew.cooper3@citrix.com>,
kexec@lists.infradead.org, Dave Anderson <anderson@redhat.com>,
crash-utility@redhat.com
Subject: Re: [PATCH 0/5] crash: Small bundle of fixes for Xen
Date: Thu, 5 Jul 2012 11:33:33 -0400 [thread overview]
Message-ID: <20120705153333.GA27568@phenom.dumpdata.com> (raw)
In-Reply-To: <20120705152950.GH2007@host-192-168-1-59.local.net-space.pl>
On Thu, Jul 05, 2012 at 05:29:50PM +0200, Daniel Kiper wrote:
> On Thu, Jul 05, 2012 at 11:15:29AM -0400, Dave Anderson wrote:
> >
> >
> > ----- 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 small
> > > 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.
> > >
> > > Daniel
> >
> > Daniel,
> >
> > Can you absolutely confirm that these changes are all backwards-compatible?
>
> I have not done tests with older versions of Xen. However,
> I made all patches with backward compatibility in mind. Anyway,
> If you wish I could do tests with let's say Xen Ver. 3.4
> and Xen Linux Kernel Ver. 2.6.18 at least.
I think Dave is worried about it breaking with the version that is bundled
with RHEL5U8?
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk-QHcLZuEGTsvQT0dZR+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,
andrew cooper3
<andrew.cooper3-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>,
kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Dave Anderson <anderson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
crash-utility-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH 0/5] crash: Small bundle of fixes for Xen
Date: Thu, 5 Jul 2012 11:33:33 -0400 [thread overview]
Message-ID: <20120705153333.GA27568@phenom.dumpdata.com> (raw)
In-Reply-To: <20120705152950.GH2007-UojuW/CpjwpdUOLzJiIvSsFoITBeLw/klGfBN0aaEZ+lPcVs/6D9LQ@public.gmane.org>
On Thu, Jul 05, 2012 at 05:29:50PM +0200, Daniel Kiper wrote:
> On Thu, Jul 05, 2012 at 11:15:29AM -0400, Dave Anderson wrote:
> >
> >
> > ----- 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 small
> > > 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.
> > >
> > > Daniel
> >
> > Daniel,
> >
> > Can you absolutely confirm that these changes are all backwards-compatible?
>
> I have not done tests with older versions of Xen. However,
> I made all patches with backward compatibility in mind. Anyway,
> If you wish I could do tests with let's say Xen Ver. 3.4
> and Xen Linux Kernel Ver. 2.6.18 at least.
I think Dave is worried about it breaking with the version that is bundled
with RHEL5U8?
next prev parent reply other threads:[~2012-07-05 15:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 14:58 [PATCH 0/5] crash: Small bundle of fixes for Xen Daniel Kiper
2012-07-05 14:58 ` Daniel Kiper
2012-07-05 15:00 ` [PATCH 1/5] xen: Always calculate max_cpus value Daniel Kiper
2012-07-05 15:00 ` Daniel Kiper
2012-07-05 15:56 ` [Xen-devel] " Jan Beulich
2012-07-05 15:56 ` Jan Beulich
2012-07-13 13:19 ` Daniel Kiper
2012-07-13 13:19 ` [Xen-devel] " Daniel Kiper
2012-07-13 14:51 ` Andrew Cooper
2012-07-13 14:51 ` Andrew Cooper
2012-07-05 15:01 ` [PATCH 2/5] xen: Read only crash notes for onlined CPUs Daniel Kiper
2012-07-05 15:01 ` Daniel Kiper
2012-07-05 15:02 ` [PATCH 3/5] x86/xen: Read variables from dynamically allocated per_cpu data Daniel Kiper
2012-07-05 15:02 ` Daniel Kiper
2012-07-05 15:03 ` [PATCH 4/5] xen: Get idle data from alternative source Daniel Kiper
2012-07-05 15:03 ` Daniel Kiper
2012-07-05 15:04 ` [PATCH 5/5] xen: Read data correctly from dynamically allocated console ring too Daniel Kiper
2012-07-05 15:04 ` Daniel Kiper
2012-07-05 15:15 ` [PATCH 0/5] crash: Small bundle of fixes for Xen Dave Anderson
2012-07-05 15:15 ` Dave Anderson
2012-07-05 15:29 ` Daniel Kiper
2012-07-05 15:29 ` Daniel Kiper
2012-07-05 15:33 ` Konrad Rzeszutek Wilk [this message]
2012-07-05 15:33 ` Konrad Rzeszutek Wilk
2012-07-05 17:06 ` Dave Anderson
2012-07-05 17:06 ` Dave Anderson
2012-07-05 19:20 ` Dave Anderson
2012-07-05 19:20 ` Dave Anderson
2012-07-05 15:39 ` Dave Anderson
2012-07-05 15:39 ` Dave Anderson
2012-07-05 15:51 ` Daniel Kiper
2012-07-05 15:51 ` Daniel Kiper
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=20120705153333.GA27568@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=anderson@redhat.com \
--cc=andrew.cooper3@citrix.com \
--cc=crash-utility@redhat.com \
--cc=daniel.kiper@oracle.com \
--cc=kexec@lists.infradead.org \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xensource.com \
/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.