From: Chen Gang <gang.chen@asianux.com>
To: Toshi Kani <toshi.kani@hp.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"isimatu.yasuaki@jp.fujitsu.com" <isimatu.yasuaki@jp.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Suggestion] about calling debug_hotplug_cpu() which enabled by 'allmodconfig' for a x86_64 dual core laptop.
Date: Fri, 04 Oct 2013 17:27:47 +0800 [thread overview]
Message-ID: <524E8A13.7020903@asianux.com> (raw)
In-Reply-To: <1380812843.5429.46.camel@misato.fc.hp.com>
On 10/03/2013 11:07 PM, Toshi Kani wrote:
> On Thu, 2013-10-03 at 22:21 +0800, Chen Gang wrote:
>> One root cause found (but not only one), allmodconfig will enable
>> CONFIG_SYSFS_DEPRECATED which for new kernel on old distribution.
>>
>>
>> I am comparing from allmodconfig config file to defconfig config file,
>> the attachments are middle files (one enable CONFIG_SYSFS_DEPRECATED
>> which can not boot up, the other disable it which can boot up).
>>
>> The related information in "init/Kconfig"
>>
>> config SYSFS_DEPRECATED
>> bool "Enable deprecated sysfs features to support old userspace tools"
>> depends on SYSFS
>> default n
>> help
>> This option adds code that switches the layout of the "block" class
>> devices, to not show up in /sys/class/block/, but only in
>> /sys/block/.
>>
>> This switch is only active when the sysfs.deprecated=1 boot option is
>> passed or the SYSFS_DEPRECATED_V2 option is set.
>>
>> This option allows new kernels to run on old distributions and tools,
>> which might get confused by /sys/class/block/. Since 2007/2008 all
>> major distributions and tools handle this just fine.
>>
>> Recent distributions and userspace tools after 2009/2010 depend on
>> the existence of /sys/class/block/, and will not work with this
>> option enabled.
>>
>> Only if you are using a new kernel on an old distribution, you might
>> need to say Y here.
>>
>>
>> I will continue to analyze another related issues for allmodconfig on
>> my laptop (after disable SYSFS_DEPRECATED, for allmodconfig, it still
>> can not boot up successfully, although my 'middle' config file can).
>
> Since this is no longer a hotplug issue, I'd suggest you change the
> subject line and resend it to the folks who worked on this config
> option. I won't be able to help on this one.
>
OK, thanks, I will/should send related information (or patch) to the
related members for continue discussing.
And again, thank you for spending your time on it (already provided
useful information)
:-)
> -Toshi
>
>
>
>
Thanks.
--
Chen Gang
next prev parent reply other threads:[~2013-10-04 9:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 3:10 [Suggestion] about calling debug_hotplug_cpu() which enabled by 'allmodconfig' for a x86_64 dual core laptop Chen Gang
2013-10-02 15:28 ` Toshi Kani
2013-10-02 16:41 ` Chen Gang F T
2013-10-02 19:33 ` Toshi Kani
2013-10-03 0:49 ` Chen Gang
2013-10-03 14:21 ` Chen Gang
2013-10-03 15:07 ` Toshi Kani
2013-10-04 9:27 ` Chen Gang [this message]
2013-10-03 14:51 ` Toshi Kani
2013-10-04 10:54 ` Chen Gang F T
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=524E8A13.7020903@asianux.com \
--to=gang.chen@asianux.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hp.com \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.