Hi, In continuation with my previous post, I am able to login to the compiled Xen. But it is continuing to run on credit scheduler even if i modify the kernel parameters to run using round robin scheduler. I have pasted the contents of the /boot/grub/menu.lst file. title Xen -- openSUSE 11.0 - 2.6.18.8 manually compiled AGAIN root (hd0,4) kernel /boot/xen.gz module /boot/vmlinuz-2.6.18.8-xen0 root=/dev/disk/by-id/scsi-SATA_Hitachi_HTS5416_SB2D04E4CE7YEE-part5 showopts *sched=rrobin* vga=0x314 module /boot/initrd-2.6.18-xen0 Incidentally, even if i give sched=sedf, it still runs only on credit scheduler. Please let me know your feedback on this issue. My aim is to study the performance statistics of credit, sedf and new RR scheduler. It would be great if you could give me any pointers to measure scheduler performance or get statistics from the system. Thanks & Regards Ananth ---------- Forwarded message ---------- From: Ananth <cbananth@gmail.com> Date: Mon, Apr 27, 2009 at 6:45 PM Subject: Re: [Xen-devel] Fwd: Error while compiling with new RR scheduler To: George Dunlap <dunlapg@umich.edu> Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> Hello, Thank you so much for pointing it out. How could I miss something so obvious. I am able to compile it now. I will get back to you in case I get into any issues during run time. Thank you. Regards Ananth On Mon, Apr 27, 2009 at 6:29 PM, George Dunlap <dunlapg@umich.edu> wrote:> The message says it pretty clearly: you return the value of ret, but > there are control paths in the function for which ret.task is not set. > Namely, if list_empty(runq) is true, then you will return an > uninitialized value, which may be anything (garbage on the stack, > NULL, &c). This will most likely cause Xen to crash, as > xen/common/schedule.c assumes that ret.task will be a valid, non-NULL > pointer. > > If you happen to know that runq is never empty, then you don''t need > the if statement. If it may be empty, then you need an else clause to > return the idle vcpu for that processor. > > -George > > 2009/4/24 Ananth <cbananth@gmail.com>: > > Hi, > > I figured out that the error was because of a missing '' ; '' . This has > been fixed now. I have attached the modified code. > > While compiling I am getting the below error message. > > > > cc1: warnings being treated as errors > > sched_rrobin.c: In function ‘rrobin_schedule’: > > sched_rrobin.c:74: error: ‘ret.task’ may be used uninitialized in this > function > > > > Please guide. > > > > Thanks & Regards > > Ananth > > > > > > ---------- Forwarded message ---------- > > From: Ananth <cbananth@gmail.com> > > Date: Fri, Apr 24, 2009 at 7:25 PM > > Subject: Error while compiling with new RR scheduler > > To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> > > > > > > Hi, > > Please find attached the source code of Round Robin scheduler which I am > trying to add to Xen 3.3.1. > > I am facing the following error messages while compiling the same. > > > > sched_rrobin.c:31: error: two or more data types in declaration > specifiers > > > > sched_rrobin.c: In function ‘rrobin_vcpu_init’: > > > > sched_rrobin.c:34: error: incompatible types in return > > > > sched_rrobin.c:51: error: incompatible types in return > > > > sched_rrobin.c:94: error: initialization from incompatible pointer type > > > > I believe the error in line 94 is causing the rest of the error messages. > I have checked with the structure definition in sched-if.h as well as the > implementation of the same in other schedulers such as SEDF and Credit. > > > > Request you to kindly provide your feedback regarding the same. > > > > Thanks & Regards > > Ananth > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
George Dunlap
2009-Apr-27 20:41 UTC
[Xen-devel] Re: Issues while running Xen with new RR scheduler
You need to pass the arguments to xen on the xen command line, not the dom0 kernel command line. So the following line should be: kernel /boot/xen.gz sched=rrobin (I haven''t checked to make sure that "sched" is the right parameter.) -George On Mon, Apr 27, 2009 at 7:39 PM, Ananth <cbananth@gmail.com> wrote:> Hi, > In continuation with my previous post, I am able to login to the compiled > Xen. But it is continuing to run on credit scheduler even if i modify the > kernel parameters to run using round robin scheduler. > I have pasted the contents of the /boot/grub/menu.lst file. > > title Xen -- openSUSE 11.0 - 2.6.18.8 manually compiled AGAIN > root (hd0,4) > kernel /boot/xen.gz > module /boot/vmlinuz-2.6.18.8-xen0 > root=/dev/disk/by-id/scsi-SATA_Hitachi_HTS5416_SB2D04E4CE7YEE-part5 showopts > sched=rrobin vga=0x314 > module /boot/initrd-2.6.18-xen0 > > Incidentally, even if i give sched=sedf, it still runs only on credit > scheduler. Please let me know your feedback on this issue. My aim is to > study the performance statistics of credit, sedf and new RR scheduler. It > would be great if you could give me any pointers to measure scheduler > performance or get statistics from the system. > > Thanks & Regards > Ananth > > ---------- Forwarded message ---------- > From: Ananth <cbananth@gmail.com> > Date: Mon, Apr 27, 2009 at 6:45 PM > Subject: Re: [Xen-devel] Fwd: Error while compiling with new RR scheduler > To: George Dunlap <dunlapg@umich.edu> > Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> > > > Hello, > Thank you so much for pointing it out. How could I miss something so > obvious. I am able to compile it now. I will get back to you in case I get > into any issues during run time. > > Thank you. > > Regards > Ananth > > On Mon, Apr 27, 2009 at 6:29 PM, George Dunlap <dunlapg@umich.edu> wrote: >> >> The message says it pretty clearly: you return the value of ret, but >> there are control paths in the function for which ret.task is not set. >> Namely, if list_empty(runq) is true, then you will return an >> uninitialized value, which may be anything (garbage on the stack, >> NULL, &c). This will most likely cause Xen to crash, as >> xen/common/schedule.c assumes that ret.task will be a valid, non-NULL >> pointer. >> >> If you happen to know that runq is never empty, then you don''t need >> the if statement. If it may be empty, then you need an else clause to >> return the idle vcpu for that processor. >> >> -George >> >> 2009/4/24 Ananth <cbananth@gmail.com>: >> > Hi, >> > I figured out that the error was because of a missing '' ; '' . This has >> > been fixed now. I have attached the modified code. >> > While compiling I am getting the below error message. >> > >> > cc1: warnings being treated as errors >> > sched_rrobin.c: In function ‘rrobin_schedule’: >> > sched_rrobin.c:74: error: ‘ret.task’ may be used uninitialized in this >> > function >> > >> > Please guide. >> > >> > Thanks & Regards >> > Ananth >> > >> > >> > ---------- Forwarded message ---------- >> > From: Ananth <cbananth@gmail.com> >> > Date: Fri, Apr 24, 2009 at 7:25 PM >> > Subject: Error while compiling with new RR scheduler >> > To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> >> > >> > >> > Hi, >> > Please find attached the source code of Round Robin scheduler which I am >> > trying to add to Xen 3.3.1. >> > I am facing the following error messages while compiling the same. >> > >> > sched_rrobin.c:31: error: two or more data types in declaration >> > specifiers >> > >> > sched_rrobin.c: In function ‘rrobin_vcpu_init’: >> > >> > sched_rrobin.c:34: error: incompatible types in return >> > >> > sched_rrobin.c:51: error: incompatible types in return >> > >> > sched_rrobin.c:94: error: initialization from incompatible pointer type >> > >> > I believe the error in line 94 is causing the rest of the error >> > messages. I have checked with the structure definition in sched-if.h as well >> > as the implementation of the same in other schedulers such as SEDF and >> > Credit. >> > >> > Request you to kindly provide your feedback regarding the same. >> > >> > Thanks & Regards >> > Ananth >> > >> > >> > _______________________________________________ >> > Xen-devel mailing list >> > Xen-devel@lists.xensource.com >> > http://lists.xensource.com/xen-devel >> > >> > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ananth
2009-Apr-27 22:39 UTC
[Xen-devel] Re: Issues while running Xen with new RR scheduler
Hi, Thanks for your suggestion. I was able to change scheduler from credit to sedf. "sched" is the correct parameter. However when I try to select sched=rrobin, the system gets ready to boot and then everything goes blank. I have attached the round robin scheduler code along with this mail. Could you give me your feedback on whether I have missed out something. Thank you very much once again. Warm Regards Ananth On Tue, Apr 28, 2009 at 2:11 AM, George Dunlap <dunlapg@umich.edu> wrote:> You need to pass the arguments to xen on the xen command line, not the > dom0 kernel command line. So the following line should be: > > kernel /boot/xen.gz sched=rrobin > > (I haven''t checked to make sure that "sched" is the right parameter.) > > -George > > On Mon, Apr 27, 2009 at 7:39 PM, Ananth <cbananth@gmail.com> wrote: > > Hi, > > In continuation with my previous post, I am able to login to the compiled > > Xen. But it is continuing to run on credit scheduler even if i modify the > > kernel parameters to run using round robin scheduler. > > I have pasted the contents of the /boot/grub/menu.lst file. > > > > title Xen -- openSUSE 11.0 - 2.6.18.8 manually compiled AGAIN > > root (hd0,4) > > kernel /boot/xen.gz > > module /boot/vmlinuz-2.6.18.8-xen0 > > root=/dev/disk/by-id/scsi-SATA_Hitachi_HTS5416_SB2D04E4CE7YEE-part5 > showopts > > sched=rrobin vga=0x314 > > module /boot/initrd-2.6.18-xen0 > > > > Incidentally, even if i give sched=sedf, it still runs only on credit > > scheduler. Please let me know your feedback on this issue. My aim is to > > study the performance statistics of credit, sedf and new RR scheduler. It > > would be great if you could give me any pointers to measure scheduler > > performance or get statistics from the system. > > > > Thanks & Regards > > Ananth > > > > ---------- Forwarded message ---------- > > From: Ananth <cbananth@gmail.com> > > Date: Mon, Apr 27, 2009 at 6:45 PM > > Subject: Re: [Xen-devel] Fwd: Error while compiling with new RR scheduler > > To: George Dunlap <dunlapg@umich.edu> > > Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> > > > > > > Hello, > > Thank you so much for pointing it out. How could I miss something so > > obvious. I am able to compile it now. I will get back to you in case I > get > > into any issues during run time. > > > > Thank you. > > > > Regards > > Ananth > > > > On Mon, Apr 27, 2009 at 6:29 PM, George Dunlap <dunlapg@umich.edu> > wrote: > >> > >> The message says it pretty clearly: you return the value of ret, but > >> there are control paths in the function for which ret.task is not set. > >> Namely, if list_empty(runq) is true, then you will return an > >> uninitialized value, which may be anything (garbage on the stack, > >> NULL, &c). This will most likely cause Xen to crash, as > >> xen/common/schedule.c assumes that ret.task will be a valid, non-NULL > >> pointer. > >> > >> If you happen to know that runq is never empty, then you don''t need > >> the if statement. If it may be empty, then you need an else clause to > >> return the idle vcpu for that processor. > >> > >> -George > >> > >> 2009/4/24 Ananth <cbananth@gmail.com>: > >> > Hi, > >> > I figured out that the error was because of a missing '' ; '' . This has > >> > been fixed now. I have attached the modified code. > >> > While compiling I am getting the below error message. > >> > > >> > cc1: warnings being treated as errors > >> > sched_rrobin.c: In function ‘rrobin_schedule’: > >> > sched_rrobin.c:74: error: ‘ret.task’ may be used uninitialized in this > >> > function > >> > > >> > Please guide. > >> > > >> > Thanks & Regards > >> > Ananth > >> > > >> > > >> > ---------- Forwarded message ---------- > >> > From: Ananth <cbananth@gmail.com> > >> > Date: Fri, Apr 24, 2009 at 7:25 PM > >> > Subject: Error while compiling with new RR scheduler > >> > To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> > >> > > >> > > >> > Hi, > >> > Please find attached the source code of Round Robin scheduler which I > am > >> > trying to add to Xen 3.3.1. > >> > I am facing the following error messages while compiling the same. > >> > > >> > sched_rrobin.c:31: error: two or more data types in declaration > >> > specifiers > >> > > >> > sched_rrobin.c: In function ‘rrobin_vcpu_init’: > >> > > >> > sched_rrobin.c:34: error: incompatible types in return > >> > > >> > sched_rrobin.c:51: error: incompatible types in return > >> > > >> > sched_rrobin.c:94: error: initialization from incompatible pointer > type > >> > > >> > I believe the error in line 94 is causing the rest of the error > >> > messages. I have checked with the structure definition in sched-if.h > as well > >> > as the implementation of the same in other schedulers such as SEDF and > >> > Credit. > >> > > >> > Request you to kindly provide your feedback regarding the same. > >> > > >> > Thanks & Regards > >> > Ananth > >> > > >> > > >> > _______________________________________________ > >> > Xen-devel mailing list > >> > Xen-devel@lists.xensource.com > >> > http://lists.xensource.com/xen-devel > >> > > >> > > > > > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
George Dunlap
2009-Apr-28 14:19 UTC
Re: [Xen-devel] Re: Issues while running Xen with new RR scheduler
Welcome to OS programming. :-) When you say, "everything goes blank", you mean that the machine reboots, or do you mean it just hangs? The main thing to do is add printks to your code to figure out where things start to go bad. If your machine is rebooting / crashing, then you''re probably dereferencing a null pointer or something like that. The best thing for this is to set up a serial console, enable the sync_console feature on the xen command line, and log the serial console output. Then you''ll have the printks as close as possible to the actual crash, which should help you narrow things down. Good luck, -George On Mon, Apr 27, 2009 at 11:39 PM, Ananth <cbananth@gmail.com> wrote:> Hi, > Thanks for your suggestion. I was able to change scheduler from credit to > sedf. "sched" is the correct parameter. > However when I try to select sched=rrobin, the system gets ready to boot and > then everything goes blank. I have attached the round robin scheduler code > along with this mail. Could you give me your feedback on whether I have > missed out something. > > Thank you very much once again. > > Warm Regards > Ananth > > On Tue, Apr 28, 2009 at 2:11 AM, George Dunlap <dunlapg@umich.edu> wrote: >> >> You need to pass the arguments to xen on the xen command line, not the >> dom0 kernel command line. So the following line should be: >> >> kernel /boot/xen.gz sched=rrobin >> >> (I haven''t checked to make sure that "sched" is the right parameter.) >> >> -George >> >> On Mon, Apr 27, 2009 at 7:39 PM, Ananth <cbananth@gmail.com> wrote: >> > Hi, >> > In continuation with my previous post, I am able to login to the >> > compiled >> > Xen. But it is continuing to run on credit scheduler even if i modify >> > the >> > kernel parameters to run using round robin scheduler. >> > I have pasted the contents of the /boot/grub/menu.lst file. >> > >> > title Xen -- openSUSE 11.0 - 2.6.18.8 manually compiled AGAIN >> > root (hd0,4) >> > kernel /boot/xen.gz >> > module /boot/vmlinuz-2.6.18.8-xen0 >> > root=/dev/disk/by-id/scsi-SATA_Hitachi_HTS5416_SB2D04E4CE7YEE-part5 >> > showopts >> > sched=rrobin vga=0x314 >> > module /boot/initrd-2.6.18-xen0 >> > >> > Incidentally, even if i give sched=sedf, it still runs only on credit >> > scheduler. Please let me know your feedback on this issue. My aim is to >> > study the performance statistics of credit, sedf and new RR scheduler. >> > It >> > would be great if you could give me any pointers to measure scheduler >> > performance or get statistics from the system. >> > >> > Thanks & Regards >> > Ananth >> > >> > ---------- Forwarded message ---------- >> > From: Ananth <cbananth@gmail.com> >> > Date: Mon, Apr 27, 2009 at 6:45 PM >> > Subject: Re: [Xen-devel] Fwd: Error while compiling with new RR >> > scheduler >> > To: George Dunlap <dunlapg@umich.edu> >> > Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> >> > >> > >> > Hello, >> > Thank you so much for pointing it out. How could I miss something so >> > obvious. I am able to compile it now. I will get back to you in case I >> > get >> > into any issues during run time. >> > >> > Thank you. >> > >> > Regards >> > Ananth >> > >> > On Mon, Apr 27, 2009 at 6:29 PM, George Dunlap <dunlapg@umich.edu> >> > wrote: >> >> >> >> The message says it pretty clearly: you return the value of ret, but >> >> there are control paths in the function for which ret.task is not set. >> >> Namely, if list_empty(runq) is true, then you will return an >> >> uninitialized value, which may be anything (garbage on the stack, >> >> NULL, &c). This will most likely cause Xen to crash, as >> >> xen/common/schedule.c assumes that ret.task will be a valid, non-NULL >> >> pointer. >> >> >> >> If you happen to know that runq is never empty, then you don''t need >> >> the if statement. If it may be empty, then you need an else clause to >> >> return the idle vcpu for that processor. >> >> >> >> -George >> >> >> >> 2009/4/24 Ananth <cbananth@gmail.com>: >> >> > Hi, >> >> > I figured out that the error was because of a missing '' ; '' . This >> >> > has >> >> > been fixed now. I have attached the modified code. >> >> > While compiling I am getting the below error message. >> >> > >> >> > cc1: warnings being treated as errors >> >> > sched_rrobin.c: In function ‘rrobin_schedule’: >> >> > sched_rrobin.c:74: error: ‘ret.task’ may be used uninitialized in >> >> > this >> >> > function >> >> > >> >> > Please guide. >> >> > >> >> > Thanks & Regards >> >> > Ananth >> >> > >> >> > >> >> > ---------- Forwarded message ---------- >> >> > From: Ananth <cbananth@gmail.com> >> >> > Date: Fri, Apr 24, 2009 at 7:25 PM >> >> > Subject: Error while compiling with new RR scheduler >> >> > To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> >> >> > >> >> > >> >> > Hi, >> >> > Please find attached the source code of Round Robin scheduler which I >> >> > am >> >> > trying to add to Xen 3.3.1. >> >> > I am facing the following error messages while compiling the same. >> >> > >> >> > sched_rrobin.c:31: error: two or more data types in declaration >> >> > specifiers >> >> > >> >> > sched_rrobin.c: In function ‘rrobin_vcpu_init’: >> >> > >> >> > sched_rrobin.c:34: error: incompatible types in return >> >> > >> >> > sched_rrobin.c:51: error: incompatible types in return >> >> > >> >> > sched_rrobin.c:94: error: initialization from incompatible pointer >> >> > type >> >> > >> >> > I believe the error in line 94 is causing the rest of the error >> >> > messages. I have checked with the structure definition in sched-if.h >> >> > as well >> >> > as the implementation of the same in other schedulers such as SEDF >> >> > and >> >> > Credit. >> >> > >> >> > Request you to kindly provide your feedback regarding the same. >> >> > >> >> > Thanks & Regards >> >> > Ananth >> >> > >> >> > >> >> > _______________________________________________ >> >> > Xen-devel mailing list >> >> > Xen-devel@lists.xensource.com >> >> > http://lists.xensource.com/xen-devel >> >> > >> >> > >> > >> > >> > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ananth
2009-Apr-30 22:00 UTC
Re: [Xen-devel] Re: Issues while running Xen with new RR scheduler
:) Thank you... The system hangs with a blank screen. It does not reboot. When I checked the /var/log/messages file, Apr 30 01:02:01 cbananth exiting on signal 15 This was the message that was logged when I booted into the system. Could you please guide me on how to set up a serial console? Should I connect another system only through a serial port? Can I connect through LAN cable also? I have never done this before. Thank you Warm Regards Ananth On Tue, Apr 28, 2009 at 7:49 PM, George Dunlap <George.Dunlap@eu.citrix.com>wrote:> Welcome to OS programming. :-) When you say, "everything goes blank", > you mean that the machine reboots, or do you mean it just hangs? > > The main thing to do is add printks to your code to figure out where > things start to go bad. > > If your machine is rebooting / crashing, then you''re probably > dereferencing a null pointer or something like that. The best thing > for this is to set up a serial console, enable the sync_console > feature on the xen command line, and log the serial console output. > Then you''ll have the printks as close as possible to the actual crash, > which should help you narrow things down. > > Good luck, > -George > > On Mon, Apr 27, 2009 at 11:39 PM, Ananth <cbananth@gmail.com> wrote: > > Hi, > > Thanks for your suggestion. I was able to change scheduler from credit to > > sedf. "sched" is the correct parameter. > > However when I try to select sched=rrobin, the system gets ready to boot > and > > then everything goes blank. I have attached the round robin scheduler > code > > along with this mail. Could you give me your feedback on whether I have > > missed out something. > > > > Thank you very much once again. > > > > Warm Regards > > Ananth > > > > On Tue, Apr 28, 2009 at 2:11 AM, George Dunlap <dunlapg@umich.edu> > wrote: > >> > >> You need to pass the arguments to xen on the xen command line, not the > >> dom0 kernel command line. So the following line should be: > >> > >> kernel /boot/xen.gz sched=rrobin > >> > >> (I haven''t checked to make sure that "sched" is the right parameter.) > >> > >> -George > >> > >> On Mon, Apr 27, 2009 at 7:39 PM, Ananth <cbananth@gmail.com> wrote: > >> > Hi, > >> > In continuation with my previous post, I am able to login to the > >> > compiled > >> > Xen. But it is continuing to run on credit scheduler even if i modify > >> > the > >> > kernel parameters to run using round robin scheduler. > >> > I have pasted the contents of the /boot/grub/menu.lst file. > >> > > >> > title Xen -- openSUSE 11.0 - 2.6.18.8 manually compiled AGAIN > >> > root (hd0,4) > >> > kernel /boot/xen.gz > >> > module /boot/vmlinuz-2.6.18.8-xen0 > >> > root=/dev/disk/by-id/scsi-SATA_Hitachi_HTS5416_SB2D04E4CE7YEE-part5 > >> > showopts > >> > sched=rrobin vga=0x314 > >> > module /boot/initrd-2.6.18-xen0 > >> > > >> > Incidentally, even if i give sched=sedf, it still runs only on credit > >> > scheduler. Please let me know your feedback on this issue. My aim is > to > >> > study the performance statistics of credit, sedf and new RR scheduler. > >> > It > >> > would be great if you could give me any pointers to measure scheduler > >> > performance or get statistics from the system. > >> > > >> > Thanks & Regards > >> > Ananth > >> > > >> > ---------- Forwarded message ---------- > >> > From: Ananth <cbananth@gmail.com> > >> > Date: Mon, Apr 27, 2009 at 6:45 PM > >> > Subject: Re: [Xen-devel] Fwd: Error while compiling with new RR > >> > scheduler > >> > To: George Dunlap <dunlapg@umich.edu> > >> > Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> > >> > > >> > > >> > Hello, > >> > Thank you so much for pointing it out. How could I miss something so > >> > obvious. I am able to compile it now. I will get back to you in case I > >> > get > >> > into any issues during run time. > >> > > >> > Thank you. > >> > > >> > Regards > >> > Ananth > >> > > >> > On Mon, Apr 27, 2009 at 6:29 PM, George Dunlap <dunlapg@umich.edu> > >> > wrote: > >> >> > >> >> The message says it pretty clearly: you return the value of ret, but > >> >> there are control paths in the function for which ret.task is not > set. > >> >> Namely, if list_empty(runq) is true, then you will return an > >> >> uninitialized value, which may be anything (garbage on the stack, > >> >> NULL, &c). This will most likely cause Xen to crash, as > >> >> xen/common/schedule.c assumes that ret.task will be a valid, non-NULL > >> >> pointer. > >> >> > >> >> If you happen to know that runq is never empty, then you don''t need > >> >> the if statement. If it may be empty, then you need an else clause > to > >> >> return the idle vcpu for that processor. > >> >> > >> >> -George > >> >> > >> >> 2009/4/24 Ananth <cbananth@gmail.com>: > >> >> > Hi, > >> >> > I figured out that the error was because of a missing '' ; '' . This > >> >> > has > >> >> > been fixed now. I have attached the modified code. > >> >> > While compiling I am getting the below error message. > >> >> > > >> >> > cc1: warnings being treated as errors > >> >> > sched_rrobin.c: In function ‘rrobin_schedule’: > >> >> > sched_rrobin.c:74: error: ‘ret.task’ may be used uninitialized in > >> >> > this > >> >> > function > >> >> > > >> >> > Please guide. > >> >> > > >> >> > Thanks & Regards > >> >> > Ananth > >> >> > > >> >> > > >> >> > ---------- Forwarded message ---------- > >> >> > From: Ananth <cbananth@gmail.com> > >> >> > Date: Fri, Apr 24, 2009 at 7:25 PM > >> >> > Subject: Error while compiling with new RR scheduler > >> >> > To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com > > > >> >> > > >> >> > > >> >> > Hi, > >> >> > Please find attached the source code of Round Robin scheduler which > I > >> >> > am > >> >> > trying to add to Xen 3.3.1. > >> >> > I am facing the following error messages while compiling the same. > >> >> > > >> >> > sched_rrobin.c:31: error: two or more data types in declaration > >> >> > specifiers > >> >> > > >> >> > sched_rrobin.c: In function ‘rrobin_vcpu_init’: > >> >> > > >> >> > sched_rrobin.c:34: error: incompatible types in return > >> >> > > >> >> > sched_rrobin.c:51: error: incompatible types in return > >> >> > > >> >> > sched_rrobin.c:94: error: initialization from incompatible pointer > >> >> > type > >> >> > > >> >> > I believe the error in line 94 is causing the rest of the error > >> >> > messages. I have checked with the structure definition in > sched-if.h > >> >> > as well > >> >> > as the implementation of the same in other schedulers such as SEDF > >> >> > and > >> >> > Credit. > >> >> > > >> >> > Request you to kindly provide your feedback regarding the same. > >> >> > > >> >> > Thanks & Regards > >> >> > Ananth > >> >> > > >> >> > > >> >> > _______________________________________________ > >> >> > Xen-devel mailing list > >> >> > Xen-devel@lists.xensource.com > >> >> > http://lists.xensource.com/xen-devel > >> >> > > >> >> > > >> > > >> > > >> > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
George Dunlap
2009-May-01 10:25 UTC
Re: [Xen-devel] Re: Issues while running Xen with new RR scheduler
What''s your Linux setup? If it has any kind of splash screen on boot (like say, Ubuntu), you probably want to turn that off. How that''s done depends on the particular distribution. Can you see a cursor at all? You might try, from your keyboard, pressing "Ctrl-A" three times. If Xen isn''t totally trashed, this will cause Xen to take control of the keyboard, and you can pass it several debug-key commands. Pressing ''h'' will give you a list; ''d'' (IIRC) will give you a dump of the state of the cpus. Using that you can figure out what Xen is doing. As for the serial port: I googled for "serial console", and found this page that has a lot of useful information: http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/ The problem with that page is that it give a little *too much* useful information. The key things you want are: * Use a NULL modem cable to connect two computers. You can get this (or an adapter) at most computer stores. * Probably use 115200 for the speed. * I use minicom on the "monitoring" computer. (Any other suggestions?) + You''ll need to redefine the "command" key from Ctrl-A to Ctrl-B, so that you can use the Ctrl-A to talk to Xen. + Turn on logging in minicom so you can go back and look at things that scrolled off the screen * Your distro is probably already set up to allow Linux to use the serial port; you just need to add the proper command line args to your bootloader. * Allowing root to log in from the serial console is handy, but not necessary to begin with. This is a bit of a hassle to start out with, but if you''re serious about doing Xen development, it''s definitely worth the investment. -George On Thu, Apr 30, 2009 at 11:00 PM, Ananth <cbananth@gmail.com> wrote:> :) Thank you... > The system hangs with a blank screen. It does not reboot. > When I checked the /var/log/messages file, > > Apr 30 01:02:01 cbananth exiting on signal 15 > > This was the message that was logged when I booted into the system. > Could you please guide me on how to set up a serial console? Should I > connect another system only through a serial port? Can I connect through LAN > cable also? I have never done this before. > > Thank you > > Warm Regards > Ananth > > On Tue, Apr 28, 2009 at 7:49 PM, George Dunlap <George.Dunlap@eu.citrix.com> > wrote: >> >> Welcome to OS programming. :-) When you say, "everything goes blank", >> you mean that the machine reboots, or do you mean it just hangs? >> >> The main thing to do is add printks to your code to figure out where >> things start to go bad. >> >> If your machine is rebooting / crashing, then you''re probably >> dereferencing a null pointer or something like that. The best thing >> for this is to set up a serial console, enable the sync_console >> feature on the xen command line, and log the serial console output. >> Then you''ll have the printks as close as possible to the actual crash, >> which should help you narrow things down. >> >> Good luck, >> -George >> >> On Mon, Apr 27, 2009 at 11:39 PM, Ananth <cbananth@gmail.com> wrote: >> > Hi, >> > Thanks for your suggestion. I was able to change scheduler from credit >> > to >> > sedf. "sched" is the correct parameter. >> > However when I try to select sched=rrobin, the system gets ready to boot >> > and >> > then everything goes blank. I have attached the round robin scheduler >> > code >> > along with this mail. Could you give me your feedback on whether I have >> > missed out something. >> > >> > Thank you very much once again. >> > >> > Warm Regards >> > Ananth >> > >> > On Tue, Apr 28, 2009 at 2:11 AM, George Dunlap <dunlapg@umich.edu> >> > wrote: >> >> >> >> You need to pass the arguments to xen on the xen command line, not the >> >> dom0 kernel command line. So the following line should be: >> >> >> >> kernel /boot/xen.gz sched=rrobin >> >> >> >> (I haven''t checked to make sure that "sched" is the right parameter.) >> >> >> >> -George >> >> >> >> On Mon, Apr 27, 2009 at 7:39 PM, Ananth <cbananth@gmail.com> wrote: >> >> > Hi, >> >> > In continuation with my previous post, I am able to login to the >> >> > compiled >> >> > Xen. But it is continuing to run on credit scheduler even if i modify >> >> > the >> >> > kernel parameters to run using round robin scheduler. >> >> > I have pasted the contents of the /boot/grub/menu.lst file. >> >> > >> >> > title Xen -- openSUSE 11.0 - 2.6.18.8 manually compiled AGAIN >> >> > root (hd0,4) >> >> > kernel /boot/xen.gz >> >> > module /boot/vmlinuz-2.6.18.8-xen0 >> >> > root=/dev/disk/by-id/scsi-SATA_Hitachi_HTS5416_SB2D04E4CE7YEE-part5 >> >> > showopts >> >> > sched=rrobin vga=0x314 >> >> > module /boot/initrd-2.6.18-xen0 >> >> > >> >> > Incidentally, even if i give sched=sedf, it still runs only on credit >> >> > scheduler. Please let me know your feedback on this issue. My aim is >> >> > to >> >> > study the performance statistics of credit, sedf and new RR >> >> > scheduler. >> >> > It >> >> > would be great if you could give me any pointers to measure scheduler >> >> > performance or get statistics from the system. >> >> > >> >> > Thanks & Regards >> >> > Ananth >> >> > >> >> > ---------- Forwarded message ---------- >> >> > From: Ananth <cbananth@gmail.com> >> >> > Date: Mon, Apr 27, 2009 at 6:45 PM >> >> > Subject: Re: [Xen-devel] Fwd: Error while compiling with new RR >> >> > scheduler >> >> > To: George Dunlap <dunlapg@umich.edu> >> >> > Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> >> >> > >> >> > >> >> > Hello, >> >> > Thank you so much for pointing it out. How could I miss something so >> >> > obvious. I am able to compile it now. I will get back to you in case >> >> > I >> >> > get >> >> > into any issues during run time. >> >> > >> >> > Thank you. >> >> > >> >> > Regards >> >> > Ananth >> >> > >> >> > On Mon, Apr 27, 2009 at 6:29 PM, George Dunlap <dunlapg@umich.edu> >> >> > wrote: >> >> >> >> >> >> The message says it pretty clearly: you return the value of ret, >> >> >> but >> >> >> there are control paths in the function for which ret.task is not >> >> >> set. >> >> >> Namely, if list_empty(runq) is true, then you will return an >> >> >> uninitialized value, which may be anything (garbage on the stack, >> >> >> NULL, &c). This will most likely cause Xen to crash, as >> >> >> xen/common/schedule.c assumes that ret.task will be a valid, >> >> >> non-NULL >> >> >> pointer. >> >> >> >> >> >> If you happen to know that runq is never empty, then you don''t need >> >> >> the if statement. If it may be empty, then you need an else clause >> >> >> to >> >> >> return the idle vcpu for that processor. >> >> >> >> >> >> -George >> >> >> >> >> >> 2009/4/24 Ananth <cbananth@gmail.com>: >> >> >> > Hi, >> >> >> > I figured out that the error was because of a missing '' ; '' . This >> >> >> > has >> >> >> > been fixed now. I have attached the modified code. >> >> >> > While compiling I am getting the below error message. >> >> >> > >> >> >> > cc1: warnings being treated as errors >> >> >> > sched_rrobin.c: In function ‘rrobin_schedule’: >> >> >> > sched_rrobin.c:74: error: ‘ret.task’ may be used uninitialized in >> >> >> > this >> >> >> > function >> >> >> > >> >> >> > Please guide. >> >> >> > >> >> >> > Thanks & Regards >> >> >> > Ananth >> >> >> > >> >> >> > >> >> >> > ---------- Forwarded message ---------- >> >> >> > From: Ananth <cbananth@gmail.com> >> >> >> > Date: Fri, Apr 24, 2009 at 7:25 PM >> >> >> > Subject: Error while compiling with new RR scheduler >> >> >> > To: "xen-devel@lists.xensource.com" >> >> >> > <xen-devel@lists.xensource.com> >> >> >> > >> >> >> > >> >> >> > Hi, >> >> >> > Please find attached the source code of Round Robin scheduler >> >> >> > which I >> >> >> > am >> >> >> > trying to add to Xen 3.3.1. >> >> >> > I am facing the following error messages while compiling the same. >> >> >> > >> >> >> > sched_rrobin.c:31: error: two or more data types in declaration >> >> >> > specifiers >> >> >> > >> >> >> > sched_rrobin.c: In function ‘rrobin_vcpu_init’: >> >> >> > >> >> >> > sched_rrobin.c:34: error: incompatible types in return >> >> >> > >> >> >> > sched_rrobin.c:51: error: incompatible types in return >> >> >> > >> >> >> > sched_rrobin.c:94: error: initialization from incompatible pointer >> >> >> > type >> >> >> > >> >> >> > I believe the error in line 94 is causing the rest of the error >> >> >> > messages. I have checked with the structure definition in >> >> >> > sched-if.h >> >> >> > as well >> >> >> > as the implementation of the same in other schedulers such as SEDF >> >> >> > and >> >> >> > Credit. >> >> >> > >> >> >> > Request you to kindly provide your feedback regarding the same. >> >> >> > >> >> >> > Thanks & Regards >> >> >> > Ananth >> >> >> > >> >> >> > >> >> >> > _______________________________________________ >> >> >> > Xen-devel mailing list >> >> >> > Xen-devel@lists.xensource.com >> >> >> > http://lists.xensource.com/xen-devel >> >> >> > >> >> >> > >> >> > >> >> > >> >> > >> > >> > >> > _______________________________________________ >> > Xen-devel mailing list >> > Xen-devel@lists.xensource.com >> > http://lists.xensource.com/xen-devel >> > >> > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
George Dunlap
2009-May-01 10:27 UTC
Re: [Xen-devel] Re: Issues while running Xen with new RR scheduler
Also, comb through your code and make sure you understand what is *supposed* to be returned and what *is* returned by all of your functions. Comparing your code with other scheduler code may be helpful. -George On Fri, May 1, 2009 at 11:25 AM, George Dunlap <George.Dunlap@eu.citrix.com> wrote:> What''s your Linux setup? If it has any kind of splash screen on boot > (like say, Ubuntu), you probably want to turn that off. How that''s > done depends on the particular distribution. > > Can you see a cursor at all? You might try, from your keyboard, > pressing "Ctrl-A" three times. If Xen isn''t totally trashed, this > will cause Xen to take control of the keyboard, and you can pass it > several debug-key commands. Pressing ''h'' will give you a list; ''d'' > (IIRC) will give you a dump of the state of the cpus. Using that you > can figure out what Xen is doing. > > As for the serial port: I googled for "serial console", and found this > page that has a lot of useful information: > http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/ > > The problem with that page is that it give a little *too much* useful > information. The key things you want are: > * Use a NULL modem cable to connect two computers. You can get this > (or an adapter) at most computer stores. > * Probably use 115200 for the speed. > * I use minicom on the "monitoring" computer. (Any other suggestions?) > + You''ll need to redefine the "command" key from Ctrl-A to Ctrl-B, so > that you can use the Ctrl-A to talk to Xen. > + Turn on logging in minicom so you can go back and look at things > that scrolled off the screen > * Your distro is probably already set up to allow Linux to use the > serial port; you just need to add the proper command line args to your > bootloader. > * Allowing root to log in from the serial console is handy, but not > necessary to begin with. > > This is a bit of a hassle to start out with, but if you''re serious > about doing Xen development, it''s definitely worth the investment. > > -George > > On Thu, Apr 30, 2009 at 11:00 PM, Ananth <cbananth@gmail.com> wrote: >> :) Thank you... >> The system hangs with a blank screen. It does not reboot. >> When I checked the /var/log/messages file, >> >> Apr 30 01:02:01 cbananth exiting on signal 15 >> >> This was the message that was logged when I booted into the system. >> Could you please guide me on how to set up a serial console? Should I >> connect another system only through a serial port? Can I connect through LAN >> cable also? I have never done this before. >> >> Thank you >> >> Warm Regards >> Ananth >> >> On Tue, Apr 28, 2009 at 7:49 PM, George Dunlap <George.Dunlap@eu.citrix.com> >> wrote: >>> >>> Welcome to OS programming. :-) When you say, "everything goes blank", >>> you mean that the machine reboots, or do you mean it just hangs? >>> >>> The main thing to do is add printks to your code to figure out where >>> things start to go bad. >>> >>> If your machine is rebooting / crashing, then you''re probably >>> dereferencing a null pointer or something like that. The best thing >>> for this is to set up a serial console, enable the sync_console >>> feature on the xen command line, and log the serial console output. >>> Then you''ll have the printks as close as possible to the actual crash, >>> which should help you narrow things down. >>> >>> Good luck, >>> -George >>> >>> On Mon, Apr 27, 2009 at 11:39 PM, Ananth <cbananth@gmail.com> wrote: >>> > Hi, >>> > Thanks for your suggestion. I was able to change scheduler from credit >>> > to >>> > sedf. "sched" is the correct parameter. >>> > However when I try to select sched=rrobin, the system gets ready to boot >>> > and >>> > then everything goes blank. I have attached the round robin scheduler >>> > code >>> > along with this mail. Could you give me your feedback on whether I have >>> > missed out something. >>> > >>> > Thank you very much once again. >>> > >>> > Warm Regards >>> > Ananth >>> > >>> > On Tue, Apr 28, 2009 at 2:11 AM, George Dunlap <dunlapg@umich.edu> >>> > wrote: >>> >> >>> >> You need to pass the arguments to xen on the xen command line, not the >>> >> dom0 kernel command line. So the following line should be: >>> >> >>> >> kernel /boot/xen.gz sched=rrobin >>> >> >>> >> (I haven''t checked to make sure that "sched" is the right parameter.) >>> >> >>> >> -George >>> >> >>> >> On Mon, Apr 27, 2009 at 7:39 PM, Ananth <cbananth@gmail.com> wrote: >>> >> > Hi, >>> >> > In continuation with my previous post, I am able to login to the >>> >> > compiled >>> >> > Xen. But it is continuing to run on credit scheduler even if i modify >>> >> > the >>> >> > kernel parameters to run using round robin scheduler. >>> >> > I have pasted the contents of the /boot/grub/menu.lst file. >>> >> > >>> >> > title Xen -- openSUSE 11.0 - 2.6.18.8 manually compiled AGAIN >>> >> > root (hd0,4) >>> >> > kernel /boot/xen.gz >>> >> > module /boot/vmlinuz-2.6.18.8-xen0 >>> >> > root=/dev/disk/by-id/scsi-SATA_Hitachi_HTS5416_SB2D04E4CE7YEE-part5 >>> >> > showopts >>> >> > sched=rrobin vga=0x314 >>> >> > module /boot/initrd-2.6.18-xen0 >>> >> > >>> >> > Incidentally, even if i give sched=sedf, it still runs only on credit >>> >> > scheduler. Please let me know your feedback on this issue. My aim is >>> >> > to >>> >> > study the performance statistics of credit, sedf and new RR >>> >> > scheduler. >>> >> > It >>> >> > would be great if you could give me any pointers to measure scheduler >>> >> > performance or get statistics from the system. >>> >> > >>> >> > Thanks & Regards >>> >> > Ananth >>> >> > >>> >> > ---------- Forwarded message ---------- >>> >> > From: Ananth <cbananth@gmail.com> >>> >> > Date: Mon, Apr 27, 2009 at 6:45 PM >>> >> > Subject: Re: [Xen-devel] Fwd: Error while compiling with new RR >>> >> > scheduler >>> >> > To: George Dunlap <dunlapg@umich.edu> >>> >> > Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com> >>> >> > >>> >> > >>> >> > Hello, >>> >> > Thank you so much for pointing it out. How could I miss something so >>> >> > obvious. I am able to compile it now. I will get back to you in case >>> >> > I >>> >> > get >>> >> > into any issues during run time. >>> >> > >>> >> > Thank you. >>> >> > >>> >> > Regards >>> >> > Ananth >>> >> > >>> >> > On Mon, Apr 27, 2009 at 6:29 PM, George Dunlap <dunlapg@umich.edu> >>> >> > wrote: >>> >> >> >>> >> >> The message says it pretty clearly: you return the value of ret, >>> >> >> but >>> >> >> there are control paths in the function for which ret.task is not >>> >> >> set. >>> >> >> Namely, if list_empty(runq) is true, then you will return an >>> >> >> uninitialized value, which may be anything (garbage on the stack, >>> >> >> NULL, &c). This will most likely cause Xen to crash, as >>> >> >> xen/common/schedule.c assumes that ret.task will be a valid, >>> >> >> non-NULL >>> >> >> pointer. >>> >> >> >>> >> >> If you happen to know that runq is never empty, then you don''t need >>> >> >> the if statement. If it may be empty, then you need an else clause >>> >> >> to >>> >> >> return the idle vcpu for that processor. >>> >> >> >>> >> >> -George >>> >> >> >>> >> >> 2009/4/24 Ananth <cbananth@gmail.com>: >>> >> >> > Hi, >>> >> >> > I figured out that the error was because of a missing '' ; '' . This >>> >> >> > has >>> >> >> > been fixed now. I have attached the modified code. >>> >> >> > While compiling I am getting the below error message. >>> >> >> > >>> >> >> > cc1: warnings being treated as errors >>> >> >> > sched_rrobin.c: In function ‘rrobin_schedule’: >>> >> >> > sched_rrobin.c:74: error: ‘ret.task’ may be used uninitialized in >>> >> >> > this >>> >> >> > function >>> >> >> > >>> >> >> > Please guide. >>> >> >> > >>> >> >> > Thanks & Regards >>> >> >> > Ananth >>> >> >> > >>> >> >> > >>> >> >> > ---------- Forwarded message ---------- >>> >> >> > From: Ananth <cbananth@gmail.com> >>> >> >> > Date: Fri, Apr 24, 2009 at 7:25 PM >>> >> >> > Subject: Error while compiling with new RR scheduler >>> >> >> > To: "xen-devel@lists.xensource.com" >>> >> >> > <xen-devel@lists.xensource.com> >>> >> >> > >>> >> >> > >>> >> >> > Hi, >>> >> >> > Please find attached the source code of Round Robin scheduler >>> >> >> > which I >>> >> >> > am >>> >> >> > trying to add to Xen 3.3.1. >>> >> >> > I am facing the following error messages while compiling the same. >>> >> >> > >>> >> >> > sched_rrobin.c:31: error: two or more data types in declaration >>> >> >> > specifiers >>> >> >> > >>> >> >> > sched_rrobin.c: In function ‘rrobin_vcpu_init’: >>> >> >> > >>> >> >> > sched_rrobin.c:34: error: incompatible types in return >>> >> >> > >>> >> >> > sched_rrobin.c:51: error: incompatible types in return >>> >> >> > >>> >> >> > sched_rrobin.c:94: error: initialization from incompatible pointer >>> >> >> > type >>> >> >> > >>> >> >> > I believe the error in line 94 is causing the rest of the error >>> >> >> > messages. I have checked with the structure definition in >>> >> >> > sched-if.h >>> >> >> > as well >>> >> >> > as the implementation of the same in other schedulers such as SEDF >>> >> >> > and >>> >> >> > Credit. >>> >> >> > >>> >> >> > Request you to kindly provide your feedback regarding the same. >>> >> >> > >>> >> >> > Thanks & Regards >>> >> >> > Ananth >>> >> >> > >>> >> >> > >>> >> >> > _______________________________________________ >>> >> >> > Xen-devel mailing list >>> >> >> > Xen-devel@lists.xensource.com >>> >> >> > http://lists.xensource.com/xen-devel >>> >> >> > >>> >> >> > >>> >> > >>> >> > >>> >> > >>> > >>> > >>> > _______________________________________________ >>> > Xen-devel mailing list >>> > Xen-devel@lists.xensource.com >>> > http://lists.xensource.com/xen-devel >>> > >>> > >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Jackson
2009-May-01 14:48 UTC
Re: [Xen-devel] Re: Issues while running Xen with new RR scheduler
George Dunlap writes ("Re: [Xen-devel] Re: Issues while running Xen with
new RR scheduler"):> * I use minicom on the "monitoring" computer. (Any other
suggestions?)
picocom is a lot less annoying than minicom.
> + Turn on logging in minicom so you can go back and look at things
> that scrolled off the screen
It doesn''t have its own terminal emulator so stuff just scrolls into
your xterm scrollback which is far more sensible.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
George Dunlap
2009-May-01 14:53 UTC
Re: [Xen-devel] Re: Issues while running Xen with new RR scheduler
Ian Jackson wrote:> It doesn''t have its own terminal emulator so stuff just scrolls into > your xterm scrollback which is far more sensible. >xterm scrollback: * Is much more limited in scope, if you want to see what happened 5000 lines ago * Can''t be searched through / grepped easily * May disappear if something in the boot path clears the screen. The last one is the most annoying to me. But if it could be used with script -f, I''d probably switch to it from minicom. (We actually have serial console devices here at the office, so I don''t need minicom.) -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Jackson
2009-May-01 14:59 UTC
Re: [Xen-devel] Re: Issues while running Xen with new RR scheduler
George Dunlap writes ("Re: [Xen-devel] Re: Issues while running Xen with
new RR scheduler"):> xterm scrollback:
> * Is much more limited in scope, if you want to see what happened 5000
> lines ago
Of course this is configurable, and ...
> * Can''t be searched through / grepped easily
> * May disappear if something in the boot path clears the screen.
... xterm also has the ability to log to a file, available from the
mouse menus.
> The last one is the most annoying to me. But if it could be used with
> script -f, I''d probably switch to it from minicom. (We actually
have
> serial console devices here at the office, so I don''t need
minicom.)
I''m sure it would work with script too.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
George Dunlap
2009-May-01 15:03 UTC
Re: [Xen-devel] Re: Issues while running Xen with new RR scheduler
Ian Jackson wrote:> ... xterm also has the ability to log to a file, available from the > mouse menus. >Hmm, or with the -l option apparently. But you can''t chose the name of the log file, only the directory where it gets created, which could be annoying. Well, I learned a trick or two today. :-) -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ananth
2009-May-04 09:59 UTC
Re: [Xen-devel] Re: Issues while running Xen with new RR scheduler
Hello, Thank you so much for the suggestions. I suddenly got back my confidence that there are so many people to help me out. :) I will try setting it up and get back to you in case I face any issues. Thanks again. Warm Regards Ananth On Fri, May 1, 2009 at 8:33 PM, George Dunlap <george.dunlap@eu.citrix.com>wrote:> Ian Jackson wrote: > >> ... xterm also has the ability to log to a file, available from the >> mouse menus. >> >> > Hmm, or with the -l option apparently. But you can''t chose the name of the > log file, only the directory where it gets created, which could be annoying. > > Well, I learned a trick or two today. :-) > -George >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ananth
2009-May-08 20:55 UTC
Re: [Xen-devel] Re: Issues while running Xen with new RR scheduler
Hi, I am not able to even view the cursor when system boots. I pressed Ctrl+A and tried giving other commands. But there was no response. I dont think setting up a serial console will also help in this case. In my code (attached) I have written methods to initialize vcpu and destroy vcpu. I have not initialized domains as it is compared to the other schedulers. Could that be the problem? Please guide me in this regard. Thank you. Regards Ananth On Mon, May 4, 2009 at 3:29 PM, Ananth <cbananth@gmail.com> wrote:> Hello, > Thank you so much for the suggestions. I suddenly got back my confidence > that there are so many people to help me out. :) > I will try setting it up and get back to you in case I face any issues. > > Thanks again. > > Warm Regards > Ananth > > > On Fri, May 1, 2009 at 8:33 PM, George Dunlap <george.dunlap@eu.citrix.com > > wrote: > >> Ian Jackson wrote: >> >>> ... xterm also has the ability to log to a file, available from the >>> mouse menus. >>> >>> >> Hmm, or with the -l option apparently. But you can''t chose the name of >> the log file, only the directory where it gets created, which could be >> annoying. >> >> Well, I learned a trick or two today. :-) >> -George >> > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ananth
2009-May-08 21:41 UTC
Re: [Xen-devel] Re: Issues while running Xen with new RR scheduler
Hello, Sorry, I had attached the wrong file. Please find the correct round robin code as attached. Thanks & Regards Ananth On Sat, May 9, 2009 at 2:25 AM, Ananth <cbananth@gmail.com> wrote:> Hi, > I am not able to even view the cursor when system boots. I pressed Ctrl+A > and tried giving other commands. But there was no response. I dont think > setting up a serial console will also help in this case. > In my code (attached) I have written methods to initialize vcpu and destroy > vcpu. I have not initialized domains as it is compared to the other > schedulers. Could that be the problem? > Please guide me in this regard. > > Thank you. > > Regards > Ananth > > > On Mon, May 4, 2009 at 3:29 PM, Ananth <cbananth@gmail.com> wrote: > >> Hello, >> Thank you so much for the suggestions. I suddenly got back my confidence >> that there are so many people to help me out. :) >> I will try setting it up and get back to you in case I face any issues. >> >> Thanks again. >> >> Warm Regards >> Ananth >> >> >> On Fri, May 1, 2009 at 8:33 PM, George Dunlap < >> george.dunlap@eu.citrix.com> wrote: >> >>> Ian Jackson wrote: >>> >>>> ... xterm also has the ability to log to a file, available from the >>>> mouse menus. >>>> >>>> >>> Hmm, or with the -l option apparently. But you can''t chose the name of >>> the log file, only the directory where it gets created, which could be >>> annoying. >>> >>> Well, I learned a trick or two today. :-) >>> -George >>> >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel