From: "孙世龙 sunshilong" <sunshilong369@gmail.com>
To: Pavel Machek <pavel@ucw.cz>, LKML <linux-kernel@vger.kernel.org>
Cc: kernelnewbies <Kernelnewbies@kernelnewbies.org>,
Greg KH <greg@kroah.com>
Subject: Re: Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform?
Date: Sun, 19 Jul 2020 13:03:25 +0800 [thread overview]
Message-ID: <CAAvDm6YcE7VwphmD0t4FP+JNutkC4W8B=n1X5adL7wZ2s=92Wg@mail.gmail.com> (raw)
In-Reply-To: <20200704122222.GB15530@amd>
Hi, Pavel
>> Are there some potentially serious problems that I should be aware of
>> if I totally disable the CONFIG_ACPI option on the X86_64 platform?
>These machines are still mostly IBM-PC compatible, so it is likely to
>somehow work. You'll likely get worse power and thermal
>management. Try it.
Thank you for taking the time to respond to my question.
Do you mean disabling the CONFIG_ACPI option is mostly on IBM-PC
compatible platforms?
Do you think disabling the CONFIG_ACPI may cause the OS failing to boot
up?
Thank you for your attention to this matter.
On Sat, Jul 4, 2020 at 8:22 PM Pavel Machek <pavel@ucw.cz> wrote:
>
> Hi!
>
> > Are there some potentially serious problems that I should be aware of
> > if I totally disable the CONFIG_ACPI option on the X86_64 platform?
> >
> > Would it do harm to the hardware?
> >
> > Thank you for your attention to this matter.
>
> These machines are still mostly IBM-PC compatible, so it is likely to
> somehow work. You'll likely get worse power and thermal
> management. Try it.
>
> Pavel
>
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2020-07-19 5:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 9:15 Are there some potentially serious problems that I should be aware of if I totally disable the CONFIG_ACPI option on the X86_64 platform? 孙世龙 sunshilong
2020-07-01 10:58 ` Greg KH
[not found] ` <CAAvDm6YjbvEq9Y3wG-Lx_-hJtQ_LW28j97BOqvrewYXnEAS2dg@mail.gmail.com>
2020-07-01 12:28 ` 孙世龙 sunshilong
2020-07-19 4:38 ` 孙世龙 sunshilong
2020-07-04 12:22 ` Pavel Machek
2020-07-04 13:34 ` 孙世龙 sunshilong
2020-07-04 20:09 ` Pavel Machek
2020-07-05 1:47 ` 孙世龙 sunshilong
2020-07-19 5:03 ` 孙世龙 sunshilong [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='CAAvDm6YcE7VwphmD0t4FP+JNutkC4W8B=n1X5adL7wZ2s=92Wg@mail.gmail.com' \
--to=sunshilong369@gmail.com \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).