Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Q: Which CONFIG_* items are latency killers, and should be avoided ?
...
APM: The APM model assigns power management control to the BIOS, and BIOS code is never written with RT-latency in mind. If configured, APM routines are invoked with SMI priority, which breaks the rule that adeos-ipipe must be in charge of such things. DISABLE_SMI doesnt help here (more later).
The problem is that I am not able to find this APM thing anywhere.
See the screenshots below:
"ACPI (Advanced Configuration and Power Interface) Support" results in the following menu:
Code:
--- ACPI (Advanced Configuration and Power Interface) Support[*] Deprecated /proc/acpi files[*] Deprecated power /proc/acpi directories
<M> ACPI 4.0 power meter
< > EC read/write access through /sys/kernel/debug/ec (NEW)[*] Deprecated /proc/acpi/event support
<M> AC Adapter
<M> Battery
{M} Button
{M} Video
<M> Fan[*] Dock
<M> Processor
< > IPMI (NEW)
<M> Processor Aggregator
<M> Thermal Zone
-*- NUMA support
() Custom DSDT
Table file to include[*] Debug Statements
[ ] Additionally enable ACPI function tracing
<M> PCI slot detection driver
{M} Container and Module Devices (EXPERIMENTAL)
<M> Memory Hotplug
<M> Smart Battery System
< > Hardware Error Device (NEW)
[ ] ACPI Platform Error Interface (APEI) (NEW)
Please help.
Last edited by Aquarius_Girl; 02-16-2015 at 11:57 PM.
Sorry, but I couldn't get your point here.
I can't see APM in "Power management and ACPI options".
Did you see the second screenshot?
What's the point that I am missing?
Thanks for your time , BTW.
EDIT
Actually, I am using "make menuconfig". That shows a GUI. This option isn't there in "Power management and ACPI support". I did attach the screenshot. what am I over looking? –
Last edited by Aquarius_Girl; 06-01-2012 at 03:32 AM.
linux-y3pi:/usr/src/linux-2.6.38.8 # grep X86_32 .config
# CONFIG_X86_32 is not set
linux-y3pi:/usr/src/linux-2.6.38.8 # grep PM_SLEEP .config
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
# CONFIG_PM_SLEEP_ADVANCED_DEBUG is not set
So, now I opened the .config and set CONFIG_X86_32 to y and saved.
Still, APM isn't visible through make menuconfig.
Well, learning comes at a cost.
Last edited by Aquarius_Girl; 02-16-2015 at 11:57 PM.
I did "make menuconfig" with your .config and APM is visible.
Thus I don't understand why it is not for you
EDIT
Quote:
Originally Posted by Anisha Kaul
So, now I opened the .config and set CONFIG_X86_32 to y and saved.
If you mean that you did use an editor for that I'm not sure it can work. Though I be not sure of that my guess is you should use "make menuconfig" to change a config setting.
Last edited by Didier Spaier; 08-15-2015 at 05:41 PM.
The reason why we don't get the same results is that APM depends on X86_32 [=y].
But this dependency can be met only if CONFIG_X86_32 is defined, which is done in the "make *config" process only for relevant ARCHs.
Unless explicitly stated by the user the ARCH variable's value is set up according to the results of the "uname -m" command in the main Makefile of the kernel source tree, in our case linux-2.6.38/Makefile:
Code:
# SUBARCH tells the usermode build what the underlying arch is. That is set
# first, and if a usermode build is happening, the "ARCH=um" on the command
# line overrides the setting of ARCH below. If a native build is happening,
# then ARCH is assigned, getting whatever value it gets normally, and
# SUBARCH is subsequently ignored.
SUBARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ \
-e s/arm.*/arm/ -e s/sa110/arm/ \
-e s/s390x/s390/ -e s/parisc64/parisc/ \
-e s/ppc.*/powerpc/ -e s/mips.*/mips/ \
-e s/sh[234].*/sh/ )
# Cross compiling and selecting different set of gcc/bin-utils
#
---------------------------------------------------------------------------
#
# When performing cross compilation for other architectures ARCH shall be
set
# to the target architecture. (See arch/* for the possibilities).
# ARCH can be set during invocation of make:
# make ARCH=ia64
# Another way is to have ARCH set in the environment.
# The default ARCH is the host where make is executed.
This is confirmed in linux-2.6.38/Documentation/kbuild/makefiles.txt:
Code:
ARCH
This variable defines the target architecture, such as "i386",
"arm", or "sparc". Some kbuild Makefiles test $(ARCH) to
determine which files to compile.
By default, the top Makefile sets $(ARCH) to be the same as the
host system architecture. For a cross build, a user may
override the value of $(ARCH) on the command line:
make ARCH=m68k ...
Here "uname -m" result is "i686" thus CONFIG_APM is defined in the "make menuconfig" process.
But if I type for instance "make ARCH=arm menuconfig" neither CONFIG_X86_32 nor CONFIG_APM are defined thus there is no menu entry for APM in the "menuconfig" screens.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.