Hi!

On Tue, May 27, 2008 at 11:38 PM, Adrian Bunk <bunk@kernel.org> wrote:
quoted text
> On Tue, May 27, 2008 at 10:49:26PM +0200, Vegard Nossum wrote:
>> Hi,
>>
>> What do you think about this? The new file (vm86_mask.h) could actually be
>> embedded completely in processor-flags.h, but I went for what I believe is
>> the safer approach.
>
> Breaking the mutual header inclusion is appreciated, but some comments
> are below.

[...]

quoted text
>> -/* the DS BTS struct is used for ptrace as well */
>> -#include <asm/ds.h>
>> -
>>  struct task_struct;
>>
>>  extern void ptrace_bts_take_timestamp(struct task_struct *, enum bts_qualifier);
>
> Moving #include's out of an #ifdef __KERNEL__ can (and does here) break
> our userspace headers.
>
> Running "make headers_check" after touching anything under include/ is
> recommended since it catches these problems.
>

Ah, that's true. My mistake.

  CHECK   include/asm/ptrace.h
[...]/usr/include/asm/ptrace.h requires asm/ds.h, which does not exist
in exported headers

What do you reckon is better here, to put #ifdef __KERNEL__ around the
whole of ds.h and export it, or put #ifdef __KERNEL__ around the
#include in ptrace.h? It feels wasteful to put it around the whole
ds.h, since what is the point in exporting an empty file? On the other
hand, it makes much more sense to put it there than in the "caller" in
order to avoid the duplication of #ifdef __KERNEL__. So unless you
prefer otherwise, I will choose the former (to export ds.h as well).

I hope you agree with the idea of moving the #include line to the top
of the file, however?

Thanks for the tip, that is very useful. I didn't realize I should use
that and I'm sorry for wasting your time with the first attempt :-(

quoted text
>>...
>> --- /dev/null
>> +++ b/include/asm-x86/vm86_mask.h
>> @@ -0,0 +1,12 @@
>> +#ifndef ASM_X86_VM86_MASK
>> +#define ASM_X86_VM86_MASK
>> +
>> +#include <asm/processor-flags.h>
>> +
>> +#ifdef CONFIG_VM86
>> +#define X86_VM_MASK  X86_EFLAGS_VM
>> +#else
>> +#define X86_VM_MASK  0 /* No VM86 support */
>> +#endif
>> +
>> +#endif
>
> Do we need a new header for this or can it go into processor-flags.h ?

It can go in there, yes. I will do that in the re-worked (hopefully
correct) patch.

This business of breaking cycles is a bit nasty. There are very many
traps to fall into, very many setups to break, and very little support
from the tools to help you get it right (though with 'make
headers_check' I am a little better off).

Thanks for the help :-)


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/