Re: [PATCH v2 0/6] Clean up and unify the vDSO

[H. Peter Anvin]

On 04/24/2014 03:08 PM, Andy Lutomirski wrote:
> This rewrites a bunch of the vdso code.  After these patches, the vvar
> and hpet pages are mapped directly after the vdso text on all five vdso
> variants.  The fixmaps are gone on 64-bit systems.
> 
> It would be possible to build the x32 vdso the normal way on top of
> these patches.
> 
> I haven't touched the pvclock code.  I'd want to understand why it
> exists, why it isn't using rdtsc, and why it has two rdtsc_barrier calls
> before rearranging it.  In a discussion with Marcello Tosatti, I think
> we concluded that the kvmclock code could be significantly simplified
> and sped up without breaking anything, but I want to save that for
> later.
> 
> This should apply to -linus or to tip/x86/vdso.  It's also here:
> 
> https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=vdso/cleanups
> 
> and it has survived the build bot for a day.
> 

Hello,

I get build errors building an allyesconfig on i386:

/home/hpa/kernel/distwork/arch/x86/vdso/vdso32-setup.c: In function
‘arch_vma_name’:
/home/hpa/kernel/distwork/arch/x86/vdso/vdso32-setup.c:123:9: error:
dereferencing pointer to incomplete type
  if (vma->vm_mm && vma->vm_start == (long)vma->vm_mm->context.vdso)
         ^
/home/hpa/kernel/distwork/arch/x86/vdso/vdso32-setup.c:123:23: error:
dereferencing pointer to incomplete type
  if (vma->vm_mm && vma->vm_start == (long)vma->vm_mm->context.vdso)
                       ^
/home/hpa/kernel/distwork/arch/x86/vdso/vdso32-setup.c:123:46: error:
dereferencing pointer to incomplete type
  if (vma->vm_mm && vma->vm_start == (long)vma->vm_mm->context.vdso)
                                              ^
  CHECK   /home/hpa/kernel/distwork/block/elevator.c
make[4]: *** [arch/x86/vdso/vdso32-setup.o] Error 1

	-hpa

--
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/