linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: build failure after merge of the xen tree
@ 2010-10-25  2:30 Stephen Rothwell
  2010-10-25  8:38 ` Ian Campbell
  0 siblings, 1 reply; 12+ messages in thread
From: Stephen Rothwell @ 2010-10-25  2:30 UTC (permalink / raw)
  To: Jeremy Fitzhardinge, Xen Devel
  Cc: linux-next, linux-kernel, Ian Campbell, Stefano Stabellini,
	Konrad Rzeszutek Wilk

[-- Attachment #1: Type: text/plain, Size: 613 bytes --]

Hi all,

After merging the xen tree, today's linux-next build (s86_64 allmodconfig)
failed like this:

arch/x86/xen/setup.c: In function 'xen_memory_setup':
arch/x86/xen/setup.c:161: error: implicit declaration of function 'xen_initial_domain'

Caused by commit 9e9a5fcb04e3af077d1be32710298b852210d93f ("xen: use host
E820 map for dom0").  See Rule 1 from Documentation/SubmitChecklist.

I have used the xen tree from next-20101021 for today (due to the complex
conflict in Friday's tree).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread
* linux-next: build failure after merge of the xen tree
@ 2011-09-15  5:27 Stephen Rothwell
  2011-09-15  9:10 ` Jeremy Fitzhardinge
  0 siblings, 1 reply; 12+ messages in thread
From: Stephen Rothwell @ 2011-09-15  5:27 UTC (permalink / raw)
  To: Jeremy Fitzhardinge, Xen Devel; +Cc: linux-next, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 827 bytes --]

Hi all,

After merging the xen tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

arch/x86/xen/time.c: In function 'xen_set_wallclock':
arch/x86/xen/time.c:204:25: error: storage size of 'op' isn't known
arch/x86/xen/time.c:211:11: error: 'XENPF_settime' undeclared (first use in this function)
arch/x86/xen/time.c:211:11: note: each undeclared identifier is reported only once for each function it appears in
arch/x86/xen/time.c:216:2: error: implicit declaration of function 'HYPERVISOR_dom0_op'
arch/x86/xen/time.c:204:25: warning: unused variable 'op'

Caused by commit 7b11a83f592a ("xen/dom0: set wallclock time in Xen").

I have used teh xen tree from next-20110914 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread
* linux-next: build failure after merge of the xen tree
@ 2010-10-27  2:02 Stephen Rothwell
  0 siblings, 0 replies; 12+ messages in thread
From: Stephen Rothwell @ 2010-10-27  2:02 UTC (permalink / raw)
  To: Jeremy Fitzhardinge, Xen Devel; +Cc: linux-next, linux-kernel

Hi all,

After merging the xen tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

arch/x86/xen/setup.c: In function 'xen_add_extra_mem':
arch/x86/xen/setup.c:65: error: implicit declaration of function 'reserve_early'

Caused by commit 42ee1471e9b879479a15debac752314a596c738e ("xen:
implement "extra" memory to reserve space for pages not present at boot")
interacting with commit a9ce6bc15100023b411f8117e53a016d61889800 ("x86,
memblock: Replace e820_/_early string with memblock_").  This latter
commit was in the xen tree yesterday (via a merge of tip/core/memblock)
but has been removed today (but it is in Linus' tree).

Linus will need this fixup patch when he merges the xen tree.  I have
applied it to linux-next today and can carry it as necessary.

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, 27 Oct 2010 12:57:06 +1100
Subject: [PATCH] xen: merge fixup for reserve_early name change

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 arch/x86/xen/setup.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
index 1163bc5..105db25 100644
--- a/arch/x86/xen/setup.c
+++ b/arch/x86/xen/setup.c
@@ -62,7 +62,7 @@ static __init void xen_add_extra_mem(unsigned long pages)
 	e820_add_region(extra_start, size, E820_RAM);
 	sanitize_e820_map(e820.map, ARRAY_SIZE(e820.map), &e820.nr_map);
 
-	reserve_early(extra_start, extra_start + size, "XEN EXTRA");
+	memblock_x86_reserve_range(extra_start, extra_start + size, "XEN EXTRA");
 
 	xen_extra_mem_size += size;
 
-- 
1.7.2.3

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

^ permalink raw reply related	[flat|nested] 12+ messages in thread
* linux-next: build failure after merge of the xen tree
@ 2010-07-28  4:18 Stephen Rothwell
  0 siblings, 0 replies; 12+ messages in thread
From: Stephen Rothwell @ 2010-07-28  4:18 UTC (permalink / raw)
  To: Jeremy Fitzhardinge, Xen Devel; +Cc: linux-next, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

Hi all,

After merging the xen tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

arch/x86/xen/enlighten.c:71: error: __pcpu_scope_xen_vcpu causes a section type conflict
arch/x86/xen/enlighten.c:72: error: __pcpu_scope_xen_vcpu_info causes a section type conflict
arch/x86/xen/enlighten.c:71: error: __pcpu_unique_xen_vcpu causes a section type conflict
arch/x86/xen/enlighten.c:72: error: __pcpu_unique_xen_vcpu_info causes a section type conflict
arch/x86/xen/enlighten.c:565: error: __pcpu_unique_idt_desc causes a section type conflict
arch/x86/xen/enlighten.c:767: error: __pcpu_unique_xen_cr0_value causes a section type conflict

Presumably because commit "support multiple .discard.* sections to avoid
section type conflicts" was dropped from the xen tree today.

I have used the xen tree from next-20100727 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread
* linux-next: build failure after merge of the xen tree
@ 2010-07-23  4:01 Stephen Rothwell
  2010-07-23  4:48 ` Jeremy Fitzhardinge
                   ` (2 more replies)
  0 siblings, 3 replies; 12+ messages in thread
From: Stephen Rothwell @ 2010-07-23  4:01 UTC (permalink / raw)
  To: Jeremy Fitzhardinge; +Cc: linux-next, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 898 bytes --]

Hi Jeremy,

After merging the xen tree, today's linux-next build (86_64 allmodconfig)
failed like this:

arch/x86/xen/enlighten.c:71: error: __pcpu_scope_xen_vcpu causes a section type conflict
arch/x86/xen/enlighten.c:72: error: __pcpu_scope_xen_vcpu_info causes a section type conflict
arch/x86/xen/enlighten.c:71: error: __pcpu_unique_xen_vcpu causes a section type conflict
arch/x86/xen/enlighten.c:72: error: __pcpu_unique_xen_vcpu_info causes a section type conflict
arch/x86/xen/enlighten.c:558: error: __pcpu_unique_idt_desc causes a section type conflict
arch/x86/xen/enlighten.c:760: error: __pcpu_unique_xen_cr0_value causes a section type conflict

Not sure what has caused this.  I have dropped the xen tree for today.

gcc version 4.4.4 binutils version 2.20.1.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

^ permalink raw reply	[flat|nested] 12+ messages in thread
end of thread, other threads:[~2011-09-15  9:10 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-25  2:30 linux-next: build failure after merge of the xen tree Stephen Rothwell
2010-10-25  8:38 ` Ian Campbell
2010-10-25 23:57   ` Jeremy Fitzhardinge
  -- strict thread matches above, loose matches on Subject: below --
2011-09-15  5:27 Stephen Rothwell
2011-09-15  9:10 ` Jeremy Fitzhardinge
2010-10-27  2:02 Stephen Rothwell
2010-07-28  4:18 Stephen Rothwell
2010-07-23  4:01 Stephen Rothwell
2010-07-23  4:48 ` Jeremy Fitzhardinge
2010-07-23  5:56 ` Jeremy Fitzhardinge
2010-07-23  6:05 ` Jeremy Fitzhardinge
2010-07-23  6:59   ` Stephen Rothwell

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).