Re: [PATCH] pop previous section in alternative.c
- From: "Maciej W. Rozycki" <macro@xxxxxxxxxxxxxx>
- Date: Sun, 13 Apr 2008 16:27:05 +0100 (BST)
On Thu, 10 Apr 2008, Andi Kleen wrote:
A simple way to detect it on the assembler level would be checking
that the section is the same after #NO_APP as before #APP
Not as simple as the section stack would have to be traversed to check
whether there are any differences. And in the end, either such a complete
check or a simple one you have proposed may not be desirable, because I
can imagine in some scenarios the change of a section in an asm may be
deliberate. Let's not limit the tools.
Maciej
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] pop previous section in alternative.c
- From: Steven Rostedt
- Re: [PATCH] pop previous section in alternative.c
- From: Steven Rostedt
- Re: [PATCH] pop previous section in alternative.c
- From: H. Peter Anvin
- Re: [PATCH] pop previous section in alternative.c
- From: Andi Kleen
- Re: [PATCH] pop previous section in alternative.c
- From: Andy Whitcroft
- Re: [PATCH] pop previous section in alternative.c
- From: Steven Rostedt
- Re: [PATCH] pop previous section in alternative.c
- From: Andi Kleen
- Re: [PATCH] pop previous section in alternative.c
- From: Linus Torvalds
- Re: [PATCH] pop previous section in alternative.c
- From: Andi Kleen
- [PATCH] pop previous section in alternative.c
- Prev by Date: Re: [PATCH 1/3] Add prctl commands PR_GET_TSC and PR_SET_TSC
- Next by Date: Re: [patch 2/2] bootmem: Node-setup agnostic free_bootmem()
- Previous by thread: Re: [PATCH] pop previous section in alternative.c
- Next by thread: Re: [PATCH] pop previous section in alternative.c
- Index(es):
Relevant Pages
|
|
