I tried to compile xen with ADV_SCHED_HISTO set and a header file it needs is missing from the tree. make[2]: Entering directory `/home/rharper/work/openhype/xen/unstable/20050525/modified/xen/common'' gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -iwithprefix include -Wall -Werror -Wno-pointer-arith -pipe -I/home/rharper/work/openhype/xen/unstable/20050525/modified/xen/include -I/home/rharper/work/openhype/xen/unstable/20050525/modified/xen/include/asm-x86/mach-default -O3 -fomit-frame-pointer -msoft-float -m32 -march=i686 -DNDEBUG -c schedule.c -o schedule.o schedule.c:47:32: xen/adv_sched_hist.h: No such file or directory schedule.c: In function `do_block'': schedule.c:253: warning: implicit declaration of function `adv_sched_hist_start'' schedule.c: In function `__enter_scheduler'': schedule.c:492: warning: implicit declaration of function `adv_sched_hist_from_stop''schedule.c:540: warning: implicit declaration of function `adv_sched_hist_to_stop'' schedule.c: In function `print_sched_histo'': schedule.c:764: error: structure has no member named `from_hist'' schedule.c:766: error: structure has no member named `from_hist'' schedule.c:768: error: structure has no member named `from_hist'' schedule.c:783: error: structure has no member named `from_hist'' schedule.c:785: error: structure has no member named `to_hist'' schedule.c:787: error: structure has no member named `to_hist'' schedule.c: In function `reset_sched_histo'': schedule.c:801: error: structure has no member named `to_hist'' schedule.c:801: error: structure has no member named `from_hist'' schedule.c:802: error: structure has no member named `save_tsc'' make[2]: *** [schedule.o] Error 1 -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx (512) 838-9253 T/L: 678-9253 ryanh@us.ibm.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
* Ryan Harper <ryanh@us.ibm.com> [2005-05-25 10:15]:> I tried to compile xen with ADV_SCHED_HISTO set and a header file it > needs is missing from the tree.All reference to ADV_SCHED_HISTO was removed from the tree last night. I couldn''t find a changelog entry corresponding to the change. Any reason why it wasn''t added in instead, and why there was no change long entry? -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx (512) 838-9253 T/L: 678-9253 ryanh@us.ibm.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ryan Harper wrote:> * Ryan Harper <ryanh@us.ibm.com> [2005-05-25 10:15]: > >>I tried to compile xen with ADV_SCHED_HISTO set and a header file it >>needs is missing from the tree. > > All reference to ADV_SCHED_HISTO was removed from the tree last night. > I couldn''t find a changelog entry corresponding to the change. Any > reason why it wasn''t added in instead, and why there was no change long > entry?ChangeSet 1.1548 2005/05/25 11:36:59 kaf24@firebug.cl.cam.ac.uk Move to Linux''s cpumask_t and ''hotplug'' multi-processor booting interfaces. This also brings apic.c and various other files closer to their Linux 2.6 equivalents. Simplified the scheduler interfaces a little (particularly per-cpu and idle-domain initialisation). Signed-off-by: Keir Fraser <keir@xensource.com> I guess that''s "simplifying the scheduler interface"...? -- Hollis Blanchard IBM Linux Technology Center _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
* Hollis Blanchard <hollisb@us.ibm.com> [2005-05-26 11:24]:> Ryan Harper wrote: > > * Ryan Harper <ryanh@us.ibm.com> [2005-05-25 10:15]: > > > >>I tried to compile xen with ADV_SCHED_HISTO set and a header file it > >>needs is missing from the tree. > > > > All reference to ADV_SCHED_HISTO was removed from the tree last night. > > I couldn''t find a changelog entry corresponding to the change. Any > > reason why it wasn''t added in instead, and why there was no change long > > entry? > > ChangeSet 1.1548 2005/05/25 11:36:59 kaf24@firebug.cl.cam.ac.uk > Move to Linux''s cpumask_t and ''hotplug'' multi-processor booting > interfaces. This also brings apic.c and various other files closer to > their Linux 2.6 equivalents. Simplified the scheduler interfaces a > little (particularly per-cpu and idle-domain initialisation). > Signed-off-by: Keir Fraser <keir@xensource.com> > > I guess that''s "simplifying the scheduler interface"...?Hollis, thanks for pointing that out. I looked at that on xen-changelog, but I didnt see the above change in there. I don''t use a bk client and as Jon Mason was saying, all changes in a change set don''t show up in the xen-changelog message. Who runs the xen-changelog bot that commits? Any reason why the whole diff isnt included in the message sent to the mailing list? -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx (512) 838-9253 T/L: 678-9253 ryanh@us.ibm.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Hollis, thanks for pointing that out. I looked at that on > xen-changelog, but I didnt see the above change in there. I > don''t use a bk client and as Jon Mason was saying, all > changes in a change set don''t show up in the xen-changelog message. > > Who runs the xen-changelog bot that commits? Any reason why > the whole diff isnt included in the message sent to the mailing list?That would be Rik. I think I''d prefer it if we sent the whole diff too. We''re going to have to rejig all this stuff when we make changes to the SCM setup anyhow... Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Fri, 27 May 2005, Ian Pratt wrote:> > Who runs the xen-changelog bot that commits? Any reason why > > the whole diff isnt included in the message sent to the mailing list? > > That would be Rik. I think I''d prefer it if we sent the whole diff too.Other people on the xen-changelog list have asked me to limit the size of the mail sent ;) I have to admit that I prefer full diffs myself, too...> We''re going to have to rejig all this stuff when we make changes to the > SCM setup anyhow...Indeed. Lets decide on what we want the new changelog diffs to look like. -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel