Re: [PATCH tip/sched/core] mm/early_ioremap: Adjust early_ioremap system_state check

From	Thomas Gleixner <tglx@linutronix.de>
Newsgroups	linux.kernel
Subject	Re: [PATCH tip/sched/core] mm/early_ioremap: Adjust early_ioremap system_state check
Date	2017-06-16 13:00 +0200
Message-ID	<tSX8R-7mb-3@gated-at.bofh.it> (permalink)
References	<tSX8R-7mb-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Wed, 14 Jun 2017, Tom Lendacky wrote:
> A recent change added a new system_state value, SYSTEM_SCHEDULING, which
> exposed a warning issued by early_ioreamp() when the system_state was not
> SYSTEM_BOOTING. Since early_ioremap() can be called when the system_state
> is SYSTEM_SCHEDULING, the check to issue the warning is changed from
> system_state != SYSTEM_BOOTING to system_state >= SYSTEM_RUNNING.

Errm, why is that early_ioremap() stuff called after we enabled the
scheduler? At that point the regular ioremap stuff is long working.

Thanks,

	tglx

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: [PATCH tip/sched/core] mm/early_ioremap: Adjust early_ioremap  system_state check Thomas Gleixner <tglx@linutronix.de> - 2017-06-16 13:00 +0200

csiph-web