[RFC PATCH 0/3] Clean up x86 CPU feature setup

x86 CPU feature flag setup has become impossible to debug.
Every user just does set_bit()/clear_bit() or writes the
entire set to change the flags, so there's no way to trace
how they're being set.

This patchset creates an API and debug messages for tracking
how the flags get set. It's not nearly done, but I want to
know whether or not to continue.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC PATCH 0/3] Clean up x86 CPU feature setup
    • From: Andi Kleen <[email protected]>
  • [RFC PATCH 3/3] x86: use the x86 CPU feature API
    • From: Chuck Ebbert <[email protected]>
  • [RFC PATCH 2/3] x86: new API for modifying CPU feature flags
    • From: Chuck Ebbert <[email protected]>
  • [RFC PATCH 1/3] x86: use defined names for all CPU feature flags
    • From: Chuck Ebbert <[email protected]>

• Prev by Date: Re: [PATCH v3] hpet: Detect hidden HPET on NVidia motherboards
• Next by Date: [RFC PATCH 1/3] x86: use defined names for all CPU feature flags
• Previous by thread: /proc/sef/fd/0 is a socket ?!
• Next by thread: [RFC PATCH 1/3] x86: use defined names for all CPU feature flags
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]