From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751966AbcGAFGG (ORCPT ); Fri, 1 Jul 2016 01:06:06 -0400 Received: from mail-pa0-f51.google.com ([209.85.220.51]:32932 "EHLO mail-pa0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750924AbcGAFGE (ORCPT ); Fri, 1 Jul 2016 01:06:04 -0400 Date: Fri, 1 Jul 2016 14:11:12 +0900 From: AKASHI Takahiro To: ebiederm@xmission.com, dyoung@redhat.com, bhe@redhat.com, vgoyal@redhat.com Cc: kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, catalin.marinas@arm.com, will.deacon@arm.com Subject: [RFC] arm64: kexec_file_load support Message-ID: <20160701051111.GL20774@linaro.org> Mail-Followup-To: AKASHI Takahiro , ebiederm@xmission.com, dyoung@redhat.com, bhe@redhat.com, vgoyal@redhat.com, kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, catalin.marinas@arm.com, will.deacon@arm.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I'm not sure whether there is any demand for kexec_file_load support on arm64, but anyhow I'm working on this and now my early prototype code does work fine. There is, however, one essential issue: While arm64 kernel requires a device tree blob to be set up correctly at boot time, the current system call API doesn't have this parameter. int kexec_file_load(int kernel_fd, int initrd_fd, unsigned long cmdline_len, const char *cmdline_ptr, unsigned long flags); Should we invent a new system call, like kexec_file_load2, and, if so, what kind of interface would be desired? Thanks, -Takahiro AKASHI From mboxrd@z Thu Jan 1 00:00:00 1970 From: takahiro.akashi@linaro.org (AKASHI Takahiro) Date: Fri, 1 Jul 2016 14:11:12 +0900 Subject: [RFC] arm64: kexec_file_load support Message-ID: <20160701051111.GL20774@linaro.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi, I'm not sure whether there is any demand for kexec_file_load support on arm64, but anyhow I'm working on this and now my early prototype code does work fine. There is, however, one essential issue: While arm64 kernel requires a device tree blob to be set up correctly at boot time, the current system call API doesn't have this parameter. int kexec_file_load(int kernel_fd, int initrd_fd, unsigned long cmdline_len, const char *cmdline_ptr, unsigned long flags); Should we invent a new system call, like kexec_file_load2, and, if so, what kind of interface would be desired? Thanks, -Takahiro AKASHI From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-pa0-x236.google.com ([2607:f8b0:400e:c03::236]) by bombadil.infradead.org with esmtps (Exim 4.85_2 #1 (Red Hat Linux)) id 1bIqeh-0002NH-JH for kexec@lists.infradead.org; Fri, 01 Jul 2016 05:06:20 +0000 Received: by mail-pa0-x236.google.com with SMTP id bz2so35109478pad.1 for ; Thu, 30 Jun 2016 22:05:58 -0700 (PDT) Date: Fri, 1 Jul 2016 14:11:12 +0900 From: AKASHI Takahiro Subject: [RFC] arm64: kexec_file_load support Message-ID: <20160701051111.GL20774@linaro.org> MIME-Version: 1.0 Content-Disposition: inline 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: ebiederm@xmission.com, dyoung@redhat.com, bhe@redhat.com, vgoyal@redhat.com Cc: will.deacon@arm.com, catalin.marinas@arm.com, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Hi, I'm not sure whether there is any demand for kexec_file_load support on arm64, but anyhow I'm working on this and now my early prototype code does work fine. There is, however, one essential issue: While arm64 kernel requires a device tree blob to be set up correctly at boot time, the current system call API doesn't have this parameter. int kexec_file_load(int kernel_fd, int initrd_fd, unsigned long cmdline_len, const char *cmdline_ptr, unsigned long flags); Should we invent a new system call, like kexec_file_load2, and, if so, what kind of interface would be desired? Thanks, -Takahiro AKASHI _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec