Re: [Fastboot] [PATCH] Ignore PT_NOTE program headers with offset 0.

2007-03-16 Thread Vivek Goyal
On Fri, Mar 16, 2007 at 10:10:04AM +, Ian Campbell wrote: > There is a binutils bug which causes PT_NOTE segments to have an offset of > zero (http://sourceware.org/bugzilla/show_bug.cgi?id=594). The fix has not > made it into any release binutils, although several distributions have > backport

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

2007-03-16 Thread Vivek Goyal
On Fri, Mar 16, 2007 at 05:55:59PM +0530, Vivek Goyal wrote: > On Fri, Mar 16, 2007 at 11:40:55AM +, Ian Campbell wrote: > > On Fri, 2007-03-16 at 17:08 +0530, Vivek Goyal wrote: > > > On Fri, Mar 16, 2007 at 07:05:30PM +0900, Magnus Damm wrote: > > > > O

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

2007-03-16 Thread Vivek Goyal
On Fri, Mar 16, 2007 at 11:40:55AM +, Ian Campbell wrote: > On Fri, 2007-03-16 at 17:08 +0530, Vivek Goyal wrote: > > On Fri, Mar 16, 2007 at 07:05:30PM +0900, Magnus Damm wrote: > > > On 3/16/07, Vivek Goyal <[EMAIL PROTECTED]> wrote: > > > >Got a questi

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

2007-03-16 Thread Vivek Goyal
On Fri, Mar 16, 2007 at 07:05:30PM +0900, Magnus Damm wrote: > On 3/16/07, Vivek Goyal <[EMAIL PROTECTED]> wrote: > >Got a question. When running 32bit dom0 on 64bit hypervisor, which > >kexec-tools elf loader will kick in? 32bit or 64bit? Looks like in this > >case 64b

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

2007-03-16 Thread Vivek Goyal
On Fri, Mar 16, 2007 at 06:20:14PM +0900, Magnus Damm wrote: > On 3/16/07, Ian Campbell <[EMAIL PROTECTED]> wrote: > >On Fri, 2007-03-16 at 16:59 +0900, Magnus Damm wrote: > >> On 3/16/07, Ian Campbell <[EMAIL PROTECTED]> wrote: > >> > On Fri, 2007-03-16 at 11:40 +0900, Magnus Damm wrote: > >> > >

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

2007-03-16 Thread Vivek Goyal
On Fri, Mar 16, 2007 at 08:50:01AM +, Ian Campbell wrote: > On Fri, 2007-03-16 at 16:59 +0900, Magnus Damm wrote: > > On 3/16/07, Ian Campbell <[EMAIL PROTECTED]> wrote: > > > On Fri, 2007-03-16 at 11:40 +0900, Magnus Damm wrote: > > > > Right. And maybe it's a good idea to make sure that this

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

2007-03-15 Thread Vivek Goyal
On Fri, Mar 16, 2007 at 11:40:07AM +0900, Magnus Damm wrote: > On 3/16/07, Horms <[EMAIL PROTECTED]> wrote: > >On Thu, Mar 15, 2007 at 06:56:16PM +0530, Vivek Goyal wrote: > >> On Thu, Mar 15, 2007 at 12:22:57PM +, Ian Campbell wrote: > >> > On Thu, 2007-03-

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

2007-03-15 Thread Vivek Goyal
On Fri, Mar 16, 2007 at 08:48:08AM +0900, Horms wrote: > On Thu, Mar 15, 2007 at 06:56:16PM +0530, Vivek Goyal wrote: > > On Thu, Mar 15, 2007 at 12:22:57PM +, Ian Campbell wrote: > > > On Thu, 2007-03-15 at 11:17 +0530, Vivek Goyal wrote: > > > > > > But I

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

2007-03-15 Thread Vivek Goyal
On Thu, Mar 15, 2007 at 01:42:39PM +, Ian Campbell wrote: > On Thu, 2007-03-15 at 18:56 +0530, Vivek Goyal wrote: > > > > Ideal place for this probably should have been arch dependent > > crash_dump.h file. But we don't have one and no point introducing on

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

2007-03-15 Thread Vivek Goyal
On Thu, Mar 15, 2007 at 12:22:57PM +, Ian Campbell wrote: > On Thu, 2007-03-15 at 11:17 +0530, Vivek Goyal wrote: > > > > But I think changing this macro might run into issues. It is > > > > being used at few places in kernel, for example while loading > >

Re: [Fastboot] [PATCH] Move memory range variables

2007-03-15 Thread Vivek Goyal
On Thu, Mar 15, 2007 at 06:11:55PM +0900, Magnus Damm wrote: > On Thu, 2007-03-15 at 14:30 +0530, Vivek Goyal wrote: > > On Thu, Mar 15, 2007 at 05:53:19PM +0900, Magnus Damm wrote: > > > Move memory range variables > > > > > > The common kexec code is currentl

Re: [Fastboot] [PATCH] Move memory range variables

2007-03-15 Thread Vivek Goyal
On Thu, Mar 15, 2007 at 05:53:19PM +0900, Magnus Damm wrote: > Move memory range variables > > The common kexec code is currently using two global variables to keep > track of memory ranges. Other data is kept in a per-instance structure. > This mix is of per-instance and global variables is confu

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

2007-03-14 Thread Vivek Goyal
On Thu, Mar 15, 2007 at 02:07:56PM +0900, Horms wrote: > On Thu, Mar 15, 2007 at 10:25:36AM +0530, Vivek Goyal wrote: > > On Thu, Mar 15, 2007 at 10:46:38AM +0900, Horms wrote: > > > On Wed, Mar 14, 2007 at 05:00:09PM +, Ian Campbell wrote: > > > > The specific c

Re: [Fastboot] Problem with MSI-X on IA64

2007-03-14 Thread Vivek Goyal
On Wed, Mar 14, 2007 at 12:44:03PM +0100, Bernhard Walle wrote: > Hello, > > * Vivek Goyal <[EMAIL PROTECTED]> [2007-03-01 13:50]: > > > > Do you have more details about why MSI initialization failed? That only > > can explain what should be the right solution.

Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps

2007-03-14 Thread Vivek Goyal
On Thu, Mar 15, 2007 at 10:46:38AM +0900, Horms wrote: > On Wed, Mar 14, 2007 at 05:00:09PM +, Ian Campbell wrote: > > The specific case I am encountering is kdump under Xen with a 64 bit > > hypervisor and 32 bit kernel/userspace. The dump created is a 64 bit due > > to the hypervisor but the

Re: [Fastboot] FW: Re: Kexec/kdump got hung

2007-03-11 Thread Vivek Goyal
On Sun, Mar 11, 2007 at 08:35:08PM -0800, Dharmosoth Seetharam wrote: > -- > > I have traced the kexec tool .. and found the following hang point. > (kexec-tools-1.101) > purgatory/arch/x86_64/entry64.S > > entry64: > > .. > >

Re: [Fastboot] [PATCH 0/20] x86_64 Relocatable bzImage support (V4)

2007-03-08 Thread Vivek Goyal
On Thu, Mar 08, 2007 at 07:07:23PM +1100, Nigel Cunningham wrote: > Hi. > > On Thu, 2007-03-08 at 10:10 +0530, Vivek Goyal wrote: > > On Thu, Mar 08, 2007 at 10:15:02AM +1100, Nigel Cunningham wrote: > > > Hi. > > > > > > On Thu, 2007-03-08 at 07:49

Re: [Fastboot] [PATCH 0/20] x86_64 Relocatable bzImage support (V4)

2007-03-07 Thread Vivek Goyal
On Thu, Mar 08, 2007 at 10:15:02AM +1100, Nigel Cunningham wrote: > Hi. > > On Thu, 2007-03-08 at 07:49 +1100, Nigel Cunningham wrote: > > Hi. > > > > On Wed, 2007-03-07 at 07:07 -0800, Arjan van de Ven wrote: > > > On Wed, 2007-03-07 at 12:27

Re: [Fastboot] [PATCH 1/20] x86_64: Assembly safe page.h and pgtable.h

2007-03-07 Thread Vivek Goyal
On Wed, Mar 07, 2007 at 08:24:04PM +0100, Sam Ravnborg wrote: > On Wed, Mar 07, 2007 at 12:29:20PM +0530, Vivek Goyal wrote: > > > > > > This patch makes pgtable.h and page.h safe to include > > in assembly files like head.S. Allowing us to use > > symboli

Re: [Fastboot] [PATCH 15/20] Move swsusp __pa() dependent code to arch portion

2007-03-07 Thread Vivek Goyal
ch don't have kernel text/data mapped into kernel linearly mapped > > region can come up with their own ways of determining physical addresses > > associated with a kernel text. > > > > Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> > > ...hmm, but that

Re: [Fastboot] [PATCH 16/20] swsusp: do not use virt_to_page on kernel data address

2007-03-07 Thread Vivek Goyal
er). > > > > o Allocate swsusp_header dynamically so that virt_to_page() can be used > > safely. > > > > o I am changing this because in next few patches, __pa() on x86_64 will > > no longer support kernel text and data addresses and hibernation breaks. > > >

