From: "H. Peter Anvin" <hpa@zytor.com>
To: Jingbai Ma <jingbai.ma@hp.com>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
"Mitchell, Lisa (MCLinux in Fort Collins)" <lisa.mitchell@hp.com>,
mingo@redhat.com, kumagai-atsushi@mxc.nes.nec.co.jp,
ebiederm@xmission.com, yinghai@kernel.org,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [RFC PATCH 0/5] crash dump bitmap: scan memory pages in kernel to speedup kernel dump process
Date: Fri, 08 Mar 2013 02:33:35 -0800 [thread overview]
Message-ID: <5139BE7F.5020905@zytor.com> (raw)
In-Reply-To: <5139B827.3050500@hp.com>
On 03/08/2013 02:06 AM, Jingbai Ma wrote:
>
> Kernel do have some abilities that user space haven't. It's possible to
> map whole memory space of the first kernel into user space on the second
> kernel. But the user space code has to re-implement some parts of the
> kernel memory management system again. And worse, it's architecture
> dependent, more architectures supported, more codes have to be
> implemented. All implementation in user space must be sync to kernel
> implementation. It's may called "flexibility", but it's painful to
> maintain the codes.
>
What? You are basically talking about /dev/mem... there is nothing
particularly magic about it at all.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-03-08 10:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 14:58 [RFC PATCH 0/5] crash dump bitmap: scan memory pages in kernel to speedup kernel dump process Jingbai Ma
2013-03-07 14:58 ` [RFC PATCH 1/5] crash dump bitmap: add a kernel config and help document Jingbai Ma
2013-03-07 14:58 ` [RFC PATCH 2/5] crash dump bitmap: init crash dump bitmap in kernel booting process Jingbai Ma
2013-03-07 14:58 ` [RFC PATCH 3/5] crash dump bitmap: scan memory pages in kernel crash process Jingbai Ma
2013-03-07 14:59 ` [RFC PATCH 4/5] crash dump bitmap: add a proc interface for crash dump bitmap Jingbai Ma
2013-03-07 14:59 ` [RFC PATCH 5/5] crash dump bitmap: workaround for kernel 3.9-rc1 kdump issue Jingbai Ma
2013-03-07 15:21 ` [RFC PATCH 0/5] crash dump bitmap: scan memory pages in kernel to speedup kernel dump process Vivek Goyal
2013-03-07 21:38 ` Yinghai Lu
2013-03-07 21:54 ` Eric W. Biederman
2013-03-08 15:52 ` Vivek Goyal
2013-03-08 16:19 ` Eric W. Biederman
2013-03-11 8:18 ` Jingbai Ma
2013-03-11 9:42 ` Eric W. Biederman
2013-03-12 10:05 ` Jingbai Ma
2013-03-12 19:48 ` Eric W. Biederman
2013-03-08 1:31 ` HATAYAMA Daisuke
2013-03-08 10:06 ` Jingbai Ma
2013-03-08 10:33 ` H. Peter Anvin [this message]
2013-03-08 13:31 ` Ma, Jingbai (Kingboard)
2013-03-08 16:13 ` Eric W. Biederman
2013-03-11 8:31 ` Jingbai Ma
2013-03-08 16:19 ` Vivek Goyal
2013-03-11 8:53 ` Jingbai Ma
2013-03-09 4:31 ` HATAYAMA Daisuke
2013-03-11 9:02 ` Jingbai Ma
2013-03-08 10:16 ` Jingbai Ma
-- strict thread matches above, loose matches on Subject: below --
2013-03-07 14:00 Jingbai Ma
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=5139BE7F.5020905@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=jingbai.ma@hp.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa.mitchell@hp.com \
--cc=mingo@redhat.com \
--cc=vgoyal@redhat.com \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox