From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ritu kaur Subject: Re: domU guest for xcp 0.1.1 Date: Mon, 15 Mar 2010 06:42:30 -0700 Message-ID: <29b32d341003150642o4e2620edsf154b19d78aa7f42@mail.gmail.com> References: <29b32d341003120910l5340bc01tcada3ca2adbaf763@mail.gmail.com> <29b32d341003130809u49d1edcas234fdca4c3d70ed@mail.gmail.com> <20100313164102.GZ1878@reaktio.net> <29b32d341003131743j6ae271d6of486a3c1a4858513@mail.gmail.com> <112460240.20100314121540@eikelenboom.it> <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com> <1056770753.20100314215224@eikelenboom.it> <29b32d341003141840x5a55e74sfb2eda56005e4f84@mail.gmail.com> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@mail.gmail.com> <1268642688.8652.2792.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1567620191==" Return-path: In-Reply-To: <1268642688.8652.2792.camel@localhost.localdomain> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org --===============1567620191== Content-Type: multipart/alternative; boundary=000e0cd13bca7957c70481d70ddc --000e0cd13bca7957c70481d70ddc Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Ian, Thanks. Should I use DDK to compile my drivers? I have pci device listed in domU and drivers are not compilable there hence wondering how do I use the it? Thanks On Mon, Mar 15, 2010 at 1:44 AM, Ian Campbell wrot= e: > On Mon, 2010-03-15 at 03:30 +0000, Ritu kaur wrote: > > Just to add, this driver compiles fine in other linux flavors(Debian > > Lenny 5.0, Citrix Xenserver...) so it has to do with Xen/stable. > > Didn't see anything related to this in xen-devel, inputs appreciated. > > This is because the pvops kernel is based on a much newer upstream > kernel (2.6.31 or 32) than that found in Lenny (2.6.26) or Citrix > XenServer (2.6.18/27) and some of the kernel's internal interfaces must > have changed. > > This has nothing to do with Xen per-se but rather compatibility with > different Linux kernels. > > Ian. > > > > > Thanks > > > > On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur > > wrote: > > Hi Pasi, > > > > I am able to use xen/stable kernel in domU(debian lenny) and > > lspci lists the device(i am testing pci passthrough). however, > > when I compile my driver in domU I get > > > > struct net_device has no member named open > > struct net_device has no member named stop > > struct net_device has no member named hard_start_xmit > > ... > > > > I need to compile my driver in domU and load it in order to > > use the nic from domU. Inputs appreciated. > > > > Thanks > > > > > > > > On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom > > wrote: > > Hello Ritu, > > > > I don't have experience with XCP specifically, but > > normal compiled pvops-kernels work fine for me with > > Debian lenny domU's. > > > > -- > > Sander > > > > > > Sunday, March 14, 2010, 9:29:29 PM, you wrote: > > > > > Hi Sander, > > > > > Thanks, I enabled DOM0 and other backend drivers > > along with pci frontend in > > > .config file. I am able to get it build. However, I > > having additional > > > questions, inputs appreciated. > > > > > 1. can this kernel be used in any linux > > distribution? I have Debian Lenny as > > > DomU? > > > > > 2. In Debian Lenny /boot/grub/menu.lst, I have > > > title Debian GNU/Linux, kernel > > 2.6.26-2-686-bigmem > > > root (hd0,0) > > > kernel /boot/vmlinuz-2.6.26-2-686-bigmem > > root=3D/dev/xvda1 ro > > > console=3Dhvc0 quiet > > > initrd /boot/initrd.img-2.6.26-2-686-bigmem > > > > > but the kernel image built in arch/i386/boot is > > bzImage. Does "make > > > modules_install" and "make install" take care of it, > > since I am not sure I > > > haven't tried it. > > > > > Basically, my question boils down to > > > > > 1. Can I use bzImage in debian lenny, > > > 2. does make install take care of configuring it > > > > > > > Thanks > > > > > On Sun, Mar 14, 2010 at 4:15 AM, Sander Eikelenboom > > wrote: > > > > >> Hello Ritu, > > >> > > >> There are some problems with pci.h, i have also > > reported this to Konrad. > > >> As a workaround you can enable dom0 support in > > these kernels, then they > > >> compile fine in my case. > > >> > > >> -- > > >> > > >> Sander > > >> > > >> > > >> Sunday, March 14, 2010, 2:43:23 AM, you wrote: > > >> > > >> > I followed the steps mentioned in wiki to pull > > xen code to compile domU > > >> > kernel from > > >> > > >> > 1. xen/master, I get following compilation > > errors. I do see in xen-devel > > >> > forum someone else has reported similar issue but > > no solution yet(patch > > >> > provided by Konrad has followup errors) > > >> > > >> > CC [M] drivers/watchdog/machzwd.o > > >> > CC [M] drivers/watchdog/sbc_epx_c3.o > > >> > CC [M] drivers/watchdog/softdog.o > > >> > CC drivers/xen/grant-table.o > > >> > CC drivers/xen/features.o > > >> > CC drivers/xen/events.o > > >> > drivers/xen/events.c:605: error: redefinition of > > =E2=80=98xen_destroy_irq=E2=80=99 > > >> > > > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:29: error: > > >> > previous definition of =E2=80=98xen_destroy_irq=E2= =80=99 was > > here > > >> > drivers/xen/events.c:637: error: redefinition of > > =E2=80=98xen_create_msi_irq=E2=80=99 > > >> > > > > /root/kernel/linux.2-6.xen/arch/x86/include/asm/xen/pci.h:25: error: > > >> > previous definition of =E2=80=98xen_create_msi_irq= =E2=80=99 > > was here > > >> > make[2]: *** [drivers/xen/events.o] Error 1 > > >> > make[1]: *** [drivers/xen] Error 2 > > >> > make: *** [drivers] Error 2 > > >> > > >> > 2. xen/stable, I get following errors > > >> > > >> > CC drivers/pci/xen-pcifront.o > > >> > drivers/pci/xen-pcifront.c:373: error: variable = =E2 > > =80=98pci_frontend_ops=E2=80=99 > > >> has > > >> > initializut incomplete type > > >> > drivers/pci/xen-pcifront.c:374: error: unknown > > field =E2=80=98enable_msi=E2=80=99 > > >> > specified in ializer > > >> > drivers/pci/xen-pcifront.c:374: warning: excess > > elements in struct > > >> > initializer > > >> > drivers/pci/xen-pcifront.c:374: warning: (near > > initialization for > > >> > =E2=80=98pci_frontend_op)=E2=80=99 > > >> > drivers/pci/xen-pcifront.c:375: error: unknown > > field =E2=80=98disable_msi=E2=80=99 > > >> > specified in ializer > > >> > drivers/pci/xen-pcifront.c:375: warning: excess > > elements in struct > > >> > initializer > > >> > drivers/pci/xen-pcifront.c:375: warning: (near > > initialization for > > >> > =E2=80=98pci_frontend_op)=E2=80=99 > > >> > drivers/pci/xen-pcifront.c:376: error: unknown > > field =E2=80=98enable_msix=E2=80=99 > > >> > specified in ializer > > >> > drivers/pci/xen-pcifront.c:376: warning: excess > > elements in struct > > >> > initializer > > >> > drivers/pci/xen-pcifront.c:376: warning: (near > > initialization for > > >> > =E2=80=98pci_frontend_op)=E2=80=99 > > >> > drivers/pci/xen-pcifront.c:377: error: unknown > > field =E2=80=98disable_msix=E2=80=99 > > >> > specified intializer > > >> > drivers/pci/xen-pcifront.c:377: warning: excess > > elements in struct > > >> > initializer > > >> > drivers/pci/xen-pcifront.c:377: warning: (near > > initialization for > > >> > =E2=80=98pci_frontend_op)=E2=80=99 > > >> > drivers/pci/xen-pcifront.c: In function =E2 > > =80=98pci_frontend_registrar=E2=80=99: > > >> > drivers/pci/xen-pcifront.c:383: error: =E2 > > =80=98xen_pci_frontend=E2=80=99 undeclared > > >> > (first use his function) > > >> > drivers/pci/xen-pcifront.c:383: error: (Each > > undeclared identifier is > > >> > reported only once > > >> > drivers/pci/xen-pcifront.c:383: error: for each > > function it appears in.) > > >> > make[2]: *** [drivers/pci/xen-pcifront.o] Error 1 > > >> > make[1]: *** [drivers/pci] Error 2 > > >> > make: *** [drivers] Error 2 > > >> > > >> > Kindly let me know how to proceed on this. > > >> > > >> > Thanks > > >> > > >> > > >> > > >> -- > > >> Best regards, > > >> Sander > > mailto:linux@eikelenboom.it > > >> > > >> > > > > > > > > > > -- > > > > Best regards, > > Sander > > mailto:linux@eikelenboom.it > > > > > > > > > > > > > --000e0cd13bca7957c70481d70ddc Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Ian,

