From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Message-ID: <1449096562.6139.74.camel@infradead.org> Subject: Re: [PATCH v12 08/16] arm64/kexec: Add core kexec support From: Geoff Levand Date: Wed, 02 Dec 2015 14:49:22 -0800 In-Reply-To: <002101d12c66$ae985440$0bc8fcc0$@codeaurora.org> References: <6ac232ad37d6b02cf2d5848b15236f26f5ac61ac.1448403503.git.geoff@infradead.org> <20151127131306.GE23908@dhcppc13.redhat.com> <1448909475.31214.27.camel@infradead.org> <20151201021615.GA5704@dhcppc13.redhat.com> <002101d12c66$ae985440$0bc8fcc0$@codeaurora.org> Mime-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Azriel Samson , 'Pratyush Anand' Cc: 'Mark Rutland' , marc.zyngier@arm.com, 'Catalin Marinas' , 'Will Deacon' , 'AKASHI Takahiro' , christoffer.dall@linaro.org, 'Dave Young' , kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org Azriel and Pratyush, On Tue, 2015-12-01 at 11:32 -0700, Azriel Samson wrote: > I tested with v11 on our platform and I too needed the invalidation > fix. I pushed out a kexec-v12.1 branch to my linux-kexec repo [1] with fixes. Could you test it with both kexec reboot and kdump? For kdump, use something like: CMDLINE += 'crashkernel=64M@2240M' then # kexec -d --load-panic /boot/vmlinux.strip --append="1 mem=64M maxcpus=1 reset_devices console=... root=..." # echo c > /proc/sysrq-trigger We need to test both reboot and kdump since the the way the kexec is done is different for the two. [1] https://git.kernel.org/cgit/linux/kernel/git/geoff/linux-kexec.git -Geoff _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec From mboxrd@z Thu Jan 1 00:00:00 1970 From: geoff@infradead.org (Geoff Levand) Date: Wed, 02 Dec 2015 14:49:22 -0800 Subject: [PATCH v12 08/16] arm64/kexec: Add core kexec support In-Reply-To: <002101d12c66$ae985440$0bc8fcc0$@codeaurora.org> References: <6ac232ad37d6b02cf2d5848b15236f26f5ac61ac.1448403503.git.geoff@infradead.org> <20151127131306.GE23908@dhcppc13.redhat.com> <1448909475.31214.27.camel@infradead.org> <20151201021615.GA5704@dhcppc13.redhat.com> <002101d12c66$ae985440$0bc8fcc0$@codeaurora.org> Message-ID: <1449096562.6139.74.camel@infradead.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Azriel and Pratyush, On Tue, 2015-12-01 at 11:32 -0700, Azriel Samson wrote: > I tested with v11 on our platform and I too needed the invalidation > fix. I pushed out a kexec-v12.1 branch to my linux-kexec repo [1] with fixes. Could you test it with both kexec reboot and kdump? For kdump, use something like: CMDLINE += 'crashkernel=64M at 2240M' then # kexec -d --load-panic /boot/vmlinux.strip --append="1 mem=64M maxcpus=1 reset_devices console=... root=..." # echo c > /proc/sysrq-trigger We need to test both reboot and kdump since the the way the kexec is done is different for the two. [1] https://git.kernel.org/cgit/linux/kernel/git/geoff/linux-kexec.git -Geoff