From: "H. Peter Anvin" <hpa@zytor.com>
To: "Zhang, Jun" <jun.zhang@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "x86@kernel.org" <x86@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Fleming, Matt" <matt.fleming@intel.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] To crash dump, we need keep other memory type except E820_RAM, because other type come from BIOS or firmware is used by other code(for example: PCI_MMCONFIG).
Date: Tue, 30 Oct 2012 19:46:56 -0700 [thread overview]
Message-ID: <50909120.3040101@zytor.com> (raw)
In-Reply-To: <88DC34334CA3444C85D647DBFA962C270FD7EAD3@SHSMSX102.ccr.corp.intel.com>
On 10/30/2012 06:26 PM, Zhang, Jun wrote:
> From aebc336baa7ec2d4ccb6f21166770c7d2ee26cba Mon Sep 17 00:00:00 2001
> From: jzha144 <jun.zhang@intel.com>
> Date: Wed, 31 Oct 2012 08:51:18 +0800
> Subject: [PATCH] To crash dump, we need keep other memory type except
> E820_RAM, because other type come from BIOS or firmware is
> used by other code(for example: PCI_MMCONFIG).
I'm sorry, I can't quite parse the description or the comment... could
you clarify it a bit? I think I know what you mean, but there is
clearly risk for misunderstandings.
-hpa
next prev parent reply other threads:[~2012-10-31 2:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 1:26 [PATCH] To crash dump, we need keep other memory type except E820_RAM, because other type come from BIOS or firmware is used by other code(for example: PCI_MMCONFIG) Zhang, Jun
2012-10-31 2:46 ` H. Peter Anvin [this message]
2012-10-31 3:39 ` Zhang, Jun
2012-10-31 4:38 ` H. Peter Anvin
2012-10-31 5:22 ` Zhang, Jun
2012-10-31 5:38 ` H. Peter Anvin
2012-11-01 2:15 ` Zhang, Jun
2012-11-01 4:20 ` H. Peter Anvin
2012-11-01 8:49 ` Zhang, Jun
2012-11-02 15:08 ` Paul Gortmaker
2012-11-02 16:37 ` H. Peter Anvin
2012-11-05 1:37 ` [PATCH] crash dump: don't delete non-E820_RAM during init Zhang, Jun
2012-11-05 2:39 ` H. Peter Anvin
2012-11-05 2:57 ` Zhang, Jun
2012-11-05 2:59 ` H. Peter Anvin
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=50909120.3040101@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=jun.zhang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 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.