public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: grygorii.strashko@ti•com (Grygorii Strashko)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] ARM: make virt_to_idmap() return unsigned long
Date: Thu, 4 Feb 2016 13:53:16 +0200	[thread overview]
Message-ID: <56B33BAC.6020303@ti.com> (raw)
In-Reply-To: <20160203195905.GC10826@n2100.arm.linux.org.uk>

On 02/03/2016 09:59 PM, Russell King - ARM Linux wrote:
> On Wed, Feb 03, 2016 at 10:43:23AM -0500, Vitaly Andrianov wrote:
>>> 100%. I came up with absolutely similar fix.
>>>
>>>
>>> Regarding, kexec:
>>> - it seems can't be tested on ks2 out of the box, because there is unmet dependency in kconfig
>>>   config KEXEC
>>>          bool "Kexec system call (EXPERIMENTAL)"
>>> -       depends on (!SMP || PM_SLEEP_SMP)
>>>          depends on !CPU_V7M
>>>          select KEXEC_CORE
>>>          help
>>>
>>> - any way, i've hacked kernel as above;
>>> - downloaded and built kexec-tools
>>> git://git.kernel.org/pub/scm/linux/kernel/git/geoff/kexec-tools.git
>>> - tried to run it using different combination of parameters, but always
>>> with below result:
>>> # kexec -l /boot/zImage
>>> kexec version: 15.12.22.16.38-g6503cb3
>>> Could not find a free area of memory of 0x3b2ca0 bytes...
>>> Cannot load /boot/zImage
>>>
>>> I'm doing something wrong, but don't know what yet :(
>>> - these patches were not applied, I'd like to see kexec not working first
>>>
>>>
>> I'm not sure about that particular issue, but when I worked on KS2 kexec I
>> had to patch kexec-tools to support KS2 LPAE memory.
> 
> This was specifically for Vitaly to test, as he has patches to work
> around most of the KS2 issues with kexec (although I have a KS2, I
> don't have everything that's necessary to get a working kexec in
> place.)
> 
> What I do want to know is whether this patch makes Vitaly's kexec
> patch smaller, and most importantly, what's left to deal with - in
> other words, I'd like to see the kernel patch for what's remaining.
> 
> Alternatively, if I can have both the kernel and userland patches
> so I can get a working kexec setup here, that may be a better way
> forward.
> 
> Either way, I think I'm going to push these patches out into
> linux-next very soon, because I believe that they're the correct
> approach to solving some of the issues found in Vitaly's original
> patch, unless someone discovers that they're broken in some manner.
> 

This patch boot/reboot tested on k2hk-evm (LPAE=y), ping works (with netcp regression fixed)
Tested-by: Grygorii Strashko <grygorii.strashko@ti•com>


-- 
regards,
-grygorii

  reply	other threads:[~2016-02-04 11:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 18:21 [PATCH 1/2] ARM: make virt_to_idmap() return unsigned long Russell King
2016-01-27  4:27 ` santosh.shilimkar at oracle.com
2016-02-01 15:20   ` Russell King - ARM Linux
2016-02-01 17:01     ` Vitaly Andrianov
2016-02-01 17:10       ` santosh shilimkar
2016-02-01 17:31         ` Russell King - ARM Linux
2016-02-01 17:55           ` santosh.shilimkar at oracle.com
2016-02-03  0:09         ` santosh shilimkar
2016-02-03 14:14           ` Grygorii Strashko
2016-02-03 15:43             ` Vitaly Andrianov
2016-02-03 19:59               ` Russell King - ARM Linux
2016-02-04 11:53                 ` Grygorii Strashko [this message]
2016-02-08 17:10                   ` Russell King - ARM Linux

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=56B33BAC.6020303@ti.com \
    --to=grygorii.strashko@ti$(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