From: per.xx.fransson@stericsson•com (Per Fransson)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 0/8] Initial implementation of kdump for ARM
Date: Mon, 5 Jul 2010 14:04:17 +0200 [thread overview]
Message-ID: <4C31CA41.6050700@stericsson.com> (raw)
In-Reply-To: <20100705113136.GB32178@gw.healthdatacare.com>
On 07/05/2010 01:31 PM, Mika Westerberg wrote:
> On Mon, Jul 05, 2010 at 12:34:15PM +0200, Per Fransson wrote:
>> But the identity mapping is only set up for user space part. It needs to
>> be set up around the code which turns off the MMU for the case when
>> there is no delay at all. And it would still be nice to not corrupt the
>> page table of the crashing context.
>
> Yeah, with the current version, user-space mappings of the crashing
> process are gone.
>
> If they are really needed, then maybe we could do similar than x86
> and set up temporary page tables and do the identity mapping there?
> This way the crashing process' page tables would remain untouched.
>
We could move the MMU disabling to the relocate_new_kernel() routine.
Before jumping there the two (if we are unlucky) page table entries (for
1 MB sections) that this routine occupies could be put into registers
and an identity mapping be set up for just those entries. Once we reach
relocate_new_kernel():
1) the MMU is turned off
2) relocate_new_kernel does it's stuff (not much if a crashkernel area
is used)
3) the entries are restored, once we are sure the disabling has taken effect
Regards,
Per
next prev parent reply other threads:[~2010-07-05 12:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 6:54 [PATCH v2 0/8] Initial implementation of kdump for ARM Mika Westerberg
2010-05-05 6:54 ` [PATCH v2 1/8] arm: kdump: reserve memory for crashkernel Mika Westerberg
2010-05-05 6:54 ` [PATCH v2 2/8] arm: kdump: implement crash_setup_regs() Mika Westerberg
2010-05-05 6:54 ` [PATCH v2 3/8] arm: kdump: implement machine_crash_shutdown() Mika Westerberg
2010-05-05 6:54 ` [PATCH v2 4/8] arm: kdump: skip indirection page when crashing Mika Westerberg
2010-05-05 6:54 ` [PATCH v2 5/8] arm: kdump: implement copy_oldmem_page() Mika Westerberg
2010-05-05 6:54 ` [PATCH v2 6/8] arm: allow passing an ELF64 header to elf_check_arch() Mika Westerberg
2010-05-10 11:20 ` Russell King - ARM Linux
2010-05-10 12:09 ` Mika Westerberg
2010-05-10 12:21 ` Russell King - ARM Linux
2010-05-11 7:17 ` Mika Westerberg
2010-07-16 8:14 ` Mika Westerberg
2010-08-25 2:40 ` Lei Wen
2010-08-25 12:29 ` Mika Westerberg
2010-05-05 6:54 ` [PATCH v2 7/8] arm: kdump: add support for elfcorehdr= parameter Mika Westerberg
2010-05-05 6:54 ` [PATCH v2 8/8] arm: kdump: add CONFIG_CRASH_DUMP Kconfig option Mika Westerberg
2010-05-25 8:19 ` [PATCH v2 0/8] Initial implementation of kdump for ARM Mika Westerberg
2010-06-11 6:36 ` Mika Westerberg
2010-07-02 12:48 ` Per Fransson
2010-07-05 8:28 ` Mika Westerberg
2010-07-05 10:01 ` Per Fransson
2010-07-05 10:18 ` Russell King - ARM Linux
2010-07-05 10:34 ` Per Fransson
2010-07-05 11:31 ` Mika Westerberg
2010-07-05 12:04 ` Per Fransson [this message]
2010-07-05 13:55 ` Russell King - ARM Linux
2010-07-05 14:05 ` Per Fransson
2010-07-05 14:19 ` Russell King - ARM Linux
2010-07-05 15:37 ` Per Fransson
2010-07-05 16:08 ` Nicolas Pitre
2010-07-05 18:14 ` Russell King - ARM Linux
2010-07-06 8:30 ` Per Fransson
2010-07-07 7:29 ` Mika Westerberg
2010-07-08 8:52 ` Per Fransson
2010-07-12 8:20 ` Mika Westerberg
2010-07-09 3:38 ` Simon Horman
2010-07-09 8:19 ` Per Fransson
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=4C31CA41.6050700@stericsson.com \
--to=per.xx.fransson@stericsson$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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