From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Keir Fraser <keir.xen@gmail.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1 of 3] apic: record local apic state on boot
Date: Thu, 19 May 2011 10:26:05 -0400 [thread overview]
Message-ID: <20110519142604.GA9854@dumpdata.com> (raw)
In-Reply-To: <4DD4FBB3.6010908@citrix.com>
> evidence shows however that linux 2.6.32 kdump (and presumably
I would suggest you use the latest linux kernel (2.6.39) to
look at the kdump implementation, much fresher.
next prev parent reply other threads:[~2011-05-19 14:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 18:08 [PATCH 0 of 3] Fix kexec path in xen (take 2) Andrew Cooper
2011-05-18 18:08 ` [PATCH 1 of 3] apic: record local apic state on boot Andrew Cooper
2011-05-18 18:49 ` Konrad Rzeszutek Wilk
2011-05-18 20:27 ` Andrew Cooper
2011-05-18 20:43 ` Konrad Rzeszutek Wilk
2011-05-19 0:56 ` Tian, Kevin
2011-05-19 8:34 ` Ian Campbell
2011-05-19 16:21 ` Konrad Rzeszutek Wilk
2011-05-19 0:54 ` Tian, Kevin
2011-05-18 23:40 ` Keir Fraser
2011-05-19 11:14 ` Andrew Cooper
2011-05-19 14:26 ` Konrad Rzeszutek Wilk [this message]
2011-05-19 14:43 ` Andrew Cooper
2011-05-18 18:08 ` [PATCH 2 of 3] apic: remove 'enabled_via_apicbase' variable Andrew Cooper
2011-05-18 18:53 ` Konrad Rzeszutek Wilk
2011-05-18 20:35 ` Andrew Cooper
2011-05-18 20:45 ` Konrad Rzeszutek Wilk
2011-05-19 3:31 ` Tian, Kevin
2011-05-18 18:08 ` [PATCH 3 of 3] kexec: disable iommu jumping into the kdump kernel Andrew Cooper
2011-05-18 18:49 ` Konrad Rzeszutek Wilk
2011-05-18 20:48 ` Andrew Cooper
2011-05-18 20:57 ` Konrad Rzeszutek Wilk
2011-05-18 21:24 ` Andrew Cooper
2011-05-19 14:32 ` Konrad Rzeszutek Wilk
2011-05-20 0:33 ` Kay, Allen M
2011-05-20 21:55 ` Kay, Allen M
2011-05-18 18:39 ` [PATCH 0 of 3] Fix kexec path in xen (take 2) Konrad Rzeszutek Wilk
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=20110519142604.GA9854@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir.xen@gmail.com \
--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.