Thanks. Should I use DDK to compile my drivers? I have pci d= evice listed in domU and drivers are not compilable there hence wondering h= ow do I use the it?

Thanks

On Mon= , Mar 15, 2010 at 1:44 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:=
On Mon, 2010-03-15 at 03:30 +0000, Ritu kaur wrote:
> Just to add, this driver compiles fine in other linux flavors(Debian > Lenny 5.0, Citrix Xenserver...) so it has to do with Xen/stable.
> Didn't see anything related to this in xen-devel, inputs appreciat= ed.

This is because the pvops kernel is based on a much newer upstream kernel (2.6.31 or 32) than that found in Lenny (2.6.26) or Citrix
XenServer (2.6.18/27) and some of the kernel's internal interfaces must=
have changed.

This has nothing to do with Xen per-se but rather compatibility with
different Linux kernels.

Ian.

>
> Thanks
>
> On Sun, Mar 14, 2010 at 6:40 PM, Ritu kaur <ritu.kaur.us@gmail.com>
> wrote:
> =A0 =A0 =A0 =A0 Hi Pasi,
>
> =A0 =A0 =A0 =A0 I am able to use xen/stable kernel in domU(debian lenn= y) and
> =A0 =A0 =A0 =A0 lspci lists the device(i am testing pci passthrough). = however,
> =A0 =A0 =A0 =A0 when I compile my driver in domU I get
>
> =A0 =A0 =A0 =A0 struct net_device has no member named open
> =A0 =A0 =A0 =A0 struct net_device has no member named stop
> =A0 =A0 =A0 =A0 struct net_device has no member named hard_start_xmit<= br> > =A0 =A0 =A0 =A0 ...
>
> =A0 =A0 =A0 =A0 I need to compile my driver in domU and load it in ord= er to
> =A0 =A0 =A0 =A0 use the nic from domU. Inputs appreciated.
>
> =A0 =A0 =A0 =A0 Thanks
>
>
>
> =A0 =A0 =A0 =A0 On Sun, Mar 14, 2010 at 1:52 PM, Sander Eikelenboom > =A0 =A0 =A0 =A0 <linux@eike= lenboom.it> wrote:
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Hello Ritu,
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 I don't have experience with XCP s= pecifically, but
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 normal compiled pvops-kernels work fin= e for me with
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Debian lenny domU's.
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 --
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Sander
>
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Sunday, March 14, 2010, 9:29:29 PM, yo= u wrote:
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Hi Sander,
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Thanks, I enabled DOM0 and other = backend drivers
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 along with pci frontend in
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > .config file. I am able to get it= build. However, I
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 having additional
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > questions, inputs appreciated. >
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 1. can this kernel be used in any= linux
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 distribution? I have Debian Lenny as > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > DomU?
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 2. In Debian Lenny /boot/grub/men= u.lst, I have
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > title =A0 =A0 =A0 =A0 =A0 Debian = GNU/Linux, kernel
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 2.6.26-2-686-bigmem
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > root =A0 =A0 =A0 =A0 =A0 =A0(hd0,= 0)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > kernel =A0 =A0 =A0 =A0 =A0/boot/v= mlinuz-2.6.26-2-686-bigmem
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 root=3D/dev/xvda1 ro
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > console=3Dhvc0 quiet
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > initrd =A0 =A0 =A0 =A0 =A0/boot/i= nitrd.img-2.6.26-2-686-bigmem
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > but the kernel image built in arc= h/i386/boot is
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 bzImage. Does "make
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > modules_install" and "m= ake install" take care of it,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 since I am not sure I
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > haven't tried it.
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Basically, my question boils down= to
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 1. Can I use bzImage in debian le= nny,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > 2. does make install take care of= configuring it
>
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > Thanks
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > On Sun, Mar 14, 2010 at 4:15 AM, = Sander Eikelenboom
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <linux@eikelenboom.it>wrote:
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Hello Ritu,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> There are some problems with = pci.h, i have also
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 reported this to Konrad.
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> As a workaround you can enabl= e dom0 support in
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 these kernels, then they
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> compile fine in my case.
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> --
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Sander
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Sunday, March 14, 2010, 2:43:= 23 AM, you wrote:
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > I followed the steps men= tioned in =A0wiki to pull
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 xen code to compile domU
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > kernel from
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > 1. xen/master, I get fol= lowing compilation
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 errors. I do see in xen-devel
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > forum someone else has r= eported similar issue but
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 no solution yet(patch
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > provided by Konrad has f= ollowup errors)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > CC [M] =A0drivers/watchd= og/machzwd.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0 CC [M] =A0drivers/wa= tchdog/sbc_epx_c3.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0 CC [M] =A0drivers/wa= tchdog/softdog.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0 CC =A0 =A0 =A0driver= s/xen/grant-table.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0 CC =A0 =A0 =A0driver= s/xen/features.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0 CC =A0 =A0 =A0driver= s/xen/events.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/xen/events.c:605= : error: redefinition of
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =E2=80=98xen_destroy_irq=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > /root/kernel/linux.2-6.xen/arch/x= 86/include/asm/xen/pci.h:29: error:
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > previous definition of = =E2=80=98xen_destroy_irq=E2=80=99 was
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 here
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/xen/events.c:637= : error: redefinition of
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =E2=80=98xen_create_msi_irq=E2=80=99 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 > /root/kernel/linux.2-6.xen/arch/x= 86/include/asm/xen/pci.h:25: error:
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > previous definition of = =E2=80=98xen_create_msi_irq=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 was here
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > make[2]: *** [drivers/xe= n/events.o] Error 1
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > make[1]: *** [drivers/xe= n] Error 2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > make: *** [drivers] Erro= r 2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > 2. xen/stable, I get fol= lowing errors
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =A0CC =A0 =A0 =A0drivers= /pci/xen-pcifront.o
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:373: error: variable =E2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =80=98pci_frontend_ops=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> has
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > initializut incomplete t= ype
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:374: error: unknown
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98enable_msi=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > specified in ializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:374: warning: excess
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struct
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > initializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:374: warning: (near
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization for
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2=80=98pci_frontend_op= )=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:375: error: unknown
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98disable_msi=E2=80=99 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > specified in ializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:375: warning: excess
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struct
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > initializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:375: warning: (near
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization for
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2=80=98pci_frontend_op= )=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:376: error: unknown
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98enable_msix=E2=80=99 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > specified in ializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:376: warning: excess
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struct
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > initializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:376: warning: (near
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization for
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2=80=98pci_frontend_op= )=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:377: error: unknown
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 field =E2=80=98disable_msix=E2=80=99 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > specified intializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:377: warning: excess
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 elements in struct
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > initializer
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:377: warning: (near
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 initialization for
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > =E2=80=98pci_frontend_op= )=E2=80=99
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c: In function =E2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =80=98pci_frontend_registrar=E2=80=99:=
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:383: error: =E2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =80=98xen_pci_frontend=E2=80=99 undecl= ared
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > (first use his function)=
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:383: error: (Each
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 undeclared identifier is
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > reported only once
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > drivers/pci/xen-pcifront= .c:383: error: for each
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 function it appears in.)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > make[2]: *** [drivers/pc= i/xen-pcifront.o] Error 1
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > make[1]: *** [drivers/pc= i] Error 2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > make: *** [drivers] Erro= r 2
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > Kindly let me know how t= o proceed on this.
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> > Thanks
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> --
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> Best regards,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >> =A0Sander
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mailto:linux@eikelenboom.it
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 >>
>
>
>
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 --
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Best regards,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Sander
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0mailto:linux@eikelenboom.it
>
>
>
>
>



--000e0cd13bca7957c70481d70ddc-- --===============1567620191== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1567620191==--