* Re: 2.6.19-rc5-mm2: warnings in MODPOST and later [not found] ` <20061114225622.GO22565@stusta.de> @ 2006-11-14 23:09 ` Andrew Morton 2006-11-15 7:42 ` Arjan van de Ven 0 siblings, 1 reply; 7+ messages in thread From: Andrew Morton @ 2006-11-14 23:09 UTC (permalink / raw) To: Adrian Bunk; +Cc: virtualization@lists.osdl.org, linux-kernel On Tue, 14 Nov 2006 23:56:22 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Since people were recently complaining about too many warnings: > Here is a list of the warnings I'm getting in MODPOST and later. > > Since the warnings by far exceed the 100kB limit of linux-kernel (sic), > I had to attach them compressed. > > With the exception of the "drivers/ide/pci/atiixp:FFFF05", none of these > warnings is present in Linus' tree. yes, lots of new section mismatch warnings. A large number of them are due to the paravirt patches: WARNING: vmlinux - Section mismatch: reference to .init.text: from .parainstructions between '__start_parainstructions' (at offset 0xc0458470) and '__stop_parainstructions' WARNING: vmlinux - Section mismatch: reference to .init.text: from .parainstructions between '__start_parainstructions' (at offset 0xc0458478) and '__stop_parainstructions' WARNING: vmlinux - Section mismatch: reference to .init.text: from .parainstructions between '__start_parainstructions' (at offset 0xc0458480) and '__stop_parainstructions' WARNING: vmlinux - Section mismatch: reference to .init.text: from .parainstructions between '__start_parainstructions' (at offset 0xc0458488) and '__stop_parainstructions' WARNING: vmlinux - Section mismatch: reference to .init.text: from .parainstructions between '__start_parainstructions' (at offset 0xc0458490) and '__stop_parainstructions' WARNING: vmlinux - Section mismatch: reference to .init.text: from .parainstructions between '__start_parainstructions' (at offset 0xc0458498) and '__stop_parainstructions' WARNING: vmlinux - Section mismatch: reference to .init.text: from .parainstructions between '__start_parainstructions' (at offset 0xc04584a0) and '__stop_parainstructions' WARNING: Can't handle masks in drivers/ata/ahci:FFFF05 WARNING: drivers/ata/pata_legacy.o - Section mismatch: reference to .init.text: from .parainstructions after '' (at offset 0x18) WARNING: drivers/ata/pata_legacy.o - Section mismatch: reference to .init.text: from .parainstructions after '' (at offset 0x20) WARNING: drivers/ata/pata_legacy.o - Section mismatch: reference to .init.text: from .parainstructions after '' (at offset 0x28) WARNING: drivers/ata/pata_qdi.o - Section mismatch: reference to .init.text: from .parainstructions after '' (at offset 0x0) WARNING: drivers/ata/pata_qdi.o - Section mismatch: reference to .init.text: from .parainstructions after '' (at offset 0x8) but there are others too. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.6.19-rc5-mm2: warnings in MODPOST and later 2006-11-14 23:09 ` 2.6.19-rc5-mm2: warnings in MODPOST and later Andrew Morton @ 2006-11-15 7:42 ` Arjan van de Ven 0 siblings, 0 replies; 7+ messages in thread From: Arjan van de Ven @ 2006-11-15 7:42 UTC (permalink / raw) To: Andrew Morton Cc: Adrian Bunk, linux-kernel, Rusty Russell, virtualization@lists.osdl.org On Tue, 2006-11-14 at 15:09 -0800, Andrew Morton wrote: > On Tue, 14 Nov 2006 23:56:22 +0100 > Adrian Bunk <bunk@stusta.de> wrote: > > > Since people were recently complaining about too many warnings: > > Here is a list of the warnings I'm getting in MODPOST and later. > > > > Since the warnings by far exceed the 100kB limit of linux-kernel (sic), > > I had to attach them compressed. > > > > With the exception of the "drivers/ide/pci/atiixp:FFFF05", none of these > > warnings is present in Linus' tree. > > yes, lots of new section mismatch warnings. > > A large number of them are due to the paravirt patches: > > WARNING: vmlinux - Section mismatch: reference to .init.text: from .parainstructions between '__start_parainstructions' (at offset 0xc0458470) and '__stop_parainstructions' > WARNING: vmlinux - Section mismatch: reference to .init.text: from .parainstructions between '__start_parainstructions' (at offset 0xc0458478) and '__stop_parainstructions' ok this means that you shouldn't probably switch paravirtualizations after boot, but that's ok ;) it's not like hypervisor support should be a module anyway ^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <20061115231626.GC31879@stusta.de>]
* Re: 2.6.19-rc5-mm2: paravirt X86_PAE=y compile error [not found] ` <20061115231626.GC31879@stusta.de> @ 2006-11-15 23:36 ` Andrew Morton 2006-11-16 1:30 ` Zachary Amsden 2006-11-28 23:36 ` Randy Dunlap 0 siblings, 2 replies; 7+ messages in thread From: Andrew Morton @ 2006-11-15 23:36 UTC (permalink / raw) To: Adrian Bunk; +Cc: virtualization@lists.osdl.org, linux-kernel On Thu, 16 Nov 2006 00:16:26 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Paravirt breaks CONFIG_X86_PAE=y compilation: > > <-- snip --> > > ... > CC init/main.o > In file included from include2/asm/pgtable.h:245, > from > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/mm.h:40, > from > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/poll.h:11, > from > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/rtc.h:113, > from > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/efi.h:19, > from > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/init/main.c:43: > include2/asm/pgtable-3level.h:108: error: redefinition of 'pte_clear' > include2/asm/paravirt.h:365: error: previous definition of 'pte_clear' was here > include2/asm/pgtable-3level.h:115: error: redefinition of 'pmd_clear' > include2/asm/paravirt.h:370: error: previous definition of 'pmd_clear' was here > make[2]: *** [init/main.o] Error 1 > So it does. Zach will save us. How come allmodconfig doesn't select highmem? ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.6.19-rc5-mm2: paravirt X86_PAE=y compile error 2006-11-15 23:36 ` 2.6.19-rc5-mm2: paravirt X86_PAE=y compile error Andrew Morton @ 2006-11-16 1:30 ` Zachary Amsden 2006-11-16 2:27 ` Chris Wright 2006-11-28 23:36 ` Randy Dunlap 1 sibling, 1 reply; 7+ messages in thread From: Zachary Amsden @ 2006-11-16 1:30 UTC (permalink / raw) To: Andrew Morton Cc: Adrian Bunk, Rusty Russell, linux-kernel, virtualization@lists.osdl.org [-- Attachment #1: Type: text/plain, Size: 1265 bytes --] Andrew Morton wrote: > On Thu, 16 Nov 2006 00:16:26 +0100 > Adrian Bunk <bunk@stusta.de> wrote: > > >> Paravirt breaks CONFIG_X86_PAE=y compilation: >> >> <-- snip --> >> >> ... >> CC init/main.o >> In file included from include2/asm/pgtable.h:245, >> from >> /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/mm.h:40, >> from >> /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/poll.h:11, >> from >> /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/rtc.h:113, >> from >> /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/efi.h:19, >> from >> /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/init/main.c:43: >> include2/asm/pgtable-3level.h:108: error: redefinition of 'pte_clear' >> include2/asm/paravirt.h:365: error: previous definition of 'pte_clear' was here >> include2/asm/pgtable-3level.h:115: error: redefinition of 'pmd_clear' >> include2/asm/paravirt.h:370: error: previous definition of 'pmd_clear' was here >> make[2]: *** [init/main.o] Error 1 >> >> > > So it does. Zach will save us. > > Well that shouldn't have happened. Must have been some reject that went unnoticed? Try this. [-- Attachment #2: pae-fix.patch --] [-- Type: text/plain, Size: 2118 bytes --] Save big on PAE patches, now cheaper by the dozen! I hope this doesn't trip someone's ham filter. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.18/include/asm-i386/pgtable-3level.h =================================================================== --- linux-2.6.18.orig/include/asm-i386/pgtable-3level.h 2006-11-10 14:49:51.000000000 -0800 +++ linux-2.6.18/include/asm-i386/pgtable-3level.h 2006-11-15 17:26:54.000000000 -0800 @@ -78,26 +78,6 @@ static inline void set_pte_present(struc set_64bit((unsigned long long *)(pmdptr),pmd_val(pmdval)) #define set_pud(pudptr,pudval) \ (*(pudptr) = (pudval)) -#endif - -/* - * Pentium-II erratum A13: in PAE mode we explicitly have to flush - * the TLB via cr3 if the top-level pgd is changed... - * We do not let the generic code free and clear pgd entries due to - * this erratum. - */ -static inline void pud_clear (pud_t * pud) { } - -#define pud_page(pud) \ -((struct page *) __va(pud_val(pud) & PAGE_MASK)) - -#define pud_page_vaddr(pud) \ -((unsigned long) __va(pud_val(pud) & PAGE_MASK)) - - -/* Find an entry in the second-level page table.. */ -#define pmd_offset(pud, address) ((pmd_t *) pud_page(*(pud)) + \ - pmd_index(address)) /* * For PTEs and PDEs, we must clear the P-bit first when clearing a page table @@ -118,6 +98,26 @@ static inline void pmd_clear(pmd_t *pmd) smp_wmb(); *(tmp + 1) = 0; } +#endif + +/* + * Pentium-II erratum A13: in PAE mode we explicitly have to flush + * the TLB via cr3 if the top-level pgd is changed... + * We do not let the generic code free and clear pgd entries due to + * this erratum. + */ +static inline void pud_clear (pud_t * pud) { } + +#define pud_page(pud) \ +((struct page *) __va(pud_val(pud) & PAGE_MASK)) + +#define pud_page_vaddr(pud) \ +((unsigned long) __va(pud_val(pud) & PAGE_MASK)) + + +/* Find an entry in the second-level page table.. */ +#define pmd_offset(pud, address) ((pmd_t *) pud_page(*(pud)) + \ + pmd_index(address)) #define __HAVE_ARCH_PTEP_GET_AND_CLEAR static inline pte_t ptep_get_and_clear(struct mm_struct *mm, unsigned long addr, pte_t *ptep) ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.6.19-rc5-mm2: paravirt X86_PAE=y compile error 2006-11-16 1:30 ` Zachary Amsden @ 2006-11-16 2:27 ` Chris Wright 2006-11-16 7:05 ` Andi Kleen 0 siblings, 1 reply; 7+ messages in thread From: Chris Wright @ 2006-11-16 2:27 UTC (permalink / raw) To: Zachary Amsden Cc: Andrew Morton, virtualization@lists.osdl.org, linux-kernel, Adrian Bunk * Zachary Amsden (zach@vmware.com) wrote: > Well that shouldn't have happened. Must have been some reject that went > unnoticed? Try this. Thanks Zach, added to the pv patchqueue as well. -chris ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.6.19-rc5-mm2: paravirt X86_PAE=y compile error 2006-11-16 2:27 ` Chris Wright @ 2006-11-16 7:05 ` Andi Kleen 0 siblings, 0 replies; 7+ messages in thread From: Andi Kleen @ 2006-11-16 7:05 UTC (permalink / raw) To: virtualization Cc: Chris Wright, Zachary Amsden, Andrew Morton, linux-kernel, Adrian Bunk On Thursday 16 November 2006 03:27, Chris Wright wrote: > * Zachary Amsden (zach@vmware.com) wrote: > > Well that shouldn't have happened. Must have been some reject that went > > unnoticed? Try this. > > Thanks Zach, added to the pv patchqueue as well. That was one of the things that got fixed in paravirt-compile too iirc -Andi ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.6.19-rc5-mm2: paravirt X86_PAE=y compile error 2006-11-15 23:36 ` 2.6.19-rc5-mm2: paravirt X86_PAE=y compile error Andrew Morton 2006-11-16 1:30 ` Zachary Amsden @ 2006-11-28 23:36 ` Randy Dunlap 1 sibling, 0 replies; 7+ messages in thread From: Randy Dunlap @ 2006-11-28 23:36 UTC (permalink / raw) To: Andrew Morton Cc: zippel, virtualization@lists.osdl.org, linux-kernel, Adrian Bunk On Wed, 15 Nov 2006 15:36:14 -0800 Andrew Morton wrote: > On Thu, 16 Nov 2006 00:16:26 +0100 > Adrian Bunk <bunk@stusta.de> wrote: > > > Paravirt breaks CONFIG_X86_PAE=y compilation: > > > > <-- snip --> > > > > ... > > CC init/main.o > > In file included from include2/asm/pgtable.h:245, > > from > > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/mm.h:40, > > from > > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/poll.h:11, > > from > > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/rtc.h:113, > > from > > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/efi.h:19, > > from > > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/init/main.c:43: > > include2/asm/pgtable-3level.h:108: error: redefinition of 'pte_clear' > > include2/asm/paravirt.h:365: error: previous definition of 'pte_clear' was here > > include2/asm/pgtable-3level.h:115: error: redefinition of 'pmd_clear' > > include2/asm/paravirt.h:370: error: previous definition of 'pmd_clear' was here > > make[2]: *** [init/main.o] Error 1 > > > > So it does. Zach will save us. > > How come allmodconfig doesn't select highmem? Must be because of "choice" and its default: choice prompt "High Memory Support" default NOHIGHMEM Changing the default fixes it. I suppose conf.c could be hacked to do something different on choices, but it's not clear how/what to do there as a general rule. --- From: Randy Dunlap <randy.dunlap@oracle.com> Make ix86 default to HIGHMEM4G instead of NOHIGHMEM. Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com> --- arch/i386/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- linux-2.6.19-rc6-git10.orig/arch/i386/Kconfig +++ linux-2.6.19-rc6-git10/arch/i386/Kconfig @@ -443,7 +443,8 @@ source "drivers/firmware/Kconfig" choice prompt "High Memory Support" - default NOHIGHMEM + default HIGHMEM4G if !X86_NUMAQ + default HIGHMEM64G if X86_NUMAQ config NOHIGHMEM bool "off" ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2006-11-28 23:36 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20061114014125.dd315fff.akpm@osdl.org>
[not found] ` <20061114225622.GO22565@stusta.de>
2006-11-14 23:09 ` 2.6.19-rc5-mm2: warnings in MODPOST and later Andrew Morton
2006-11-15 7:42 ` Arjan van de Ven
[not found] ` <20061115231626.GC31879@stusta.de>
2006-11-15 23:36 ` 2.6.19-rc5-mm2: paravirt X86_PAE=y compile error Andrew Morton
2006-11-16 1:30 ` Zachary Amsden
2006-11-16 2:27 ` Chris Wright
2006-11-16 7:05 ` Andi Kleen
2006-11-28 23:36 ` Randy Dunlap
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).