All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Patrick Colp <pjcolp@cs.ubc.ca>
Cc: xen-devel@lists.xensource.com,
	Keir Fraser <keir.fraser@eu.citrix.com>,
	Grzegorz Milos <gm281@cam.ac.uk>,
	Andrew Peace <Andrew.Peace@eu.citrix.com>
Subject: Re: [PATCH] Paging and memory sharing for HVM guests
Date: Thu, 17 Dec 2009 12:15:52 -0800	[thread overview]
Message-ID: <4B2A9178.2000404@goop.org> (raw)
In-Reply-To: <4B2A8FBE.4090000@cs.ubc.ca>

On 12/17/2009 12:08 PM, Patrick Colp wrote:
> That's odd. I just pulled a fresh copy of xen-unstable and built xen 
> and the tools. Both compiled with no errors or problems. Maybe this is 
> some sort of distro-dependent problem?

Possibly.  I'm using Fedora 11 on this machine, and it also fails in 
Fedora 12.  For the sleep() prototype, is it possible your versions 
headers are implicitly including unistd.h, or otherwise have a prototype 
for it?

And for the xen/mem_event.h problem, might you have that header 
installed somewhere?

     J

>
>
> Patrick
>
>
> Jeremy Fitzhardinge wrote:
>> On 12/16/2009 03:14 PM, Grzegorz Milos wrote:
>>> The series of 46 patches attached to this email contain the initial
>>> implementation of memory paging and sharing for Xen. Patrick Colp
>>> leads the work on the pager, and I am mostly responsible for memory
>>> sharing. We would be grateful for any comments/suggestions you might
>>> have. Individual patches are labeled with comments describing their
>>> purpose and a sign-off footnote. Of course we are happy to discuss
>>> them in more detail, as required. Assuming that there are no major
>>> objections against including them in the mainstream xen-unstable tree,
>>> we would like to move future development to that tree.
>>
>> I'm getting compile errors:
>>
>> gcc  -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g 
>> -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
>> -Wno-unused-value -Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD 
>> -MF .bidir-daemon.o.d  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE  
>> -Werror -Wno-unused -I../include -I../../tools/libxc 
>> -I../../tools/include -D_GNU_SOURCE -fPIC -g 
>> -Wp,-MD,.bidir-daemon.o.d -c -o bidir-daemon.o bidir-daemon.c
>> cc1: warnings being treated as errors
>> bidir-daemon.c: In function ‘bidir_daemon’:
>> bidir-daemon.c:74: error: implicit declaration of function ‘sleep’
>> make[3]: *** [bidir-daemon.o] Error 1
>> make[3]: Leaving directory `/home/jeremy/hg/xen/unstable/tools/memshr'
>>
>> and
>>
>> make[3]: Entering directory 
>> `/home/jeremy/hg/xen/unstable/tools/xenpaging'
>> gcc  -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g 
>> -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
>> -Wno-unused-value -Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD 
>> -MF .file_ops.o.d  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE  -I 
>> ../../tools/python/xen/lowlevel/xc -I ./ -I../../tools/libxc 
>> -I../../tools/include -I../../tools/xenstore -I../../tools/include 
>> -Werror -Wno-unused -g -Wp,-MD,.file_ops.o.d -c -o file_ops.o file_ops.c
>> gcc  -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g 
>> -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
>> -Wno-unused-value -Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD 
>> -MF .xc.o.d  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE  -I 
>> ../../tools/python/xen/lowlevel/xc -I ./ -I../../tools/libxc 
>> -I../../tools/include -I../../tools/xenstore -I../../tools/include 
>> -Werror -Wno-unused -g -Wp,-MD,.xc.o.d -c -o xc.o xc.c
>> In file included from xc.c:29:
>> xc.h:29:27: error: xen/mem_event.h: No such file or directory
>> make[3]: *** [xc.o] Error 1
>> make[3]: Leaving directory 
>> `/home/jeremy/hg/xen/unstable/tools/xenpaging'
>>
>>
>> The first is easily fixed by adding #include <unistd.h>, but I 
>> haven't looked into the second yet.
>>
>> Thanks,
>> J
>

  reply	other threads:[~2009-12-17 20:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 23:14 [PATCH] Paging and memory sharing for HVM guests Grzegorz Milos
2009-12-16 23:52 ` Dan Magenheimer
2009-12-17  0:00   ` Patrick Colp
2009-12-17  0:15     ` Dan Magenheimer
2009-12-17  8:47 ` Jan Beulich
2009-12-17 13:08   ` Grzegorz Milos
2009-12-17 15:11     ` Patrick Colp
2009-12-17 11:19 ` Jan Beulich
2009-12-17 15:59   ` Keir Fraser
2009-12-17 18:34     ` Jeremy Fitzhardinge
2009-12-17 16:19 ` Dan Magenheimer
2009-12-18 18:05   ` Dan Magenheimer
2009-12-18 18:51     ` Patrick Colp
2009-12-20 15:04     ` Grzegorz Milos
2009-12-21 16:52       ` Dan Magenheimer
2009-12-17 16:38 ` Konrad Rzeszutek Wilk
2009-12-17 16:59   ` Jan Beulich
2009-12-17 17:05     ` Patrick Colp
2009-12-18  8:08       ` Jan Beulich
2009-12-18 17:29         ` Patrick Colp
2009-12-18 18:36           ` Konrad Rzeszutek Wilk
2009-12-18 18:54             ` Patrick Colp
2009-12-17 18:27     ` Konrad Rzeszutek Wilk
2009-12-17 17:02   ` Patrick Colp
2009-12-17 17:26     ` Patrick Colp
2009-12-17 19:47 ` Jeremy Fitzhardinge
2009-12-17 20:08   ` Patrick Colp
2009-12-17 20:15     ` Jeremy Fitzhardinge [this message]
2009-12-17 20:16       ` Jeremy Fitzhardinge
2009-12-17 20:22         ` Patrick Colp
2009-12-18 16:00 ` Jan Beulich
2009-12-18 17:16   ` Patrick Colp
2009-12-22 10:49 ` Jan Beulich
2009-12-22 11:34   ` Keir Fraser
2009-12-22 12:56     ` Jan Beulich
2009-12-22 13:35       ` Keir Fraser
2010-01-04 14:14 ` Jan Beulich
2010-01-04 15:32   ` Keir Fraser
2010-01-04 16:30     ` Jan Beulich
2010-01-05  7:51       ` Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B2A9178.2000404@goop.org \
    --to=jeremy@goop.org \
    --cc=Andrew.Peace@eu.citrix.com \
    --cc=gm281@cam.ac.uk \
    --cc=keir.fraser@eu.citrix.com \
    --cc=pjcolp@cs.ubc.ca \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.