Re: [Fastboot] [PATCH 16/20] swsusp: do not use virt_to_page on kernel data address

2007-03-07 Thread Vivek Goyal
er). > > > > o Allocate swsusp_header dynamically so that virt_to_page() can be used > > safely. > > > > o I am changing this because in next few patches, __pa() on x86_64 will > > no longer support kernel text and data addresses and hibernation breaks. > > >

Re: [Fastboot] [PATCH 12/20] x86_64: 64bit ACPI wakeup trampoline

2007-03-07 Thread Vivek Goyal
n compiled for. o Removed the need for modifying any existing kernel page table. o Increased the size of the wakeup routine to 8K. This is required as wake page tables are on trampoline itself and they got to be at 4K boundary, hence one page is not sufficient. Signed-off-by: Eric W. Biederma

Re: [Fastboot] [PATCH 0/20] x86_64 Relocatable bzImage support (V4)

2007-03-07 Thread Vivek Goyal
On Thu, Mar 08, 2007 at 10:15:02AM +1100, Nigel Cunningham wrote: > Hi. > > On Thu, 2007-03-08 at 07:49 +1100, Nigel Cunningham wrote: > > Hi. > > > > On Wed, 2007-03-07 at 07:07 -0800, Arjan van de Ven wrote: > > > On Wed, 2007-03-07 at 12:27

Re: [Fastboot] [PATCH 11/20] x86_64: wakeup.S misc cleanups

2007-03-07 Thread Vivek Goyal
On Wed, Mar 07, 2007 at 11:41:57PM +0100, Pavel Machek wrote: > Hi! > > > + movw$0x0e00 + 'i', %ds:(0xb8012) > > + movb$0xa8, %al ; outb %al, $0x80; > > + > > > - movw$0x0e00 + 'i', %ds:(0xb8012) > > - movb$0xa8, %al ; outb %al, $0x80; > > Outbs were my d

Re: [Fastboot] [PATCH 11/20] x86_64: wakeup.S misc cleanups

2007-03-07 Thread Vivek Goyal
read, anyway we trash the read contents. > > - No need to enable system call (EFER_SCE). Anyway it will be > > enabled when original EFER is restored. > > - No need to set MP, ET, NE, WP, AM bits in cr0. Very soon we will > > reload the original cr0 while restro

Re: [Fastboot] [PATCH 0/20] x86_64 Relocatable bzImage support (V4)

2007-03-07 Thread Vivek Goyal
On Wed, Mar 07, 2007 at 07:07:39AM -0800, Arjan van de Ven wrote: > On Wed, 2007-03-07 at 12:27 +0530, Vivek Goyal wrote: > > Hi, > > > > Here is another attempt on x86_64 relocatable bzImage patches(V4). This > > patchset makes a bzImage relocatable and same kernel b

Re: [Fastboot] [PATCH 2/2] kexec-tools: x86_64 bzImage load purgatory below 2G

2007-03-07 Thread Vivek Goyal
On Wed, Mar 07, 2007 at 06:01:22PM +0900, Horms wrote: > On Wed, Mar 07, 2007 at 01:52:18PM +0530, Vivek Goyal wrote: > > > > o Load purgatory below 2G while loading bzImage. x86_64 purgatory got > > relocation types R_X86_64_32S hence got to be below 2G. > > Thanks.

[Fastboot] [PATCH 2/2] kexec-tools: x86_64 bzImage load purgatory below 2G

2007-03-07 Thread Vivek Goyal
o Load purgatory below 2G while loading bzImage. x86_64 purgatory got relocation types R_X86_64_32S hence got to be below 2G. Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- diff -puN kexec/arch/i386/kexec-bzImage.c~kexec-tools-x86_64-bzImage-load-purgatory-below-2G kexec/arc

[Fastboot] [PATCH 17/20] x86_64: __pa and __pa_symbol address space separation

2007-03-06 Thread Vivek Goyal
__pa in the common case, even on a relocated kernel. As this is technically a semantic change we need to be on the lookout for anything I missed. But it works for me (tm). Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> ---

[Fastboot] [PATCH 11/20] x86_64: wakeup.S misc cleanups

2007-03-06 Thread Vivek Goyal
ET, NE, WP, AM bits in cr0. Very soon we will reload the original cr0 while restroing the processor state. Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/kernel/acpi/wakeup.S | 112 +---

[Fastboot] [PATCH 1/20] x86_64: Assembly safe page.h and pgtable.h

2007-03-06 Thread Vivek Goyal
arguments. This patch adds #ifndef __ASSEMBLY__ ... #endif and _AC(1,UL) where appropriate so the assembler won't choke on the header files. Otherwise nothing should have changed. Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]>

[Fastboot] [PATCH 10/20] x86_64: wakeup.S rename registers to reflect right names

2007-03-06 Thread Vivek Goyal
o Use appropriate names for 64bit regsiters. Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/kernel/acpi/wakeup.S | 36 ++-- include/asm-x86_64/suspend.h | 12 ++---

[Fastboot] [PATCH 4/20] x86_64: Fix early printk to use standard ISA mapping

2007-03-06 Thread Vivek Goyal
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/kernel/early_printk.c |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff -puN arch/x86_64/kernel/early_printk.c~x86_64-fix-early_printk-to-use-the-

[Fastboot] [PATCH 13/20] x86_64: Modify discover_ebda to use virtual addresses

2007-03-06 Thread Vivek Goyal
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/kernel/setup.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff -puN arch/x86_64/kernel/setup.c~x86_64-Modify-discover_ebda-to-use-virtual-add

[Fastboot] [PATCH 20/20] x86_64: Move cpu verification code to common file

2007-03-06 Thread Vivek Goyal
patch, at least it can be easily isolated. Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/boot/compressed/head.S | 19 ++ arch/x86_64/boot/setup.S | 65 ++--- arch/x86_64/ker

[Fastboot] [PATCH 6/20] x86_64: cleanup segments

2007-03-06 Thread Vivek Goyal
, and it potentially allows the pages to be immutable. Plus it is confusing when debugging and your gdt entries mysteriously change. Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/kernel/head.S| 12 ++--

[Fastboot] [PATCH 7/20] x86_64: Add EFER to the register set saved by save_processor_state

2007-03-06 Thread Vivek Goyal
EFER varies like %cr4 depending on the cpu capabilities, and which cpu capabilities we want to make use of. So save/restore it make certain we have the same EFER value when we are done. Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL

[Fastboot] [PATCH 19/20] x86_64: Extend bzImage protocol for relocatable bzImage

2007-03-06 Thread Vivek Goyal
. Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/boot/setup.S | 13 +++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff -puN arch/x86_64/boot/setup.S~x86_64-extend-bzImage-protocol-for-relocatable-bzImage

[Fastboot] [PATCH 8/20] x86_64: 64bit PIC SMP trampoline

2007-03-06 Thread Vivek Goyal
ROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/kernel/head.S |1 arch/x86_64/kernel/setup.c |9 -- arch/x86_64/kernel/trampoline.S | 168 3 files changed, 156 insertions(+), 22 deletions(-) diff -puN a

[Fastboot] [PATCH 0/20] x86_64 Relocatable bzImage support (V4)

2007-03-06 Thread Vivek Goyal
Hi, Here is another attempt on x86_64 relocatable bzImage patches(V4). This patchset makes a bzImage relocatable and same kernel binary can be loaded and run from different physical addresses. As on now, this mainly helps distros who have to ship an extra kernel compiled for a different physical

[Fastboot] [PATCH 18/20] x86_64: Relocatable Kernel Support

2007-03-06 Thread Vivek Goyal
2M and it will run there. This both ensures the relocation code is always working, and makes it easier to use 2M pages for the kernel and the cpu. Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/Kconfig

[Fastboot] [PATCH 9/20] x86_64: Get rid of dead code in suspend resume

2007-03-06 Thread Vivek Goyal
. Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/kernel/acpi/wakeup.S | 57 --- 1 file changed, 1 insertion(+), 56 deletions(-) diff -puN arch/x86_64/kernel/acpi/wakeup.S~x86_6

[Fastboot] [PATCH 5/20] x86_64: modify copy_bootdata to use virtual addresses

2007-03-06 Thread Vivek Goyal
. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/kernel/head64.c | 17 - 1 file changed, 8 insertions(+), 9 deletions(-) diff -puN arch/x86_64/kernel/head64.c~x86_64-modify-copy_bootdata-to-use-virtual-addresses arch/x

[Fastboot] [PATCH 15/20] Move swsusp __pa() dependent code to arch portion

2007-03-06 Thread Vivek Goyal
ernel text. Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/i386/power/suspend.c | 14 ++ arch/powerpc/kernel/Makefile |1 + arch/powerpc/kernel/suspend.c | 24 arch/x86_64/kernel/suspend.c | 14 ++ kernel/power/power.h

[Fastboot] [PATCH 3/20] x86_64: Clean up the early boot page table

2007-03-06 Thread Vivek Goyal
that makes maitenance more difficult. Instead just use label - __START_KERNEL_map like we do everywhere else in assembly. Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/k

[Fastboot] [PATCH 16/20] swsusp: do not use virt_to_page on kernel data address

2007-03-06 Thread Vivek Goyal
in next few patches, __pa() on x86_64 will no longer support kernel text and data addresses and hibernation breaks. Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- kernel/power/swap.c | 42 +++--- 1 file changed, 27 insertions(+), 15 deletions(-)

[Fastboot] [PATCH 2/20] x86_64: Kill temp boot pmds

2007-03-06 Thread Vivek Goyal
allocate/map and unmap a page. Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/kernel/head.S |3 - arch/x86_64/mm/init.c | 100 -- 2 files changed, 45 inser

[Fastboot] [PATCH 14/20] x86_64: Remove the identity mapping as early as possible

2007-03-06 Thread Vivek Goyal
AIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/kernel/head.S| 39 ++- arch/x86_64/kernel/head64.c | 17 +++-- arch/x86_64/kernel/setup.c |2 -- arch/x86_64/kernel/setup64.c |1 - arch/x86_

[Fastboot] [PATCH 12/20] x86_64: 64bit ACPI wakeup trampoline

2007-03-06 Thread Vivek Goyal
, hence one page is not sufficient. Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/x86_64/kernel/acpi/sleep.c | 22 ++ arch/x86_64/kernel/acpi/wakeup.S | 59 --- arch/x86_64/k

Re: [Fastboot] [PATCH] Fix interrupt distribution in ppc970

2007-03-06 Thread Vivek Goyal
On Tue, Mar 06, 2007 at 03:16:55PM +0100, Michael Ellerman wrote: > On Tue, 2007-03-06 at 19:27 +0530, Mohan Kumar M wrote: > > Hi, > > > > Here comes the revised version of patch to fix the interrupt missing > > problem when a kdump kernel is booted with "maxcpus=1" kernel parameter. > > > > In

Re: [Fastboot] [PATCH] Add support for longer kernel command lines (i586, x86_64, IA64)

2007-03-06 Thread Vivek Goyal
On Tue, Mar 06, 2007 at 10:24:56AM +0100, Bernhard Walle wrote: > Hello, > > * Vivek Goyal <[EMAIL PROTECTED]> [2007-03-06 05:15]: > > On Tue, Mar 06, 2007 at 09:42:04AM +0530, Vivek Goyal wrote: > > > On Mon, Mar 05, 2007 at 11:34:33PM +0100, Bernhard Walle wrote

Re: [Fastboot] [PATCH] Add support for longer kernel command lines (i586, x86_64, IA64)

2007-03-05 Thread Vivek Goyal
On Tue, Mar 06, 2007 at 09:42:04AM +0530, Vivek Goyal wrote: > On Mon, Mar 05, 2007 at 11:34:33PM +0100, Bernhard Walle wrote: > > This patch increases the kernel command line size for x86_64 and i386 > > to 2048 characters. This is necessary because with kernel 2.6.21 > >

Re: [Fastboot] [PATCH] Add support for longer kernel command lines (i586, x86_64, IA64)

2007-03-05 Thread Vivek Goyal
On Mon, Mar 05, 2007 at 11:34:33PM +0100, Bernhard Walle wrote: > This patch increases the kernel command line size for x86_64 and i386 > to 2048 characters. This is necessary because with kernel 2.6.21 > and newer, the kernel command line size has increased and kexec needs > lot of command line sp

Re: [Fastboot] Kernel format issues?

2007-03-05 Thread Vivek Goyal
On Fri, Mar 02, 2007 at 02:29:42PM -0800, Greg Kurtzer wrote: > On testing of RHEL5 beta with Perceus (uses kexec), people are having > problems with the kexec. I can't replicate locally but here is the > info that I got: > > # kexec --initrd=/vnfs.img --force --append="masterip=192.168.1.254

Re: [Fastboot] [PATCH RFC 0/5] hard_smp_processor_id overhaul

2007-03-01 Thread Vivek Goyal
On Thu, Mar 01, 2007 at 09:06:48AM -0500, Benjamin LaHaise wrote: > On Thu, Mar 01, 2007 at 04:16:13PM +0900, Fernando Luis Vázquez Cao wrote: > > As a consequence, the hardcoding of hard_smp_processor_id() to 0 on UP > > systems (see "linux/smp.h") is not correct. > > > > This patch-set does the

Re: [Fastboot] Problem with MSI-X on IA64

2007-03-01 Thread Vivek Goyal
On Wed, Feb 21, 2007 at 02:12:40PM +0100, Bernhard Walle wrote: > * Bernhard Walle <[EMAIL PROTECTED]> [2007-02-16 19:03]: > > we have a HP rx2660 with a cciss controller that uses MSI. When > > dumping into the kdump kernel, the kernel hangs with following error: > > > > cciss: Device 0x3230

Re: [Fastboot] Problem with MSI-X on IA64

2007-03-01 Thread Vivek Goyal
On Fri, Feb 16, 2007 at 07:03:36PM +0100, Bernhard Walle wrote: > Hello, > > we have a HP rx2660 with a cciss controller that uses MSI. When > dumping into the kdump kernel, the kernel hangs with following error: > > cciss: Device 0x3230 has been found at bus 5 dev 0 func 0 > ACPI: PCI In

Re: [Fastboot] [PATCH 2/5] Use the APIC to determine the hardware processor id - i386

2007-03-01 Thread Vivek Goyal
On Thu, Mar 01, 2007 at 04:16:59PM +0900, Fernando Luis Vázquez Cao wrote: > Use the APIC to determine the hardware processor id when APIC support > has been selected, independently of whether CONFIG_SMP is set or not. > > Signed-off-by: Fernando Luis Vazquez Cao <[EMAIL PROTECTED]> > --- > > dif

Re: [Fastboot] [PATCH] kexec-tools : fix compile time error on x86-64

2007-02-26 Thread Vivek Goyal
On Tue, Feb 27, 2007 at 11:25:07AM +0530, Sachin P. Sant wrote: > On x86_64 machines running kernels having relocatale kernel patches > compilation of kexec tools fails with following error. > > kexec/arch/i386/kexec-multiboot-x86.c:347: warning: implicit > declaration of function ‘_AC’ > kexec/a

Re: [Fastboot] [PATCH] Keep alignment comment in elf code and use ELF_CORE_HEADER_ALIGN

2007-02-15 Thread Vivek Goyal
On Thu, Feb 15, 2007 at 06:57:06PM +0900, Magnus Damm wrote: > Keep alignment comment in elf code and use ELF_CORE_HEADER_ALIGN > > This patch puts back and extends the alignment comment in crashdump-elf.c > and adds a small check to make sure the arch-specific code aligns properly. > Instead of h

Re: [Fastboot] [PATCH] Keep alignment comment in elf code and use KERNEL_CMDLINE_ALIGN

2007-02-15 Thread Vivek Goyal
On Thu, Feb 15, 2007 at 05:24:04PM +0900, Magnus Damm wrote: > Keep alignment comment in elf code and use KERNEL_CMDLINE_ALIGN > > This patch puts back the alignment comment to crashdump-elf.c and > adds a small check to make sure the arch-specific code aligns properly. > Instead of hardcoding 102

Re: [Fastboot] Zero size /proc/vmcore on ia64

2007-02-07 Thread Vivek Goyal
On Thu, Feb 08, 2007 at 12:06:53PM +0900, Horms wrote: > On Thu, Feb 08, 2007 at 10:07:48AM +0800, Zou, Nanhai wrote: > > > > Hi Vivek, > > I have a question about why saved_max_pfn check in vmcore.c is needed. > > Here is a typical memory layout of IA64 machine. > > > > - ===>max_pfn for

[Fastboot] Fw: Re: Dump only kernel memory

2007-02-02 Thread Vivek Goyal
Hi Ken'ichi, FYI. Another user is looking for support of DISCONTIGMEM in makedumpfile. Thanks Vivek - Forwarded message from trajce nedev <[EMAIL PROTECTED]> - From: trajce nedev <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Dump only kernel memory Date: Fri, 02 Feb 2007 00:06:

Re: [Fastboot] [ PATCH ] fix to documentation for kexec

2007-02-02 Thread Vivek Goyal
On Thu, Feb 01, 2007 at 10:58:08AM -0800, Judith Lebzelter wrote: > > > > I did notice that my patch is out of date for the latest kernel, > > however. I can send an up to date one. > > > This applies to 2.6.20-rc7 > > Signed-off-by: Judith Lebzeelter <[EMAIL PROTECTED]> > --- > > Stop recomm

Re: [Fastboot] IA64: reliable way to determine kdump_kernel?

2007-01-28 Thread Vivek Goyal
On Sat, Jan 20, 2007 at 10:10:36AM -0800, Jay Lan wrote: > What is a reliable way to determine whether the booting kernel > is a production kernel or a kdump kernel? > > In setup_arch() routine of arch/ia64/kernel/setup.c, there is > a statement as below: > > kdump_kernel = (strstr(saved_command

Re: [Fastboot] [PATCH] Kdump documentation update for 2.6.20

2007-01-18 Thread Vivek Goyal
On Thu, Jan 18, 2007 at 05:31:17PM -0500, Mohan Kumar M wrote: > Hi, > > Vivek's kdump documentaion patch is in 2.6.20-rc5 tree. > > I have modified kdump documentation for ppc64 and slightly made minor > changes. Attached patch is generated over 2.6.20-rc5 tree. > > Please review the patch. If

Re: [Fastboot] Confusion about IO-APIC Entry?

2007-01-16 Thread Vivek Goyal
On Tue, Jan 16, 2007 at 12:49:31PM -0500, Benjamin Romer wrote: > On Fri, 2007-01-12 at 15:16 +0530, Vivek Goyal wrote: > > On Thu, Jan 11, 2007 at 10:01:20AM -0500, Benjamin Romer wrote: > > > After a lot of internal discussion with other Unisys employees, I think > > >

[Fastboot] [PATCH] i386: modpost apic related warning fixes

2007-01-14 Thread Vivek Goyal
eck_apicid_present' o Some functions which are inline (acpi_madt_oem_check) are not inlined by compiler as these functions are accessed using function pointer. These functions are put in .text section and they in-turn access __init type functions hence modpost generates warnings. o Do not in

Re: [Fastboot] Dumping to a remote host by makedumpfile.

2007-01-14 Thread Vivek Goyal
On Fri, Jan 12, 2007 at 09:27:10AM -0500, Dave Anderson wrote: > > Well, we effectively do that already -- there's significant overlap in the > makedumpfile and crash code bases as it is. (When I look at the makedumpfile > code, it's like deja vu all over again...) > > But that's not the point.

Re: [Fastboot] [PATCH] Allow i136 and x86_64 platforms to grok /proc/iomem on EFI-based systems

2007-01-14 Thread Vivek Goyal
On Fri, Jan 12, 2007 at 12:44:17PM -0800, Lombard, David N wrote: > The attached patch adds recognition of the appropriate /proc/iomem tags > on EFI-based platforms for x86 and x86_64 IA systems. > Hi David, This patch looks fine to me. Its a small patch, you don't have to compress it before se

Re: [Fastboot] kdump on ia64 with 2.6.20-rc4 > no vmcore ?

2007-01-12 Thread Vivek Goyal
On Fri, Jan 12, 2007 at 09:52:36AM +0100, Welterlen Benoit wrote: > TCP: Hash tables configured (established 16384 bind 8192) > TCP reno registered > checking if image is initramfs... it is > Freeing initrd memory: 3776kB freed > perfmon: version 2.0 IRQ 238 > perfmon: Montecito PMU detected, 27 PM

Re: [Fastboot] Confusion about IO-APIC Entry?

2007-01-12 Thread Vivek Goyal
On Thu, Jan 11, 2007 at 10:01:20AM -0500, Benjamin Romer wrote: > After a lot of internal discussion with other Unisys employees, I think > I've finally got this all figured out. The problem is one line of code > in the disable_IO_APIC() function, that says this: > > entry.dest.physical.physical

Re: [Fastboot] Confusion about IO-APIC Entry?

2007-01-12 Thread Vivek Goyal
On Tue, Jan 09, 2007 at 12:26:20PM -0500, Benjamin Romer wrote: > While working with the IO-APIC problem I've been having on the ES-7000, > I noticed something that confuses me about the IO-APIC table entry > structure. If you look in include/asm-x86_64/io_apic.h, it lists the > destination field a

Re: [Fastboot] kdump on ia64 with 2.6.20-rc4 > no vmcore ?

2007-01-12 Thread Vivek Goyal
On Fri, Jan 12, 2007 at 09:27:55AM +0100, Welterlen Benoit wrote: > Horms wrote: > >On Thu, Jan 11, 2007 at 01:06:11PM +0100, Welterlen Benoit wrote: > > > >>Hello all, > >> > >>I try kdump with 2.6.20-rc4 kernel from kernel.org. > >>I successfully reboot on the debug kernel after c sys-rq but I ha

Re: [Fastboot] kdump on ia64 with 2.6.20-rc4 > no vmcore ?

2007-01-12 Thread Vivek Goyal
On Fri, Jan 12, 2007 at 03:14:28PM +0900, Horms wrote: > On Thu, Jan 11, 2007 at 01:06:11PM +0100, Welterlen Benoit wrote: > > Hello all, > > > > I try kdump with 2.6.20-rc4 kernel from kernel.org. > > I successfully reboot on the debug kernel after c sys-rq but I have an > > error : > > Kdump: vm

Re: [Fastboot] Dumping to a remote host by makedumpfile.

2007-01-12 Thread Vivek Goyal
On Thu, Jan 11, 2007 at 08:55:44AM -0500, Dave Anderson wrote: > Vivek Goyal wrote: > > > On Wed, Jan 10, 2007 at 09:07:03AM -0500, Dave Anderson wrote: > > > Just curious -- how difficult would it be to put the "-R" intelligence > > > into the >

Re: [Fastboot] kdump on ia64 with 2.6.20-rc4 > no vmcore ?

2007-01-11 Thread Vivek Goyal
On Thu, Jan 11, 2007 at 01:06:11PM +0100, Welterlen Benoit wrote: > Hello all, > > I try kdump with 2.6.20-rc4 kernel from kernel.org. > I successfully reboot on the debug kernel after c sys-rq but I have an > error : > Kdump: vmcore not initialized > > I can not access the /proc/vmcore with cras

Re: [Fastboot] Dumping to a remote host by makedumpfile.

2007-01-10 Thread Vivek Goyal
On Wed, Jan 10, 2007 at 09:07:03AM -0500, Dave Anderson wrote: > Just curious -- how difficult would it be to put the "-R" intelligence into > the > crash utility so that it could read the intermediate dumpfile.tmp file? > > Or do we want to consistently maintain "readablility" by both crash and

Re: [Fastboot] Dumping to a remote host by makedumpfile.

2007-01-10 Thread Vivek Goyal
On Wed, Jan 10, 2007 at 10:16:02PM +0900, Ken'ichi Ohmichi wrote: > > Hi. > > 2007/01/10 09:59:49 +0530, Vivek Goyal <[EMAIL PROTECTED]> wrote: > >Still don't understand why do I need -R? I think it comes from that fact > >that mkdumpfile needs a way t

Re: [Fastboot] [PATCH] Kdump documentation update for 2.6.20

2007-01-10 Thread Vivek Goyal
On Wed, Jan 10, 2007 at 11:07:05AM +0530, Mohan Kumar M wrote: > On Tue, Jan 09, 2007 at 08:17:08PM +0530, Vivek Goyal wrote: > > > > Mohan, Can you please check the correctness of ppc64 specific details. > > > > Vivek, > > My inputs. > Thanks Mohan. I h

Re: [Fastboot] IO-APIC Trace (was RE: Test Message)

2007-01-09 Thread Vivek Goyal
On Fri, Jan 05, 2007 at 09:37:22AM -0500, Benjamin Romer wrote: > As you suspected, the vector field was not necessary for the timer to > work in the kexec kernel - I only needed to reset the logical > destination. I've emailed our platform group to get some more > information about how our IO-APIC

Re: [Fastboot] [PATCH] Kdump documentation update for 2.6.20

2007-01-09 Thread Vivek Goyal
On Wed, Jan 10, 2007 at 10:53:34AM +0900, Horms wrote: > On Wed, Jan 10, 2007 at 09:34:12AM +0800, Zou, Nanhai wrote: > > > > > > > > I am hoping it --args-linux will be required while loading vmlinux on > > > > IA64? Because this is ELF file specific option. And this interface > > > > should > >

Re: [Fastboot] Dumping to a remote host by makedumpfile.

2007-01-09 Thread Vivek Goyal
On Tue, Jan 09, 2007 at 11:14:31PM -0500, Don Zickus wrote: > On Wed, Jan 10, 2007 at 09:28:12AM +0530, Vivek Goyal wrote: > > On Wed, Jan 10, 2007 at 11:21:02AM +0900, Ken'ichi Ohmichi wrote: > > > > > > Hi. > > > > > > Last year, we discuss

[Fastboot] Fw: Re: kernel-only memory to kdump

2007-01-09 Thread Vivek Goyal
Had forgotten to CC to the list. - Forwarded message from Vivek Goyal <[EMAIL PROTECTED]> - Date: Wed, 10 Jan 2007 09:07:32 +0530 From: Vivek Goyal <[EMAIL PROTECTED]> To: trajce nedev <[EMAIL PROTECTED]> Cc: Ken'ichi Ohmichi <[EMAIL PROTECTED]> Subject: Re

Re: [Fastboot] Dumping to a remote host by makedumpfile.

2007-01-09 Thread Vivek Goyal
On Wed, Jan 10, 2007 at 11:21:02AM +0900, Ken'ichi Ohmichi wrote: > > Hi. > > Last year, we discussed about "dumping to a remote host by makedumpfile". > For this feature, I will add 2 options of STDOUT output to makedumpfile. > If this feature is implemented, makedumpfile can output the dump dat

Re: [Fastboot] [PATCH] Kdump documentation update for 2.6.20

2007-01-09 Thread Vivek Goyal
uld be common across all the architectures. > Then again, I could be wrong, I'm not sure that I understand > --args-linux, I just know that I'm not using it :) Thanks Vivek o Kdump documentation update. - Update details for using relocatable kernel. - Start usi

[Fastboot] [PATCH 2/4] make initkmem_list3 non init data to fix modpost warning

2007-01-08 Thread Vivek Goyal
Accesses initkmem_list3[] } o Somebody who knows this code well needs to review and ack. Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- mm/slab.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN mm/slab.c~make-initkmem_list3-non-init mm/slab.c --

[Fastboot] [PATCH 4/4] Make noirqdebug_setup function non init to fix modpost warning

2007-01-08 Thread Vivek Goyal
WARNING: vmlinux - Section mismatch: reference to .init.text:noirqdebug_setup from .text between 'quirk_intel_irqbalance' (at offset 0xc010969e) and 'i8237A_suspend' o Make noirqdebug_setup() non-init. Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- kernel/irq/sp

[Fastboot] [PATCH 1/4] pci quirks MODPOST warning fix

2007-01-08 Thread Vivek Goyal
x - Section mismatch: reference to .init.data: from .text between 'asus_hides_smbus_lpc' (at offset 0xc0217fd9) and 'pci_match_id' o Two quirk functions which are non __init, are accessing data which is of type __init. Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- dri

[Fastboot] [PATCH 3/4] i386: sched_clock using init data tsc_disable fix

2007-01-08 Thread Vivek Goyal
llback' Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- arch/i386/kernel/tsc.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN arch/i386/kernel/tsc.c~sched_clock-using-init-data-tsc_disable-fix arch/i386/kernel/tsc.c --- linux-2.6.20-rc2-mm1-reloc/arch/i386/kern

[Fastboot] [PATCH] Kdump documentation update for 2.6.20

2007-01-07 Thread Vivek Goyal
o Kdump documentation update. - Update details for using relocatable kernel. - Start using kexec-tools-testing release as it is latest and old kexec-tools can't load relocatable bzImage file. Signed-off-by: Vivek Goyal <[EMAIL PROTECTED]> --- Document

Re: [Fastboot] crash_dump on ppc4xx ?

2007-01-07 Thread Vivek Goyal
On Sat, Jan 06, 2007 at 10:14:37AM -0800, Randy Dunlap wrote: > Hi, > > Does CRASH_DUMP work on ppc4xx boards? or are there any > plans to do that? > ppc4xx is 32bit RISC processor and AFAIK, currently crash dump works only for ppc64. At least I am not aware of anybody working on it. > I'm a

Re: [Fastboot] [PATCH 2/2] kexec-tool: Append reset_devices flag to second kernel commandline

2007-01-04 Thread Vivek Goyal
On Fri, Jan 05, 2007 at 08:20:41AM +0900, Horms wrote: > On Thu, Jan 04, 2007 at 10:51:57AM -0500, Don Zickus wrote: > > On Thu, Jan 04, 2007 at 08:59:10AM -0500, Neil Horman wrote: > > > > Hi Neil, > > > > > > > > That solution would be very specific to RedHat. If a user on non RHEL5 > > > > dist

Re: [Fastboot] [PATCH 2/2] kexec-tool: Append reset_devices flag to second kernel commandline

2007-01-04 Thread Vivek Goyal
On Thu, Jan 04, 2007 at 10:51:57AM -0500, Don Zickus wrote: > On Thu, Jan 04, 2007 at 08:59:10AM -0500, Neil Horman wrote: > > > Hi Neil, > > > > > > That solution would be very specific to RedHat. If a user on non RHEL5 > > > distro tries to use kdump then how would he handle it? > > > > > I under

Re: [Fastboot] [PATCH 2/2] kexec-tool: Append reset_devices flag to second kernel commandline

2007-01-04 Thread Vivek Goyal
On Thu, Jan 04, 2007 at 07:41:01AM -0500, Neil Horman wrote: > On Thu, Jan 04, 2007 at 11:24:20AM +0530, Vivek Goyal wrote: > > On Thu, Jan 04, 2007 at 10:56:28AM +0530, Ankita Garg wrote: > > > Hi, > > > > > > o Patch to pass reset_devices flag to the second k

Re: [Fastboot] [PATCH 2/2] kexec-tool: Append reset_devices flag to second kernel commandline

2007-01-03 Thread Vivek Goyal
On Thu, Jan 04, 2007 at 10:56:28AM +0530, Ankita Garg wrote: > Hi, > > o Patch to pass reset_devices flag to the second kernel. > Some background why we need this command line parameter. Command line parameter reset_devices was introduced in kernel versions 2.6.19. The intention of this paramete

Re: [Fastboot] IO-APIC Trace (was RE: Test Message)

2007-01-03 Thread Vivek Goyal
On Wed, Jan 03, 2007 at 03:14:39PM -0500, Romer, Benjamin M wrote: > Hi again Vivek! I've got good news. :) > > First, I figured out why I wasn't getting my print_IO_APIC calls from my > kexec kernel - I had forgotten to copy the rebuilt vmlinux file into > /boot, so I was using the old version wi

Re: [Fastboot] [PATCH] i386 kernel instant reboot with older binutils fix

2007-01-03 Thread Vivek Goyal
On Wed, Jan 03, 2007 at 02:53:26PM +0100, Adrian Bunk wrote: > On Wed, Jan 03, 2007 at 09:46:45AM +0530, Vivek Goyal wrote: > > > > o i386 kernel reboots instantly if compiled with binutils older than > > 2.6.15. > > Should that have been "2.15"? > Y

[Fastboot] [PATCH 4/4] i386: Specify section flags while creating new sections

2007-01-03 Thread Vivek Goyal
tch in -mm which will break the things if used with older binutils. Hence this is the fix on top of that patch. http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc2/2.6.20-rc2-mm1/broken-out/i386-move-startup_32-in-texthead-section.patch Signed-off-by: Vivek Goyal <[EM

  1   2   3   4   5   >