[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e8357c26-1969-f870-d2e5-62b77a1b4fd5@redhat.com>
Date: Sat, 27 Oct 2018 10:19:52 +0800
From: lijiang <lijiang@...hat.com>
To: Borislav Petkov <bp@...en8.de>
Cc: linux-kernel@...r.kernel.org, kexec@...ts.infradead.org,
tglx@...utronix.de, mingo@...hat.com, x86@...nel.org,
bhe@...hat.com, dyoung@...hat.com
Subject: Re: [PATCH] kdump, vmcoreinfo: Export sme_me_mask value to vmcoreinfo
在 2018年10月27日 00:35, Borislav Petkov 写道:
> On Fri, Oct 26, 2018 at 08:32:11PM +0800, lijiang wrote:
>> If SME is enabled in the first kernel, the crash kernel's page table(pgd/pud/pmd/pte)
>> contains the memory encryption mask, so i have to remove the sme mask to obtain the
>> true physical address when dump vmcore.
>
> Sorry, I have no clue what makedumpfile does exactly so you'd have to
> be more detailed (or wait until I look at it :)). Which kernel accesses
> which kernel's pagetable?
>
> /me goes and looks at the makedumpfile's manpage...
>
So sorry that i should provide more detail about this.
Thanks a lot for spending time reading the manpage.
> Ok, it uses vmcoreinfo to exclude pages which would mean, it accesses
> the first kernel's pagetable and traverses it.
>
> Am I close?
>
Yes, your explanation is perfect.
Thanks.
Lianbo
Powered by blists - more mailing lists