[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <B9E073BF-14BD-485F-9FB6-BE17A385C08A@gmail.com>
Date: Tue, 21 Feb 2017 14:47:08 +0900
From: Ho-Eun Ryu <hoeun.ryu@...il.com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: kernel-hardening@...ts.openwall.com,
linux-kernel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
Anna-Maria Gleixner <anna-maria@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>
Subject: Re: [RFC 5/7] cpu: mark ro_mostly_after_init for cpuhp_ap/bp_states
> On 20 Feb 2017, at 5:20 PM, Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:
>
> On 2017-02-19 19:04:08 [+0900], Hoeun Ryu wrote:
>> It would be good that `__ro_mostly_after_init` is marked to cpuhp state
>> objects.
> why?
>
I’m requesting for comments of a new feature called __ro_mostly_after_init section marker.
It’s similar to __ro_after_init, but the section can be writable for some point of time.
Please see the cover letter [1] and the first patch [2].
[1] : https://lkml.org/lkml/2017/2/19/29
[2] : https://lkml.org/lkml/2017/2/19/32
> Sebastian
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
