From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/8] Initial implementation of kdump for ARM
Date: Mon, 5 Jul 2010 19:14:21 +0100 [thread overview]
Message-ID: <20100705181421.GA27771@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4C31FC27.4010102@stericsson.com>
On Mon, Jul 05, 2010 at 05:37:11PM +0200, Per Fransson wrote:
> On 07/05/2010 04:19 PM, Russell King - ARM Linux wrote:
> > On Mon, Jul 05, 2010 at 04:05:56PM +0200, Per Fransson wrote:
> >> Well, I had another suggestion in my last mail.
> >
> > Which is going to need per-CPU type support in order to achieve. Do
> > we really want to implement relocate_new_kernel for each of the 24
> > CPU types which we currently support?
> >
>
> Perhaps not. Couldn't the variable delay be macrofied then, i.e. a
> macro like
>
> MMU_DISABLED_DELAY_AND_EXEC(<asm instr>)
>
> which would do nothing for an appropriate amount of time and put the
> instruction in the last MMU mapped slot?
There is no "appropriate amount of time" - some CPUs depend on many
effects that a "3 nops and you'll be fine" approach doesn't work.
Also, what about kernels that support multiple different CPU types.
next prev parent reply other threads:[~2010-07-05 18:14 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
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 [this message]
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=20100705181421.GA27771@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).