[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181030050900.GA25987@dhcp-128-65.nay.redhat.com>
Date:   Tue, 30 Oct 2018 13:09:00 +0800
From:   Dave Young <dyoung@...hat.com>
To:     lijiang <lijiang@...hat.com>
Cc:     Borislav Petkov <bp@...en8.de>, 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
Subject: Re: [PATCH] kdump, vmcoreinfo: Export sme_me_mask value to vmcoreinfo
On 10/30/18 at 12:46pm, lijiang wrote:
> 在 2018年10月29日 21:49, Borislav Petkov 写道:
> > 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?
> > 
> 
> I'm not sure whether the following document is what you need.
> Documentation/ABI/testing/sysfs-kernel-vmcoreinfo
It is not the content, I think it is a good catch from Boris, it would
be good to document the exported things in somewhere eg.
Documentation/kdump/vmcoreinfo.txt
> 
> Thanks.
> Lianbo
> > If not, we need it documented.
> > 
Thanks
Dave
Powered by blists - more mailing lists
 
