mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: "Habil Eren Türker" <habilerenturker@hotmail.com>,
	"Thomas Gleixner" <tglx@kernel.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Daniel J Blueman" <daniel@quora.org>,
	"Jiri Wiesner" <jwiesner@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/hpet: Mark boot-time variables as __ro_after_init
Date: Thu, 19 Nov 2026 11:40:32 -0800	[thread overview]
Message-ID: <55cf7d7a-b16b-4d7f-b455-d239f8d80363@intel.com> (raw)
In-Reply-To: <20261117122949.60297-1-habilerenturker@hotmail.com>

On 11/17/26 04:29, Habil Eren Türker wrote:
> The following variables are only written during early boot or __init
> functions and remain read-only at runtime:
> 
>  - hpet_blockid: set once in acpi_parse_hpet() (__init)
>  - hpet_msi_disable: set only in force_disable_hpet_msi() (early PCI quirk)
>  - hpet_freq: set only in hpet_enable() (__init)
>  - boot_hpet_disable: set only in force_disable_hpet() (early-quirks.c)
>    and __init setup functions (hpet_setup(), disable_hpet(),
>    hpet_is_pc10_damaged())
> 
> Mark them as __ro_after_init to protect them against unintended runtime
> modifications.

How did you find this? Why does it matter?

  reply	other threads:[~2026-11-19 19:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 12:29 Habil Eren Türker
2026-11-19 19:40 ` Dave Hansen [this message]
2026-11-19 20:37   ` Habil Eren Türker
2026-11-19 22:44     ` Dave Hansen
2026-11-19 23:02       ` Habil Eren Türker

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=55cf7d7a-b16b-4d7f-b455-d239f8d80363@intel.com \
    --to=dave.hansen@intel.com \
    --cc=bp@alien8.de \
    --cc=daniel@quora.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=habilerenturker@hotmail.com \
    --cc=hpa@zytor.com \
    --cc=jwiesner@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®