Re: [patch] i386: use thread_info flags for debug regs and IO bitmaps

On Fri, 7 Jul 2006, Chuck Ebbert wrote:
>
> From: Stephane Eranian <[email protected]>
> 
> Use thread info flags to track use of debug registers and IO bitmaps.
>  
> 	- add TIF_DEBUG to track when debug registers are active
>  	- add TIF_IO_BITMAP to track when I/O bitmap is used
>  	- modify __switch_to() to use the new TIF flags

Can you explain what the advantages of this are?

I don't see it. It's just creating new state to describe state that we 
already had, and as far as I can tell, it's just a way to potentially have 
more new bugs thanks to the new state getting out of sync with the old 
one?

		Linus
-
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: [patch] i386: use thread_info flags for debug regs and IO bitmaps
    • From: Stephane Eranian <[email protected]>
  • Re: [patch] i386: use thread_info flags for debug regs and IO bitmaps
    • From: Andi Kleen <[email protected]>

• References:
  • [patch] i386: use thread_info flags for debug regs and IO bitmaps
    • From: Chuck Ebbert <[email protected]>

• Prev by Date: Re: [Suspend2-devel] Re: uswsusp history lesson
• Next by Date: Re: [patch] spinlocks: remove 'volatile'
• Previous by thread: Re: [patch] i386: use thread_info flags for debug regs and IO bitmaps
• Next by thread: Re: [patch] i386: use thread_info flags for debug regs and IO bitmaps
• 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]