linux-kernel - Re: [PATCH] kdump, vmcoreinfo: Export sme_me

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c55bef2a-b972-7e6e-b698-6ac1bc736046@redhat.com>
Date:   Sat, 27 Oct 2018 22:41:56 +0800
From:   lijiang <lijiang@...hat.com>
To:     Boris Petkov <bp@...en8.de>, Baoquan He <bhe@...hat.com>
Cc:     Petr Tesarik <ptesarik@...e.cz>, linux-kernel@...r.kernel.org,
        x86@...nel.org, kexec@...ts.infradead.org, mingo@...hat.com,
        tglx@...utronix.de, dyoung@...hat.com
Subject: Re: [PATCH] kdump, vmcoreinfo: Export sme_me_mask value to vmcoreinfo

在 2018年10月27日 21:17, Boris Petkov 写道:
> On October 27, 2018 12:08:58 PM GMT+01:00, Baoquan He <bhe@...hat.com> wrote:
>> OK, then it's fine to get the bit number, e.g calling
>> find_first_bit(sme_me_mask, BITS_PER_LONG), and export it to
>> vmcoreinfo. Thanks.
> 
> You can simply assign sme_me_mask for now...
> 

Thank you, Boris and Baoquan.

Actually, the value of 'sme_me_mask' is 0x800000000000 when SME is enabled, otherwise it is 0.
That is to say, if the bit 47 is set, the bit number is also 0x800000000000 (1 << 47UL);

At present, they are both the same value.

Regards,
Lianbo