April 2013 - kernelnewbies@kernelnewbies.org - Kernelnewbies Mailing Lists

[ARM-LINUX]Init process is not getting launched while bringing up an opensource kernel on Qualcomm board...
by sandeep kumar April 19, 2013

April 19, 2013

Hi All I am doing a open-source kernel bringup on Qualcomm board. I reached till the successfull kernel initialization complete, and i can see the run_init_process() function executing successfully. But still i am not seeing my init process is not launched. Here are the following check points...i did, 1) I made a ramdisk image with the init process code, like this.... int main() { return 0; } 2) With the same ramdisk.img(which contains my init process(a return; statement in the main()) and another kernel i can see init process launch is successful. (in the kernel logs i am seeing panic message: Trying to kill init!! ) 3) In my bringup kernel, The similer kind of message is not seen. I can see ramdisk uncompression successful and also.. I have kept logs in arch/arm/kernel/sys_arm.c in the function kernel_execv() and i observed do_execv() function call is successful. Can anyone help me, am i missing something?? Please give me pointers on how to proceed. -- With regards, Sandeep Kumar Anantapalli,

2 3

scheduler context
by ratheesh kannoth April 18, 2013

April 18, 2013

I would like to understand on linux scheduler context. I have read a lot in websites and i could find contradictory statement. There are so many mailing list also ,but with less info. I would really appreciate if anybody could spend some time answering my question. 1. Which context scheduler run ? ( process context or interrupt context ). 2. scheduler is the guy who picks up the next candidate to run. if it gets interrupted by hardirq, what will happen ? 3. if scheduler run in process context , how bottom half are scheduled ? 4. In smp, schedule() function may be called simultaneously. How it is handled ? 5. When a bottom half is interrupted by hard irq, how softirq kernel thread saves the state and restart it later ? ...what i mean is , an hardirq came and its isr executed. bottom half enabled and bottom half gets scheduled . Before bottom half is completed , next irq came and it enables bottom half , and the new bottom half is scheduled ....So here , what will happen to old bottom half , will it again run later ? Thanks, Ratheesh

2 1

RE: linux-3.8.7 64bit build
by Giridhara RP (grp) April 18, 2013

April 18, 2013

I was using wrong compiler. 1. Changed compiler to 64bit 2. Changed Ld to 64 bit. So, its good if we run make command under linux 64 bit. From: Giridhara RP (grp) Sent: Thursday, April 18, 2013 1:42 PM To: 'kernelnewbies(a)kernelnewbies.org' Subject: linux-3.8.7 64bit build Hi, I am trying to build 64bit linux. .config file got created. But while compiling I get the error "unimplemented: 64-bit mode not compiled in". Any pointers much appreciated. Step2: bash-3.00$ make V=1 CC="gcc.c4.5.3-p0.linux" ARCH=x86_64 gcc.c4.5.3-p0.linux -Wp,-MD,kernel/.bounds.s.d -nostdinc -isystem /auto/sw/packages/gcc/c4.5.3-p0/i686-pc-linux/bin/../lib/gcc/i686-pc-linux/4.5.3/include -I/iws/grp-1/Linux_ker/linux-3.8.7/arch/x86/include -Iarch/x86/include/generated -Iinclude -I/iws/grp-1/Linux_ker/linux-3.8.7/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/iws/grp-1/Linux_ker/linux-3.8.7/include/uapi -Iinclude/generated/uapi -include /iws/grp-1/Linux_ker/linux-3.8.7/include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mno-red-zone -mcmodel=kernel -maccumulate-outgoing-args -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_AVX=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -fno-optimize-sibling-calls -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(bounds)" -D"KBUILD_MODNAME=KBUILD_STR(bounds)" -fverbose-asm -S -o kernel/bounds.s kernel/bounds.c kernel/bounds.c:1:0: error: code model âkernelâ not supported in the 32 bit mode <===Error here kernel/bounds.c:1:0: sorry, unimplemented: 64-bit mode not compiled in <==== Error here make-3.79.1-p7[1]: *** [kernel/bounds.s] Error 1 make-3.79.1-p7: *** [prepare0] Error 2 bash-3.00$ Step1: bash-3.00$ make V=1 CC="gcc.c4.5.3-p0.x86elf" ARCH=x86_64 x86_64_defconfig make-3.79.1-p7 -f scripts/Makefile.build obj=scripts/basic rm -f .tmp_quiet_recordmcount mkdir -p include/linux include/config make-3.79.1-p7 -f scripts/Makefile.build obj=scripts/kconfig x86_64_defconfig scripts/kconfig/conf --defconfig=arch/x86/configs/x86_64_defconfig Kconfig # # configuration written to .config #

1 0

linux-3.8.7 64bit build
by Giridhara RP (grp) April 18, 2013

April 18, 2013

Hi, I am trying to build 64bit linux. .config file got created. But while compiling I get the error "unimplemented: 64-bit mode not compiled in". Any pointers much appreciated. Step2: bash-3.00$ make V=1 CC="gcc.c4.5.3-p0.linux" ARCH=x86_64 gcc.c4.5.3-p0.linux -Wp,-MD,kernel/.bounds.s.d -nostdinc -isystem /auto/sw/packages/gcc/c4.5.3-p0/i686-pc-linux/bin/../lib/gcc/i686-pc-linux/4.5.3/include -I/iws/grp-1/Linux_ker/linux-3.8.7/arch/x86/include -Iarch/x86/include/generated -Iinclude -I/iws/grp-1/Linux_ker/linux-3.8.7/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/iws/grp-1/Linux_ker/linux-3.8.7/include/uapi -Iinclude/generated/uapi -include /iws/grp-1/Linux_ker/linux-3.8.7/include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mno-red-zone -mcmodel=kernel -maccumulate-outgoing-args -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_AVX=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -fno-optimize-sibling-calls -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(bounds)" -D"KBUILD_MODNAME=KBUILD_STR(bounds)" -fverbose-asm -S -o kernel/bounds.s kernel/bounds.c kernel/bounds.c:1:0: error: code model âkernelâ not supported in the 32 bit mode <===Error here kernel/bounds.c:1:0: sorry, unimplemented: 64-bit mode not compiled in <==== Error here make-3.79.1-p7[1]: *** [kernel/bounds.s] Error 1 make-3.79.1-p7: *** [prepare0] Error 2 bash-3.00$ Step1: bash-3.00$ make V=1 CC="gcc.c4.5.3-p0.x86elf" ARCH=x86_64 x86_64_defconfig make-3.79.1-p7 -f scripts/Makefile.build obj=scripts/basic rm -f .tmp_quiet_recordmcount mkdir -p include/linux include/config make-3.79.1-p7 -f scripts/Makefile.build obj=scripts/kconfig x86_64_defconfig scripts/kconfig/conf --defconfig=arch/x86/configs/x86_64_defconfig Kconfig # # configuration written to .config #

1 0

Re: Build error in linux-3.8.7
by Sarbojit Ganguly April 18, 2013

April 18, 2013

On 18 April 2013 09:22, Giridhara RP (grp) <grp(a)cisco.com> wrote: > Hi Sarbojit,**** > > ** ** > > Builng kernel with gcc-4.5+ solved all the major issues (compile error and > Segmentation Fault). Regarding bnx2, our board does not have bnx2. So, I > commented ‘CONFIG_BNX2’ in .config file. > Good :-) > **** > > ** ** > > Thanks**** > > Giri**** > > ** ** > > *From:* Sarbojit Ganguly [mailto:unixman.linuxboy@gmail.com] > *Sent:* Wednesday, April 17, 2013 5:43 PM > > *To:* Giridhara RP (grp) > *Cc:* kernelnewbies(a)kernelnewbies.org > *Subject:* Re: Build error in linux-3.8.7**** > > ** ** > > ** ** > > ** ** > > On 17 April 2013 15:38, Giridhara RP (grp) <grp(a)cisco.com> wrote:**** > > Thanks guys J. Finally I have a successful build.**** > > ** ** > > Sorry, checked late, do share the reason and solution. It might help > others who are facing similar problem. > > **** > > Giri**** > > **** > > *From:* kernelnewbies-bounces(a)kernelnewbies.org [mailto: > kernelnewbies-bounces(a)kernelnewbies.org] *On Behalf Of *Giridhara RP (grp) > *Sent:* Wednesday, April 17, 2013 1:42 PM**** > > > *To:* Sarbojit Ganguly > *Cc:* kernelnewbies(a)kernelnewbies.org > *Subject:* RE: Build error in linux-3.8.7**** > > **** > > Hi,**** > > **** > > I am getting error in firmware. Any pointer will be helpful. Segmetation > fault is gone after changning to gcc-4.5**** > > **** > > make-3.79.1-p7[1]: Nothing to be done for `all'.**** > > CHK include/generated/uapi/linux/version.h**** > > make-3.79.1-p7[1]: Nothing to be done for `relocs'.**** > > CHK include/generated/utsrelease.h**** > > CALL scripts/checksyscalls.sh**** > > *make-3.79.1-p7[1]: *** No rule to make target `|', needed by > `firmware/bnx2/bnx2-mips-09-6.2.1a.fw.gen.S'. Stop.***** > > *make-3.79.1-p7: *** [firmware] Error 2***** > > make-3.79.1-p7: *** Waiting for unfinished jobs....**** > > CHK include/generated/compile.h**** > > PASYMS arch/x86/realmode/rm/pasyms.h**** > > VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds**** > > LDS arch/x86/realmode/rm/realmode.lds**** > > LD arch/x86/realmode/rm/realmode.elf**** > > RELOCS arch/x86/realmode/rm/realmode.relocs**** > > OBJCOPY arch/x86/realmode/rm/realmode.bin**** > > VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds**** > > AS arch/x86/realmode/rmpiggy.o**** > > VDSOSYM arch/x86/vdso/vdso32-syms.lds**** > > LD arch/x86/realmode/built-in.o**** > > LD arch/x86/vdso/built-in.o**** > > LD arch/x86/built-in.o**** > > make-3.79.1-p7: *** wait: No child processes. Stop.**** > > bash-3.00$**** > > **** > > Thanks**** > > Giri**** > > **** > > *From:* kernelnewbies-bounces(a)kernelnewbies.org [ > mailto:kernelnewbies-bounces@kernelnewbies.org<kernelnewbies-bounces(a)kernelnewbies.org>] > *On Behalf Of *Giridhara RP (grp) > *Sent:* Wednesday, April 17, 2013 12:33 PM > *To:* Sarbojit Ganguly > *Cc:* kernelnewbies(a)kernelnewbies.org > *Subject:* RE: Build error in linux-3.8.7**** > > **** > > Hi Sarbojit,**** > > **** > > Using gcc4.2.1 the compilation error disaappered, but now linker (ld) is > crashing. Any workaround to overcome this?**** > > **** > > CHK include/generated/uapi/linux/version.h**** > > CHK include/generated/utsrelease.h**** > > CALL scripts/checksyscalls.sh**** > > CHK include/generated/compile.h**** > > LD arch/x86/kernel/built-in.o**** > > /bin/sh: line 1: 17454 Segmentation fault ld -m elf_i386 -r -o > arch/x86/kernel/built-in.o arch/x86/kernel/process_32.o > arch/x86/kernel/signal.o arch/x86/kernel/entry_32.o arch/x86/kernel/traps.o > arch/x86/kernel/irq.o arch/x86/kernel/irq_32.o > arch/x86/kernel/dumpstack_32.o arch/x86/kernel/time.o > arch/x86/kernel/ioport.o arch/x86/kernel/ldt.o arch/x86/kernel/dumpstack.o > arch/x86/kernel/nmi.o arch/x86/kernel/setup.o arch/x86/kernel/x86_init.o > arch/x86/kernel/i8259.o arch/x86/kernel/irqinit.o > arch/x86/kernel/jump_label.o arch/x86/kernel/irq_work.o > arch/x86/kernel/probe_roms.o arch/x86/kernel/i386_ksyms_32.o > arch/x86/kernel/syscall_32.o arch/x86/kernel/bootflag.o > arch/x86/kernel/e820.o arch/x86/kernel/pci-dma.o arch/x86/kernel/quirks.o > arch/x86/kernel/topology.o arch/x86/kernel/kdebugfs.o > arch/x86/kernel/alternative.o arch/x86/kernel/i8253.o > arch/x86/kernel/pci-nommu.o arch/x86/kernel/hw_breakpoint.o > arch/x86/kernel/tsc.o arch/x86/kernel/io_delay.o arch/x86/kernel/rtc.o > arch/x86/kernel/pci-iommu_table.o arch/x86/kernel/resource.o > arch/x86/kernel/process.o arch/x86/kernel/i387.o arch/x86/kernel/xsave.o > arch/x86/kernel/ptrace.o arch/x86/kernel/tls.o arch/x86/kernel/step.o > arch/x86/kernel/i8237.o arch/x86/kernel/stacktrace.o > arch/x86/kernel/cpu/built-in.o arch/x86/kernel/acpi/built-in.o > arch/x86/kernel/reboot.o arch/x86/kernel/msr.o arch/x86/kernel/cpuid.o > arch/x86/kernel/early-quirks.o arch/x86/kernel/smp.o > arch/x86/kernel/smpboot.o arch/x86/kernel/tsc_sync.o > arch/x86/kernel/setup_percpu.o arch/x86/kernel/mpparse.o > arch/x86/kernel/apic/built-in.o arch/x86/kernel/reboot_fixups_32.o > arch/x86/kernel/trace_clock.o arch/x86/kernel/machine_kexec_32.o > arch/x86/kernel/relocate_kernel_32.o arch/x86/kernel/crash.o > arch/x86/kernel/crash_dump_32.o arch/x86/kernel/kprobes.o > arch/x86/kernel/kprobes-opt.o arch/x86/kernel/module.o > arch/x86/kernel/doublefault_32.o arch/x86/kernel/vm86_32.o > arch/x86/kernel/early_printk.o arch/x86/kernel/hpet.o > arch/x86/kernel/amd_nb.o arch/x86/kernel/pcspeaker.o > arch/x86/kernel/microcode.o arch/x86/kernel/check.o > arch/x86/kernel/perf_regs.o**** > > make-3.79.1-p7[2]: *** [arch/x86/kernel/built-in.o] Error 139**** > > make-3.79.1-p7[1]: *** [arch/x86/kernel] Error 2**** > > make-3.79.1-p7: *** [arch/x86] Error 2**** > > **** > > bash-3.00$ uname -a**** > > Linux sam-build01.cisco.com 2.6.9-89.ELsmp #1 SMP Mon Jun 22 12:32:43 EDT > 2009 i686 i686 i386 GNU/Linux**** > > **** > > bash-3.00$ ld --version**** > > GNU ld version 2.15.92.0.2 20040927**** > > Copyright 2002 Free Software Foundation, Inc.**** > > This program is free software; you may redistribute it under the terms of* > *** > > the GNU General Public License. This program has absolutely no warranty.* > *** > > **** > > *From:* kernelnewbies-bounces(a)kernelnewbies.org [ > mailto:kernelnewbies-bounces@kernelnewbies.org<kernelnewbies-bounces(a)kernelnewbies.org>] > *On Behalf Of *Giridhara RP (grp) > *Sent:* Wednesday, April 17, 2013 11:35 AM > *To:* Sarbojit Ganguly > *Cc:* kernelnewbies(a)kernelnewbies.org > *Subject:* RE: Build error in linux-3.8.7**** > > **** > > Hi Sarbojit,**** > > **** > > My gcc is 3.4.6-11. Sure, I will try 3.8.8**** > > **** > > bash-3.00$ gcc --version**** > > gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-11)**** > > Copyright (C) 2006 Free Software Foundation, Inc.**** > > This is free software; see the source for copying conditions. There is NO > **** > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > **** > > **** > > *From:* Sarbojit Ganguly [mailto:unixman.linuxboy@gmail.com<unixman.linuxboy(a)gmail.com>] > > *Sent:* Wednesday, April 17, 2013 11:34 AM > *To:* Giridhara RP (grp) > *Cc:* kernelnewbies(a)kernelnewbies.org > *Subject:* Re: Build error in linux-3.8.7**** > > **** > > Hello GRP,**** > > **** > > Can you post your toolchain (gcc) version? As you're doing this, may I > request you to try with 3.8.8?**** > > **** > > Regards,**** > > Sarbojit**** > > **** > > On 17 April 2013 10:20, Giridhara RP (grp) <grp(a)cisco.com> wrote:**** > > Hi,**** > > **** > > I am new to linux kernel buidling. I have download 3.8.7 latest (stable) > kernel from https://www.kernel.org/. I want build kernel for X86_64.**** > > **** > > 1. make x86_64_defconfig (this created .config file)**** > > 2. make**** > > Make failed with below error, please help me in resolving this.**** > > **** > > CC kernel/power/user.o**** > > CC kernel/power/block_io.o**** > > CC kernel/power/poweroff.o**** > > LD kernel/power/built-in.o**** > > CC kernel/sched/core.o**** > > CC kernel/sched/clock.o**** > > CC kernel/sched/cputime.o**** > > CC kernel/sched/idle_task.o**** > > CC kernel/sched/fair.o**** > > kernel/sched/fair.c: In function `update_curr':**** > > kernel/sched/fair.c:428: sorry, unimplemented: inlining failed in call to > 'account_cfs_rq_runtime': function body not available**** > > kernel/sched/fair.c:714: sorry, unimplemented: called from here**** > > make-3.79.1-p7[2]: *** [kernel/sched/fair.o] Error 1**** > > make-3.79.1-p7[1]: *** [kernel/sched] Error 2**** > > make-3.79.1-p7: *** [kernel] Error 2**** > > bash-3.00$ pwd**** > > **** > > thanks**** > > Giri**** > > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies(a)kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies**** > > > > **** > > **** > > -- > Regards, > Sarbojit **** > > > > > -- > Regards, > Sarbojit **** > -- Regards, Sarbojit

1 0

net_device: limit rate ot tx packets
by christian+kn＠wwad.de April 17, 2013

April 17, 2013

Hi All, can someone please explain me, how the kernel handles different transfer rates of different net_devices? Or in other words: How does the systemcall send() know, when to block? An example: cat /dev/zero | pv | nc -u <someip> will show different throughput speeds depending on the network device, the packets are sent over (wlan0 will be slower than eth0). - Can someone point out the location in the linux kernel source, where this is handled? - If I register a net_device. How do I signal to the upper network layers that my driver can only accept packets at a certain rate? I tried stopping the egress queue by calling netif_stop_queue(), but this only has the effect that the queue overruns. I have the feeling that I'm missing out a very vital point on how the kernel's networking subsystem works. Unfortunately, Understanding Linux Network Internals couldn't help me out here. Thanks, Christian

3 5

Build error in linux-3.8.7
by Giridhara RP (grp) April 17, 2013

April 17, 2013

Hi, I am new to linux kernel buidling. I have download 3.8.7 latest (stable) kernel from https://www.kernel.org/. I want build kernel for X86_64. 1. make x86_64_defconfig (this created .config file) 2. make Make failed with below error, please help me in resolving this. CC kernel/power/user.o CC kernel/power/block_io.o CC kernel/power/poweroff.o LD kernel/power/built-in.o CC kernel/sched/core.o CC kernel/sched/clock.o CC kernel/sched/cputime.o CC kernel/sched/idle_task.o CC kernel/sched/fair.o kernel/sched/fair.c: In function `update_curr': kernel/sched/fair.c:428: sorry, unimplemented: inlining failed in call to 'account_cfs_rq_runtime': function body not available kernel/sched/fair.c:714: sorry, unimplemented: called from here make-3.79.1-p7[2]: *** [kernel/sched/fair.o] Error 1 make-3.79.1-p7[1]: *** [kernel/sched] Error 2 make-3.79.1-p7: *** [kernel] Error 2 bash-3.00$ pwd thanks Giri

2 7

Handling MSI interrupts
by Matti Vaittinen April 17, 2013

April 17, 2013

Hello! I am working with an asic that is controlled by CPU. With our current board this asic sends interrupts to processor via single interrupt line. CPU sees level active interrupt, and reads the reason(s) from asic's register. When handler(s) have executed, the read interrupts are acked to asic, and if no more interrupt(s) have ocurred on asic, this interrupt line is brought in inactive state. If new (different type of) interrupts have occurred on asic, the acking wont clean all interrupts from asic's register and asic keeps the interrupt line activated. Thus CPU is interrupted again && this process is done again && all interrupts are handled. Now there is plans to make this asic to use PCIe, and MSI interrupts. Also we hope to utilize the same driver(s) for this asic. So first idea would be to implement this as: 1. asic generates irq 2. MSI interrupt is sent (to PCIe controller) and CPU is interrupted 3. CPU acks interrupt to PCIe controller. 4. isr reads the interrupt reason(s) from asic and handles interrupt(s) 5. isr acks the interrupts. So is there a problem if new interrupt is generated between steps 4 and 5. Do we lose this new interrupt because the isr is still running? So when the isr acks interrupts to asic, it does not ack this new one because it had not happened when the reasons were read at step 4? I have read the MSI-HOWTO.txt and genirq guides, and even tried to read some sources. However I have not found out solid answer. Is there some de-facto method to do this so it works reliably? Following section may contain errors, it is what I have guessed by reading the sources - please kick me if it sounds stupid. By reading the sources I have figured that the "interrupt-controller" for MSI interrupts on processor does used handle_simple_irq as flow handler. If I am correct, this does not "queue" interrupts in same fashion the handle_edge_irq would do. Does this mean that my fear is correct? Br Matti Vaittinen

1 0

How to debug kernel on ARM with gdb
by Woody Wu April 17, 2013

April 17, 2013

Hi, I am working on an embedded ARM board (s3c2416) and I can already debug its boot loader (u-boot) with arm-linux-gdb, which talks to a GDB server provided from J-Link. Now I want to debug the kernel. The problem is that how can I get the correct symbol table for listing source lines in gdb. I checked the symbols in my compiled vmlinux, it starts from 0xC0008000. I think this is the final runtime address and should be a virtual address after MMU enabled. When kernel getting loaded into RAM, the virtual address probably not exists. On the other hand, the zImage loaded by boot loader is not vmlinux actually, it should be head.S which then carries vmlinux as piggy. So, with these complexities, how can I correctly debug Linux kernel starting from it's first instruction in head.S? Who have experience on this? Thanks in advance. -- woody I can't go back to yesterday - because I was a different person then.

1 0

Invitation to connect on LinkedIn
by Kumar Sukhani via LinkedIn April 17, 2013

April 17, 2013

LinkedIn ------------ Kumar Sukhani requested to add you as a connection on LinkedIn: ------------------------------------------ Deepak, I'd like to add you to my professional network on LinkedIn. - Kumar Accept invitation from Kumar Sukhani http://www.linkedin.com/e/8z2206-hflhs696-5i/L90NvsYL3GREvJdnM0f-HnfkWNbSD_… View profile of Kumar Sukhani http://www.linkedin.com/e/8z2206-hflhs696-5i/rso/123751041/F9xI/name/494894… ------------------------------------------ You are receiving Invitation emails. This email was intended for Deepak Shah. Learn why this is included: http://www.linkedin.com/e/8z2206-hflhs696-5i/plh/http%3A%2F%2Fhelp%2Elinked… (c) 2012, LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

3 2