linux-2.6-xen

linux-2.6-xen

[Shaun Reitan]

I'm using Jeremy's kernel branch and attempting to compile a kernel on 
CentOS6 x86_64.  I keep running into the following error

   CC      arch/x86/xen/mmu.o
arch/x86/xen/mmu.c:163: error: __pcpu_scope_xen_cr3 causes a section 
type conflict
arch/x86/xen/mmu.c:164: error: __pcpu_scope_xen_current_cr3 causes a 
section type conflict
arch/x86/xen/mmu.c:163: error: __pcpu_unique_xen_cr3 causes a section 
type conflict
arch/x86/xen/mmu.c:164: error: __pcpu_unique_xen_current_cr3 causes a 
section type conflict
make[2]: *** [arch/x86/xen/mmu.o] Error 1
make[1]: *** [arch/x86/xen] Error 2
make: *** [arch/x86] Error 2


I'm using the kernel config from centos6's default kernel but then 
modifying the config to enable the dom0 features.

Kernel config from centos6 is config-2.6.32-71.29.1.el6.x86_64, reason 
i'm using it is because it's from 2.6.32.x..

Anybody know what might be going on here?

--
~ShaunR

Re: linux-2.6-xen

[Pasi Kärkkäinen]

On Wed, Jul 13, 2011 at 11:59:33AM -0700, Shaun Reitan wrote:
> I'm using Jeremy's kernel branch and attempting to compile a kernel on  
> CentOS6 x86_64.  I keep running into the following error
>
>   CC      arch/x86/xen/mmu.o
> arch/x86/xen/mmu.c:163: error: __pcpu_scope_xen_cr3 causes a section  
> type conflict
> arch/x86/xen/mmu.c:164: error: __pcpu_scope_xen_current_cr3 causes a  
> section type conflict
> arch/x86/xen/mmu.c:163: error: __pcpu_unique_xen_cr3 causes a section  
> type conflict
> arch/x86/xen/mmu.c:164: error: __pcpu_unique_xen_current_cr3 causes a  
> section type conflict
> make[2]: *** [arch/x86/xen/mmu.o] Error 1
> make[1]: *** [arch/x86/xen] Error 2
> make: *** [arch/x86] Error 2
>
>
> I'm using the kernel config from centos6's default kernel but then  
> modifying the config to enable the dom0 features.
>
> Kernel config from centos6 is config-2.6.32-71.29.1.el6.x86_64, reason  
> i'm using it is because it's from 2.6.32.x..
>
> Anybody know what might be going on here?
>

Did you try using the prebuilt rpms?

xen rpms: http://xenbits.xen.org/people/mayoung/EL6.xen/
dom0 kernel rpms: http://xenbits.xen.org/people/mayoung/testing/

Taken from: http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial

-- Pasi

Re: linux-2.6-xen

[Shaun Reitan]

No, I prefer to role my own. I will take a look at his kernel configs 
but still would like to find out what might be going on.

~ShaunR

RE: Re: linux-2.6-xen

[Huang2, Wei]

It was reported before and seemed to be related to your gcc.

http://xen.1045712.n5.nabble.com/Compile-pvops-kernel-xen-stable-2-6-32-x-error-td3239070.html

-Wei

-----Original Message-----
From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Shaun Reitan
Sent: Wednesday, July 13, 2011 3:32 PM
To: xen-devel@lists.xensource.com
Subject: [Xen-devel] Re: linux-2.6-xen

No, I prefer to role my own. I will take a look at his kernel configs 
but still would like to find out what might be going on.

~ShaunR


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: linux-2.6-xen

[Jean Guyader]

On 13 July 2011 19:59, Shaun Reitan <mailinglists@unix-scripts.com> wrote:
> I'm using Jeremy's kernel branch and attempting to compile a kernel on
> CentOS6 x86_64.  I keep running into the following error
>
>  CC      arch/x86/xen/mmu.o
> arch/x86/xen/mmu.c:163: error: __pcpu_scope_xen_cr3 causes a section type
> conflict
> arch/x86/xen/mmu.c:164: error: __pcpu_scope_xen_current_cr3 causes a section
> type conflict
> arch/x86/xen/mmu.c:163: error: __pcpu_unique_xen_cr3 causes a section type
> conflict
> arch/x86/xen/mmu.c:164: error: __pcpu_unique_xen_current_cr3 causes a
> section type conflict
> make[2]: *** [arch/x86/xen/mmu.o] Error 1
> make[1]: *** [arch/x86/xen] Error 2
> make: *** [arch/x86] Error 2
>
>
> I'm using the kernel config from centos6's default kernel but then modifying
> the config to enable the dom0 features.
>
> Kernel config from centos6 is config-2.6.32-71.29.1.el6.x86_64, reason i'm
> using it is because it's from 2.6.32.x..
>
> Anybody know what might be going on here?
>

Hi,

I think I saw the same failure not so long ago.
You should try to remove CONFIG_DEBUG_FORCE_WEAK_PER_CPU from your
kernel config.

Jean