[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081217120450.GA8600@mailshack.com>
Date: Wed, 17 Dec 2008 13:04:50 +0100
From: Alexander van Heukelum <heukelum@...lshack.com>
To: Cyrill Gorcunov <gorcunov@...il.com>
Cc: Alexander van Heukelum <heukelum@...tmail.fm>,
linux-arch@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Sam Ravnborg <sam@...nborg.org>
Subject: Re: [PATCH last/many] x86: checking framework for correct use of ENTRY/PROC
On Wed, Dec 17, 2008 at 02:51:53PM +0300, Cyrill Gorcunov wrote:
> On Wed, Dec 17, 2008 at 12:17 PM, Alexander van Heukelum
> <heukelum@...tmail.fm> wrote:
> > [ DO NOT APPLY (yet...) At this point this patch will
> > just cause the build to abort due to annotation errors
> > found. ]
> >
> > Introduce a checking framework to check correct pairing
> > of ENTRY/END and PROC/ENDPROC. It also checks that the
> > annotations are not nested. I have used the ideas and
> > most of the implementation from Cyrill Gorcunov who
> > introduced the framework to check for mismatching
> > KPROBE_ENTRY annotations, which was however soon made
> > obsolete by the removal of KPROBE_ENTRY/KPROBE_END.
> >
> > Checks performed:
> > o END must terminate an ENTRY annotation
> > o ENDPROC must terminate a PROC annotation
> > o ENTRY or PROC cannot be nested inside
> > another ENTRY or PROC section.
> >
> > Finally the macro ENTRY_PROC_FINAL is introduced to
> > enable checking correct closing of PROC and ENTRY
> > sections at the end of assembly files.
> >
> > Signed-off-by: Alexander van Heukelum <heukelum@...tmail.fm>
> > Cc: Cyrill Gorcunov <gorcunov@...il.com>
> ...
>
> Thanks Alexander!
>
> You know I think you meant __ASSEMBLY__ while
> were typing __ASSEMBLER__. Don't you? :)
If it matters there is some cleanup to do in the kernel tree ;).
Greetings,
Alexander
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists