From mboxrd@z Thu Jan 1 00:00:00 1970 From: james.morse@arm.com (James Morse) Date: Wed, 14 Dec 2016 12:11:33 +0000 Subject: [PATCH 1/2] arm64: Add enable/disable d-cache support for purgatory In-Reply-To: <20161214113701.GE17982@leverpostej> References: <7a4866b928c0905ec1074dce1bfc7984c968a58a.1479788404.git.panand@redhat.com> <5838834D.90205@arm.com> <9a79b666-7990-2a23-2d74-52b3317ce272@redhat.com> <58512A01.70101@arm.com> <20161214113701.GE17982@leverpostej> Message-ID: <585136F5.3070606@arm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Mark, On 14/12/16 11:37, Mark Rutland wrote: > On Wed, Dec 14, 2016 at 11:16:17AM +0000, James Morse wrote: >> On 14/12/16 10:12, Pratyush Anand wrote: >>> On Wednesday 14 December 2016 03:08 PM, Pratyush Anand wrote: >>>>> I would go as far as to generate the page tables at 'kexec -l' time, >>>>> and only if >>>> >>>> Ok..So you mean that I create a new section which will have page table >>>> entries mapping physicalmemory represented by remaining section, and >>>> then purgatory can just enable mmu with page table from that section, >>>> right? Seems doable. can do that. >>> >>> I see a problem here. If we create page table as a new segment then, how can we >>> verify in purgatory that sha for page table is correct? We need page table >>> before sha verification start,and we can not rely the page table created by >>> first kernel until it's sha is verified. So a chicken-egg problem. >> >> There is more than one of those! What happens if your sha256 calculation code is >> corrupted? You have to run it before you know. The same goes for all the >> purgatory code. >> >> This is why I think its better to do this in the kernel before we exit to >> purgatory, but obviously that doesn't work for kdump. > > I see in an earlier message that the need for sha256 was being discussed > in another thread. Do either of you happen to have a pointer to that. https://www.spinics.net/lists/arm-kernel/msg544472.html Thanks, James From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Message-ID: <585136F5.3070606@arm.com> Date: Wed, 14 Dec 2016 12:11:33 +0000 From: James Morse MIME-Version: 1.0 Subject: Re: [PATCH 1/2] arm64: Add enable/disable d-cache support for purgatory References: <7a4866b928c0905ec1074dce1bfc7984c968a58a.1479788404.git.panand@redhat.com> <5838834D.90205@arm.com> <9a79b666-7990-2a23-2d74-52b3317ce272@redhat.com> <58512A01.70101@arm.com> <20161214113701.GE17982@leverpostej> In-Reply-To: <20161214113701.GE17982@leverpostej> 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: Mark Rutland Cc: Pratyush Anand , geoff@infradead.org, kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org Hi Mark, On 14/12/16 11:37, Mark Rutland wrote: > On Wed, Dec 14, 2016 at 11:16:17AM +0000, James Morse wrote: >> On 14/12/16 10:12, Pratyush Anand wrote: >>> On Wednesday 14 December 2016 03:08 PM, Pratyush Anand wrote: >>>>> I would go as far as to generate the page tables at 'kexec -l' time, >>>>> and only if >>>> >>>> Ok..So you mean that I create a new section which will have page table >>>> entries mapping physicalmemory represented by remaining section, and >>>> then purgatory can just enable mmu with page table from that section, >>>> right? Seems doable. can do that. >>> >>> I see a problem here. If we create page table as a new segment then, how can we >>> verify in purgatory that sha for page table is correct? We need page table >>> before sha verification start,and we can not rely the page table created by >>> first kernel until it's sha is verified. So a chicken-egg problem. >> >> There is more than one of those! What happens if your sha256 calculation code is >> corrupted? You have to run it before you know. The same goes for all the >> purgatory code. >> >> This is why I think its better to do this in the kernel before we exit to >> purgatory, but obviously that doesn't work for kdump. > > I see in an earlier message that the need for sha256 was being discussed > in another thread. Do either of you happen to have a pointer to that. https://www.spinics.net/lists/arm-kernel/msg544472.html Thanks, James _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec