Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1667638 > unrolled thread
| Started by | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| First post | 2017-06-16 13:00 +0200 |
| Last post | 2017-06-16 13:00 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
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
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Date | 2017-06-16 13:00 +0200 |
| Subject | Re: [PATCH tip/sched/core] mm/early_ioremap: Adjust early_ioremap system_state check |
| Message-ID | <tSX8R-7mb-3@gated-at.bofh.it> |
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 top | Article view | linux.kernel
csiph-web