From: Henry C <hc128168@gmail.com>
To: Valentin Vidic <Valentin.Vidic@carnet.hr>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Listing Supported Kernel Parameters?
Date: Tue, 1 Jan 2019 01:12:36 +0800 [thread overview]
Message-ID: <CAGPGUd-tV1dGDtKEx44F_QrXD8HvkmyeknjtLTnO69J2c_mCGA@mail.gmail.com> (raw)
In-Reply-To: <20181231170122.GB8140@gavran.carpriv.carnet.hr>
[-- Attachment #1.1: Type: text/plain, Size: 906 bytes --]
Thanks for your direction!
Found what I want!
Appreicate!
On Tue, Jan 1, 2019 at 1:01 AM Valentin Vidic <Valentin.Vidic@carnet.hr>
wrote:
> On Tue, Jan 01, 2019 at 12:48:58AM +0800, Henry C wrote:
> > I just downloaded the source here:
> >
> http://vault.centos.org/7.5.1804/os/Source/SPackages/kernel-3.10.0-862.el7.src.rpm
> >
> > And to my surprise, I don't even see mce as a kernel parameter based on
> the
> > command you suggested:
> > $ grep -r "early_param" . | grep mce
> > $
> >
> > So it seems like "early_param" only covers some kernel parameters but
> not all.
>
> Indeed, mce param seems to be defined using __setup:
>
> __setup("mce", mcheck_enable);
> __setup("nomce", mcheck_disable);
>
> --
> Valentin
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
[-- Attachment #1.2: Type: text/html, Size: 1667 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2018-12-31 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 6:27 Listing Supported Kernel Parameters? Henry C
2018-12-31 14:37 ` Valentin Vidic
2018-12-31 16:48 ` Henry C
2018-12-31 17:01 ` Valentin Vidic
2018-12-31 17:12 ` Henry C [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGPGUd-tV1dGDtKEx44F_QrXD8HvkmyeknjtLTnO69J2c_mCGA@mail.gmail.com \
--to=hc128168@gmail.com \
--cc=Valentin.Vidic@carnet.hr \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).