From: Wang Nan <wangnan0@huawei.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Geng Hui <hui.geng@huawei.com>,
linux-mm@kvack.org, Eric Biederman <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] ARM: kexec: copying code to ioremapped area
Date: Thu, 23 Jan 2014 10:16:37 +0800 [thread overview]
Message-ID: <52E07B85.6030709@huawei.com> (raw)
In-Reply-To: <20140122132734.GB15937@n2100.arm.linux.org.uk>
On 2014/1/22 21:27, Russell King - ARM Linux wrote:
> On Wed, Jan 22, 2014 at 07:25:15PM +0800, Wang Nan wrote:
>> ARM's kdump is actually corrupted (at least for omap4460), mainly because of
>> cache problem: flush_icache_range can't reliably ensure the copied data
>> correctly goes into RAM.
>
> Quite right too. You're mistake here is thinking that flush_icache_range()
> should push it to RAM. That's incorrect.
>
> flush_icache_range() is there to deal with such things as loadable modules
> and self modifying code, where the MMU is not being turned off. Hence, it
> only flushes to the point of coherency between the I and D caches, and
> any further levels of cache between that point and memory are not touched.
> Why should it touch any more levels - it's not the function's purpose.
>
>> After mmu turned off and jump to the trampoline, kexec always failed due
>> to random undef instructions.
>
> We already have code in the kernel which deals with shutting the MMU off.
> An instance of how this can be done is illustrated in the soft_restart()
> code path, and kexec already uses this.
>
> One of the first things soft_restart() does is turn off the outer cache -
> which OMAP4 does have, but this can only be done if there is a single CPU
> running. If there's multiple CPUs running, then the outer cache can't be
> disabled, and that's the most likely cause of the problem you're seeing.
>
You are right, commit b25f3e1c (OMAP4/highbank: Flush L2 cache before disabling)
solves my problem, it flushes outer cache before disabling. I have tested it in
UP and SMP situations and it works (actually, omap4 has not ready to support kexec
in SMP case, I insert an empty cpu_kill() to make it work), so the first 2
patches are unneeded.
What about the 3rd one (ARM: allow kernel to be loaded in middle of phymem)?
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: wangnan0@huawei.com (Wang Nan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: kexec: copying code to ioremapped area
Date: Thu, 23 Jan 2014 10:16:37 +0800 [thread overview]
Message-ID: <52E07B85.6030709@huawei.com> (raw)
In-Reply-To: <20140122132734.GB15937@n2100.arm.linux.org.uk>
On 2014/1/22 21:27, Russell King - ARM Linux wrote:
> On Wed, Jan 22, 2014 at 07:25:15PM +0800, Wang Nan wrote:
>> ARM's kdump is actually corrupted (at least for omap4460), mainly because of
>> cache problem: flush_icache_range can't reliably ensure the copied data
>> correctly goes into RAM.
>
> Quite right too. You're mistake here is thinking that flush_icache_range()
> should push it to RAM. That's incorrect.
>
> flush_icache_range() is there to deal with such things as loadable modules
> and self modifying code, where the MMU is not being turned off. Hence, it
> only flushes to the point of coherency between the I and D caches, and
> any further levels of cache between that point and memory are not touched.
> Why should it touch any more levels - it's not the function's purpose.
>
>> After mmu turned off and jump to the trampoline, kexec always failed due
>> to random undef instructions.
>
> We already have code in the kernel which deals with shutting the MMU off.
> An instance of how this can be done is illustrated in the soft_restart()
> code path, and kexec already uses this.
>
> One of the first things soft_restart() does is turn off the outer cache -
> which OMAP4 does have, but this can only be done if there is a single CPU
> running. If there's multiple CPUs running, then the outer cache can't be
> disabled, and that's the most likely cause of the problem you're seeing.
>
You are right, commit b25f3e1c (OMAP4/highbank: Flush L2 cache before disabling)
solves my problem, it flushes outer cache before disabling. I have tested it in
UP and SMP situations and it works (actually, omap4 has not ready to support kexec
in SMP case, I insert an empty cpu_kill() to make it work), so the first 2
patches are unneeded.
What about the 3rd one (ARM: allow kernel to be loaded in middle of phymem)?
WARNING: multiple messages have this Message-ID (diff)
From: Wang Nan <wangnan0@huawei.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: kexec@lists.infradead.org, Eric Biederman <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
Geng Hui <hui.geng@huawei.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/3] ARM: kexec: copying code to ioremapped area
Date: Thu, 23 Jan 2014 10:16:37 +0800 [thread overview]
Message-ID: <52E07B85.6030709@huawei.com> (raw)
In-Reply-To: <20140122132734.GB15937@n2100.arm.linux.org.uk>
On 2014/1/22 21:27, Russell King - ARM Linux wrote:
> On Wed, Jan 22, 2014 at 07:25:15PM +0800, Wang Nan wrote:
>> ARM's kdump is actually corrupted (at least for omap4460), mainly because of
>> cache problem: flush_icache_range can't reliably ensure the copied data
>> correctly goes into RAM.
>
> Quite right too. You're mistake here is thinking that flush_icache_range()
> should push it to RAM. That's incorrect.
>
> flush_icache_range() is there to deal with such things as loadable modules
> and self modifying code, where the MMU is not being turned off. Hence, it
> only flushes to the point of coherency between the I and D caches, and
> any further levels of cache between that point and memory are not touched.
> Why should it touch any more levels - it's not the function's purpose.
>
>> After mmu turned off and jump to the trampoline, kexec always failed due
>> to random undef instructions.
>
> We already have code in the kernel which deals with shutting the MMU off.
> An instance of how this can be done is illustrated in the soft_restart()
> code path, and kexec already uses this.
>
> One of the first things soft_restart() does is turn off the outer cache -
> which OMAP4 does have, but this can only be done if there is a single CPU
> running. If there's multiple CPUs running, then the outer cache can't be
> disabled, and that's the most likely cause of the problem you're seeing.
>
You are right, commit b25f3e1c (OMAP4/highbank: Flush L2 cache before disabling)
solves my problem, it flushes outer cache before disabling. I have tested it in
UP and SMP situations and it works (actually, omap4 has not ready to support kexec
in SMP case, I insert an empty cpu_kill() to make it work), so the first 2
patches are unneeded.
What about the 3rd one (ARM: allow kernel to be loaded in middle of phymem)?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Wang Nan <wangnan0@huawei.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: <kexec@lists.infradead.org>,
Eric Biederman <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
Geng Hui <hui.geng@huawei.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH 2/3] ARM: kexec: copying code to ioremapped area
Date: Thu, 23 Jan 2014 10:16:37 +0800 [thread overview]
Message-ID: <52E07B85.6030709@huawei.com> (raw)
In-Reply-To: <20140122132734.GB15937@n2100.arm.linux.org.uk>
On 2014/1/22 21:27, Russell King - ARM Linux wrote:
> On Wed, Jan 22, 2014 at 07:25:15PM +0800, Wang Nan wrote:
>> ARM's kdump is actually corrupted (at least for omap4460), mainly because of
>> cache problem: flush_icache_range can't reliably ensure the copied data
>> correctly goes into RAM.
>
> Quite right too. You're mistake here is thinking that flush_icache_range()
> should push it to RAM. That's incorrect.
>
> flush_icache_range() is there to deal with such things as loadable modules
> and self modifying code, where the MMU is not being turned off. Hence, it
> only flushes to the point of coherency between the I and D caches, and
> any further levels of cache between that point and memory are not touched.
> Why should it touch any more levels - it's not the function's purpose.
>
>> After mmu turned off and jump to the trampoline, kexec always failed due
>> to random undef instructions.
>
> We already have code in the kernel which deals with shutting the MMU off.
> An instance of how this can be done is illustrated in the soft_restart()
> code path, and kexec already uses this.
>
> One of the first things soft_restart() does is turn off the outer cache -
> which OMAP4 does have, but this can only be done if there is a single CPU
> running. If there's multiple CPUs running, then the outer cache can't be
> disabled, and that's the most likely cause of the problem you're seeing.
>
You are right, commit b25f3e1c (OMAP4/highbank: Flush L2 cache before disabling)
solves my problem, it flushes outer cache before disabling. I have tested it in
UP and SMP situations and it works (actually, omap4 has not ready to support kexec
in SMP case, I insert an empty cpu_kill() to make it work), so the first 2
patches are unneeded.
What about the 3rd one (ARM: allow kernel to be loaded in middle of phymem)?
next prev parent reply other threads:[~2014-01-23 2:16 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 11:25 [PATCH 0/3] Bugfix for kdump on arm Wang Nan
2014-01-22 11:25 ` Wang Nan
2014-01-22 11:25 ` Wang Nan
2014-01-22 11:25 ` Wang Nan
2014-01-22 11:25 ` [PATCH 1/3] ARM: Premit ioremap() to map reserved pages Wang Nan
2014-01-22 11:25 ` Wang Nan
2014-01-22 11:25 ` Wang Nan
2014-01-22 11:25 ` Wang Nan
2014-01-22 11:38 ` Will Deacon
2014-01-22 11:38 ` Will Deacon
2014-01-22 11:38 ` Will Deacon
2014-01-22 11:38 ` Will Deacon
2014-01-22 11:42 ` Russell King - ARM Linux
2014-01-22 11:42 ` Russell King - ARM Linux
2014-01-22 11:42 ` Russell King - ARM Linux
2014-01-22 11:42 ` Russell King - ARM Linux
2014-01-22 11:55 ` Wang Nan
2014-01-22 11:55 ` Wang Nan
2014-01-22 11:55 ` Wang Nan
2014-01-22 11:55 ` Wang Nan
2014-01-22 11:25 ` [PATCH 2/3] ARM: kexec: copying code to ioremapped area Wang Nan
2014-01-22 11:25 ` Wang Nan
2014-01-22 11:25 ` Wang Nan
2014-01-22 11:25 ` Wang Nan
2014-01-22 12:56 ` Vaibhav Bedia
2014-01-22 13:03 ` Wang Nan
2014-01-22 13:03 ` Wang Nan
2014-01-22 13:03 ` Wang Nan
2014-01-22 13:03 ` Wang Nan
2014-01-22 13:27 ` Russell King - ARM Linux
2014-01-22 13:27 ` Russell King - ARM Linux
2014-01-22 13:27 ` Russell King - ARM Linux
2014-01-22 13:27 ` Russell King - ARM Linux
2014-01-23 2:16 ` Wang Nan [this message]
2014-01-23 2:16 ` Wang Nan
2014-01-23 2:16 ` Wang Nan
2014-01-23 2:16 ` Wang Nan
2014-01-22 11:25 ` [PATCH 3/3] ARM: allow kernel to be loaded in middle of phymem Wang Nan
2014-01-22 11:25 ` Wang Nan
2014-01-22 11:25 ` Wang Nan
2014-01-22 11:25 ` Wang Nan
2014-01-23 19:15 ` Nicolas Pitre
2014-01-23 19:15 ` Nicolas Pitre
2014-01-23 19:15 ` Nicolas Pitre
2014-01-23 19:15 ` Nicolas Pitre
2014-01-23 19:31 ` Russell King - ARM Linux
2014-01-23 19:31 ` Russell King - ARM Linux
2014-01-23 19:31 ` Russell King - ARM Linux
2014-01-23 19:31 ` Russell King - ARM Linux
2014-01-23 20:01 ` Nicolas Pitre
2014-01-23 20:01 ` Nicolas Pitre
2014-01-23 20:01 ` Nicolas Pitre
2014-01-23 20:01 ` Nicolas Pitre
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=52E07B85.6030709@huawei.com \
--to=wangnan0@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hui.geng@huawei.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
/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.