[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181029134918.GB32150@zn.tnic>
Date: Mon, 29 Oct 2018 14:49:18 +0100
From: Borislav Petkov <bp@...en8.de>
To: lijiang <lijiang@...hat.com>
Cc: Baoquan He <bhe@...hat.com>, 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
On Mon, Oct 29, 2018 at 09:41:26PM +0800, lijiang wrote:
> > VMCOREINFO_NUMBER(phys_base);
> > VMCOREINFO_SYMBOL(init_top_pgt);
> > vmcoreinfo_append_str("NUMBER(pgtable_l5_enabled)=%d\n",
> > pgtable_l5_enabled());
> >
> > + VMCOREINFO_NUMBER(sme_mask);
What I'm still missing from the whole fun is where are we documenting
the contents of that vmcoreinfo thing?
If not, we need it documented.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists