> It probably is safe to remove... but we currently support '2.8.95 > kernel loads/resumes 2.6.24 image'... which would break if 2.8 uses > cr8. No it won't. 2.8 would just restore some random useless value. If 2.8 wants to use CR8 it would have to re-initialize it -Andi -- 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 4/8] unify paravirt parts of system.h
- From: Pavel Machek <[email protected]>
- Re: [PATCH 4/8] unify paravirt parts of system.h
- References:
- [PATCH 0/8] Integrate system.h
- From: Glauber de Oliveira Costa <[email protected]>
- [PATCH 1/8] remove volatile keyword from clflush.
- From: Glauber de Oliveira Costa <[email protected]>
- [PATCH 2/8] put together equal pieces of system.h
- From: Glauber de Oliveira Costa <[email protected]>
- [PATCH 3/8] unify load_segment macro
- From: Glauber de Oliveira Costa <[email protected]>
- [PATCH 4/8] unify paravirt parts of system.h
- From: Glauber de Oliveira Costa <[email protected]>
- Re: [PATCH 4/8] unify paravirt parts of system.h
- From: Avi Kivity <[email protected]>
- Re: [PATCH 4/8] unify paravirt parts of system.h
- From: Andi Kleen <[email protected]>
- Re: [PATCH 4/8] unify paravirt parts of system.h
- From: Pavel Machek <[email protected]>
- [PATCH 0/8] Integrate system.h
- Prev by Date: Re: [PATCH 4/8] unify paravirt parts of system.h
- Next by Date: Re: [PATCH] x86_64: fix problems due to use of "outb" to port 80 on some AMD64x2 laptops, etc.
- Previous by thread: Re: [PATCH 4/8] unify paravirt parts of system.h
- Next by thread: Re: [PATCH 4/8] unify paravirt parts of system.h
- Index(es):
 |