From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EAE68C04AAF for ; Thu, 16 May 2019 16:49:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BD681205ED for ; Thu, 16 May 2019 16:49:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="Y7WJlt4b" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728681AbfEPQtO (ORCPT ); Thu, 16 May 2019 12:49:14 -0400 Received: from mail-qt1-f196.google.com ([209.85.160.196]:46088 "EHLO mail-qt1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728035AbfEPQtO (ORCPT ); Thu, 16 May 2019 12:49:14 -0400 Received: by mail-qt1-f196.google.com with SMTP id z19so4640072qtz.13 for ; Thu, 16 May 2019 09:49:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=V54eRnKwdjS+PEKbXuK6UCgdmon3FdybUlySjzqEJGo=; b=Y7WJlt4bLjAJ4WhWIbMzJ/8PhricDREUZCU7Q1/HTZvvFSjXhMw6Fj3NYJLMxnF5H3 xFmNwRnXYTntWpRu3Lpdbvwa5tqci5Xe358XawRq25kd+KE+5NovF5rGFK6+pyVUKFjE t5pWcHvFVNZlhWAdiIbzyX+khalrXvVMxRhdo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=V54eRnKwdjS+PEKbXuK6UCgdmon3FdybUlySjzqEJGo=; b=qzZh9SxsiAiAUuE/FPLywk7z6GCOX+oyB421rAAR09Rcf5xx0jT9MhrRozlb7kLyx4 by8LTTi0WLwduA1XjD/Elu5+AcGhVb08HZ+mq1k0Inetb4xw9NUeWOUoTRcAuwINQJFC avlwwIUow8l2BmJsF1RhKot0fBjC5FN6xDzzJFas9dCRUmDlK7m23E0ng6TXcU4QXc2V /e4uBstkpI0sKVcox02GFhsae527Qji9qfBJJ6HiQGbvUdBrRYwdVcJcTz8QdtO08IC6 xvW2ZYt0tovWhh3d1Wt4W5Z0Wyu5jR7jvX1qv+rlmWhO6uCFR68DK8AWTX5pyKws5ELo gnvw== X-Gm-Message-State: APjAAAUloXaD7OVSbitjzQnL66HGYcw0aMaZB0EnfhKV+Ixd7OquikZB GYi33nIpxJY+XojyiPI8WtYkNdAFvdmfKp2NCZznaQ== X-Google-Smtp-Source: APXvYqy+/6RfTqO4HVKK22HJ4SUb9lK/prYvmIxZ0Cl7qxFHUR3oqhJi1qikDD7OHXt/c+stN5QSeCyFVHsMZ9dZnA4= X-Received: by 2002:a0c:8aad:: with SMTP id 42mr40983967qvv.200.1558025353386; Thu, 16 May 2019 09:49:13 -0700 (PDT) MIME-Version: 1.0 References: <20190516102817.188519-1-hsinyi@chromium.org> <20190516102817.188519-2-hsinyi@chromium.org> In-Reply-To: From: Hsin-Yi Wang Date: Fri, 17 May 2019 00:48:47 +0800 Message-ID: Subject: Re: [PATCH v3 2/3] arm64: implement update_fdt_pgprot() To: Rob Herring Cc: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , Frank Rowand , Catalin Marinas , Will Deacon , Andrew Morton , Mike Rapoport , Ard Biesheuvel , Miles Chen , James Morse , Andrew Murray , Mark Rutland , Jun Yao , Yu Zhao , Robin Murphy , Laura Abbott , Stephen Boyd , Kees Cook Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 16, 2019 at 11:32 PM Rob Herring wrote: > Doesn't kexec operate on a copy because it already does modifications. > Hi Rob, This patch is to assist "[PATCH v3 3/3] fdt: add support for rng-seed" (https://lkml.org/lkml/2019/5/16/257). I thought that by default second kernel would use original fdt, so I write new seed back to original fdt. Might be wrong. ** "[PATCH v3 3/3] fdt: add support for rng-seed" is supposed to handle for adding new seed in kexec case, discussed in v2 (https://lkml.org/lkml/2019/5/13/425) By default (not considering user defines their own fdt), if second kernel uses copied fdt, when is it copied and can we modify that? Thanks! From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hsin-Yi Wang Subject: Re: [PATCH v3 2/3] arm64: implement update_fdt_pgprot() Date: Fri, 17 May 2019 00:48:47 +0800 Message-ID: References: <20190516102817.188519-1-hsinyi@chromium.org> <20190516102817.188519-2-hsinyi@chromium.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Rob Herring Cc: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , Frank Rowand , Catalin Marinas , Will Deacon , Andrew Morton , Mike Rapoport , Ard Biesheuvel , Miles Chen , James Morse , Andrew Murray , Mark Rutland , Jun Yao , Yu Zhao , Robin Murphy , Laura Abbott , Stephen Boyd , Kees List-Id: devicetree@vger.kernel.org On Thu, May 16, 2019 at 11:32 PM Rob Herring wrote: > Doesn't kexec operate on a copy because it already does modifications. > Hi Rob, This patch is to assist "[PATCH v3 3/3] fdt: add support for rng-seed" (https://lkml.org/lkml/2019/5/16/257). I thought that by default second kernel would use original fdt, so I write new seed back to original fdt. Might be wrong. ** "[PATCH v3 3/3] fdt: add support for rng-seed" is supposed to handle for adding new seed in kexec case, discussed in v2 (https://lkml.org/lkml/2019/5/13/425) By default (not considering user defines their own fdt), if second kernel uses copied fdt, when is it copied and can we modify that? Thanks! From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9C158C04AAF for ; Thu, 16 May 2019 16:49:21 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 6F0BB20881 for ; Thu, 16 May 2019 16:49:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="alYbHJwt"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="Y7WJlt4b" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6F0BB20881 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=chromium.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=QoEmkS8CLwcSYSSqJdy0iXH8HCFqmYFch4k3edXphtI=; b=alYbHJwtpO0RYD vd04g5V0mszO+9euJFkbdRPKUMrfNQ+Fhia0TAIsZ6r0UpPwl4BY5Okfkrh9l69XaYWc+60O1968u lBH659jO8D2GRyD/SxI0Vc09KvsrJA9HAKWT2YdNb09Dv21WWZBVEys0fW0xG2/Co+ydX2ncLuxCn xRvj7MFVZmTiUhdqFv/Uob4M6dy4NJ1hvfH/W/hGqz+JKWX6jA6QMgnIN2jJtsqPV1Y8RzVZxUgyU w0v2kO/NZ/QUiR7diOQjhzm8UCZkj6fubBWMORkLSIO0AH6GVTmfarI6No63LLWADJ6J97VlR/jm1 SPGjLr5AEAPOAyIrpd4A==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hRJZE-0002uc-W1; Thu, 16 May 2019 16:49:16 +0000 Received: from mail-qt1-x842.google.com ([2607:f8b0:4864:20::842]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hRJZC-0002ts-JF for linux-arm-kernel@lists.infradead.org; Thu, 16 May 2019 16:49:15 +0000 Received: by mail-qt1-x842.google.com with SMTP id d13so4710192qth.5 for ; Thu, 16 May 2019 09:49:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=V54eRnKwdjS+PEKbXuK6UCgdmon3FdybUlySjzqEJGo=; b=Y7WJlt4bLjAJ4WhWIbMzJ/8PhricDREUZCU7Q1/HTZvvFSjXhMw6Fj3NYJLMxnF5H3 xFmNwRnXYTntWpRu3Lpdbvwa5tqci5Xe358XawRq25kd+KE+5NovF5rGFK6+pyVUKFjE t5pWcHvFVNZlhWAdiIbzyX+khalrXvVMxRhdo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=V54eRnKwdjS+PEKbXuK6UCgdmon3FdybUlySjzqEJGo=; b=UnclLNu8mC6RvPbCtpcR4RYGq5VUJZOzjNwQg8AAiPLlMYzp2K8vKql5fv/GGMFe+u Tnk3X33uUGqRh6T+zlGp+AhpZiEnl2n5/iTas8AhZ2FEeW4HJfWjHfkESYCblfvMFMw1 s73DneR62jN7eN1/uGa3J/KZxF3+V45cCjIjsIjYI8oXG8yoY9lG+U208yfCwcOluzQt 723Y13FP+Qhb2kXK0c+l3oy1jcElgwjQ3315kraWJtmBfIfD4HpVAF8O/pzPRMcCm7Ko t1ZENG/f6NG3eVF70/gZjgeJdqg1P3MBtLM2Qy8PYfIoTJH45HLwe/Q8g3tAvI+aHyr2 aY4A== X-Gm-Message-State: APjAAAVCac0oKUalqMgROxqBQNcPlAHnB5QD48L2FvpPX4xiNnX57oyi hA+yGujtp1h6NCQpgW8JnRnt2PmBZpucDK22/oRhIQ== X-Google-Smtp-Source: APXvYqy+/6RfTqO4HVKK22HJ4SUb9lK/prYvmIxZ0Cl7qxFHUR3oqhJi1qikDD7OHXt/c+stN5QSeCyFVHsMZ9dZnA4= X-Received: by 2002:a0c:8aad:: with SMTP id 42mr40983967qvv.200.1558025353386; Thu, 16 May 2019 09:49:13 -0700 (PDT) MIME-Version: 1.0 References: <20190516102817.188519-1-hsinyi@chromium.org> <20190516102817.188519-2-hsinyi@chromium.org> In-Reply-To: From: Hsin-Yi Wang Date: Fri, 17 May 2019 00:48:47 +0800 Message-ID: Subject: Re: [PATCH v3 2/3] arm64: implement update_fdt_pgprot() To: Rob Herring X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190516_094914_660359_1AAFD8A2 X-CRM114-Status: UNSURE ( 9.73 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , devicetree@vger.kernel.org, Yu Zhao , Kees Cook , Ard Biesheuvel , Catalin Marinas , Stephen Boyd , Will Deacon , "linux-kernel@vger.kernel.org" , Mike Rapoport , Jun Yao , Miles Chen , James Morse , Andrew Murray , Andrew Morton , Laura Abbott , Frank Rowand , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , Robin Murphy Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, May 16, 2019 at 11:32 PM Rob Herring wrote: > Doesn't kexec operate on a copy because it already does modifications. > Hi Rob, This patch is to assist "[PATCH v3 3/3] fdt: add support for rng-seed" (https://lkml.org/lkml/2019/5/16/257). I thought that by default second kernel would use original fdt, so I write new seed back to original fdt. Might be wrong. ** "[PATCH v3 3/3] fdt: add support for rng-seed" is supposed to handle for adding new seed in kexec case, discussed in v2 (https://lkml.org/lkml/2019/5/13/425) By default (not considering user defines their own fdt), if second kernel uses copied fdt, when is it copied and can we modify that? Thanks! _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel