From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: simple scheduler Date: Wed, 17 Feb 2010 11:43:38 +0000 Message-ID: References: <14f366f91002150519y1a27774h6f5d6628734f8849@mail.gmail.com> <20100215185412.GX2861@reaktio.net> <14f366f91002161018h60504c10g9224480e24872c1c@mail.gmail.com> <20100216182909.GG2861@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100216182909.GG2861@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: "michele.paolino" , Xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Did you add a printk to your schedule() function to see if it's getting cal= led? schedule() is called from within the SCHEDULE_SOFTIRQ. Look at xen/common/sched_credit.c. When is SCHEDULE_SOFTIRQ getting raised? Are you doing that in your scheduler? -George On Tue, Feb 16, 2010 at 6:29 PM, Pasi K=E4rkk=E4inen wrote: > On Tue, Feb 16, 2010 at 07:18:00PM +0100, michele.paolino wrote: >> =A0 =A0Thanks for the istructions, >> =A0 =A0I have read that thread but is not useful for me. I have compiled= and >> =A0 =A0installed the round robin scheduler of that thread. Both schedule= rs have >> =A0 =A0the same behavior. Following your advice I have set up a serial c= onsole. I >> =A0 =A0have attached serial console's log along with this mail. As I sup= posed, >> =A0 =A0dom0 doesn't start. >> > > Please paste your grub.conf. > > It could be that your dom0 kernel is not configured to use the serial con= sole. > > -- Pasi > >> =A0 =A0Michele >> >> =A0 =A0On Mon, Feb 15, 2010 at 7:54 PM, Pasi K=E4rkk=E4inen <[1]pasik@ik= i.fi> wrote: >> >> =A0 =A0 =A0On Mon, Feb 15, 2010 at 01:59:06PM +0000, George Dunlap wrote= : >> =A0 =A0 =A0> Do you have a serial console set up? >> =A0 =A0 =A0> >> >> =A0 =A0 =A0If not, instructions here: >> =A0 =A0 =A0[2]http://wiki.xensource.com/xenwiki/XenSerialConsole >> =A0 =A0 =A0-- Pasi >> =A0 =A0 =A0> You may want to skim this thread: >> =A0 =A0 =A0> >> =A0 =A0 =A0 [3]http://lists.xensource.com/archives/html/xen-devel/2009-0= 4/msg01086.html >> =A0 =A0 =A0> to see if any of the advice given there is useful. >> =A0 =A0 =A0> >> =A0 =A0 =A0> =A0-George >> =A0 =A0 =A0> >> =A0 =A0 =A0> On Mon, Feb 15, 2010 at 1:19 PM, michele.paolino >> =A0 =A0 =A0> <[4]michele.paolino@studio.unibo.it> wrote: >> =A0 =A0 =A0> > Hi! I'm writing a simple scheduler to study the xen sched= uler >> =A0 =A0 =A0interfaces. >> =A0 =A0 =A0> > I am able to compile and install it. After reboot when I = try to >> =A0 =A0 =A0select >> =A0 =A0 =A0> > sched=3Dsimple, the system gets ready to boot and then ev= erything goes >> =A0 =A0 =A0blank. >> =A0 =A0 =A0> > I think that dom0 don't start. I can't be able to solve t= his >> =A0 =A0 =A0problem, can >> =A0 =A0 =A0> > anybody help me? >> =A0 =A0 =A0> > I have attached my simple scheduler code along with this = mail. >> =A0 =A0 =A0> > >> =A0 =A0 =A0> > Thanks, >> =A0 =A0 =A0> > Michele >> =A0 =A0 =A0> > >> =A0 =A0 =A0> > _______________________________________________ >> =A0 =A0 =A0> > Xen-devel mailing list >> =A0 =A0 =A0> > [5]Xen-devel@lists.xensource.com >> =A0 =A0 =A0> > [6]http://lists.xensource.com/xen-devel >> =A0 =A0 =A0> > >> =A0 =A0 =A0> > >> =A0 =A0 =A0> >> =A0 =A0 =A0> _______________________________________________ >> =A0 =A0 =A0> Xen-devel mailing list >> =A0 =A0 =A0> [7]Xen-devel@lists.xensource.com >> =A0 =A0 =A0> [8]http://lists.xensource.com/xen-devel >> >> References >> >> =A0 =A0Visible links >> =A0 =A01. mailto:pasik@iki.fi >> =A0 =A02. http://wiki.xensource.com/xenwiki/XenSerialConsole >> =A0 =A03. http://lists.xensource.com/archives/html/xen-devel/2009-04/msg= 01086.html >> =A0 =A04. mailto:michele.paolino@studio.unibo.it >> =A0 =A05. mailto:Xen-devel@lists.xensource.com >> =A0 =A06. http://lists.xensource.com/xen-devel >> =A0 =A07. mailto:Xen-devel@lists.xensource.com >> =A0 =A08. http://lists.xensource.com/xen-devel > >> =A0__ =A0__ =A0 =A0 =A0 =A0 =A0 =A0_____ _ =A0_ =A0 =A0____ >> =A0\ \/ /___ _ __ =A0 |___ /| || | =A0|___ \ >> =A0 \ =A0// _ \ '_ \ =A0 =A0|_ \| || |_ =A0 __) | >> =A0 / =A0\ =A0__/ | | | =A0___) |__ =A0 _| / __/ >> =A0/_/\_\___|_| |_| |____(_) |_|(_)_____| >> >> (XEN) Xen version 3.4.2 (root@) (gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu= 4)) Mon Feb 15 15:12:25 CET 2010 >> (XEN) Latest ChangeSet: unavailable >> (XEN) Command line: dom0_mem=3D262144 sched=3Dsimple loglvl=3Dall guest_= loglvl=3Dall com1=3D115200,8n1 console=3Dcom1 >> (XEN) Video information: >> (XEN) =A0VGA is text mode 80x25, font 8x16 >> (XEN) Disc information: >> (XEN) =A0Found 1 MBR signatures >> (XEN) =A0Found 1 EDD information structures >> (XEN) Xen-e820 RAM map: >> (XEN) =A00000000000000000 - 000000000009f000 (usable) >> (XEN) =A0000000000009f000 - 00000000000a0000 (reserved) >> (XEN) =A000000000000e8000 - 0000000000100000 (reserved) >> (XEN) =A00000000000100000 - 000000003fff0000 (usable) >> (XEN) =A0000000003fff0000 - 0000000040000000 (ACPI data) >> (XEN) =A000000000fffbc000 - 0000000100000000 (reserved) >> (XEN) System RAM: 1023MB (1048124kB) >> (XEN) ACPI: RSDP 000FBDB0, 0014 (r0 QEMU =A0) >> (XEN) ACPI: RSDT 3FFF0000, 0034 (r1 QEMU =A0 QEMURSDT =A0 =A0 =A0 =A01 Q= EMU =A0 =A0 =A0 =A01) >> (XEN) ACPI: FACP 3FFF01B4, 0074 (r1 QEMU =A0 QEMUFACP =A0 =A0 =A0 =A01 Q= EMU =A0 =A0 =A0 =A01) >> (XEN) ACPI: DSDT 3FFF0280, 1DD4 (r1 =A0 BXPC =A0 BXDSDT =A0 =A0 =A0 =A01= INTL 20090521) >> (XEN) ACPI: FACS 3FFF0240, 0040 >> (XEN) ACPI: SSDT 3FFF2054, 09E3 (r1 =A0 BXPC =A0 BXSSDT =A0 =A0 =A0 =A01= INTL 20090521) >> (XEN) ACPI: APIC 3FFF2A38, 00EA (r1 QEMU =A0 QEMUAPIC =A0 =A0 =A0 =A01 Q= EMU =A0 =A0 =A0 =A01) >> (XEN) ACPI: HPET 3FFF2B90, 0038 (r1 QEMU =A0 QEMUHPET =A0 =A0 =A0 =A01 Q= EMU =A0 =A0 =A0 =A01) >> (XEN) NUMA turned off >> (XEN) Faking a node at 0000000000000000-000000003fff0000 >> (XEN) Xen heap: 9MB (9808kB) >> (XEN) Domain heap initialised >> (XEN) found SMP MP-table at 000fbc90 >> (XEN) DMI 2.4 present. >> (XEN) Using APIC driver default >> (XEN) ACPI: PM-Timer IO Port: 0xb008 >> (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[b004,0], pm1x_evt[b000,0] >> (XEN) ACPI: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0wakeup_vec[3fff024c], vec= _size[20] >> (XEN) ACPI: Local APIC address 0xfee00000 >> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) >> (XEN) Processor #0 6:2 APIC version 20 >> (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x05] lapic_id[0x05] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x0c] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0d] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0e] disabled) >> (XEN) ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0f] disabled) >> (XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) >> (XEN) IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23 >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level) >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level) >> (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level) >> (XEN) ACPI: IRQ0 used by override. >> (XEN) ACPI: IRQ2 used by override. >> (XEN) ACPI: IRQ5 used by override. >> (XEN) ACPI: IRQ9 used by override. >> (XEN) ACPI: IRQ10 used by override. >> (XEN) ACPI: IRQ11 used by override. >> (XEN) Enabling APIC mode: =A0Flat. =A0Using 1 I/O APICs >> (XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000 >> (XEN) Using ACPI (MADT) for SMP configuration information >> (XEN) Using scheduler: Very simple Scheduler (simple) >> (XEN) >> (XEN) >> (XEN) add VCPU 0 >> (XEN) >> (XEN) Initializing CPU#0 >> (XEN) Detected 2533.353 MHz processor. >> (XEN) CPU: L1 I cache: 32K, L1 D cache: 32K >> (XEN) CPU: L2 cache: 2048K >> (XEN) Intel machine check reporting enabled on CPU#0. >> (XEN) CMCI: CPU0 has no CMCI support >> (XEN) CPU0: Intel QEMU Virtual CPU version 0.11.0 stepping 03 >> (XEN) Total of 1 processors activated. >> (XEN) ENABLING IO-APIC IRQs >> (XEN) =A0-> Using new ACK method >> (XEN) ..TIMER: vector=3D0xF0 apic1=3D0 pin1=3D2 apic2=3D-1 pin2=3D-1 >> (XEN) BAD HPET revision id. >> (XEN) Platform timer is 3.579MHz ACPI PM Timer >> (XEN) Brought up 1 CPUs >> (XEN) I/O virtualisation disabled >> (XEN) CPUIDLE: disabled due to no HPET. Force enable with 'cpuidle'. >> (XEN) ACPI sleep modes: S3 >> (XEN) mcheck_poll: Machine check polling timer started. >> (XEN) *** LOADING DOMAIN 0 *** >> (XEN) =A0Xen =A0kernel: 32-bit, PAE, lsb >> (XEN) =A0Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc048d33c >> (XEN) PHYSICAL MEMORY ARRANGEMENT: >> (XEN) =A0Dom0 alloc.: =A0 000000003c000000->000000003e000000 (57344 page= s to be allocated) >> (XEN) VIRTUAL MEMORY ARRANGEMENT: >> (XEN) =A0Loaded kernel: c0100000->c048d33c >> (XEN) =A0Init. ramdisk: c048e000->c1380c00 >> (XEN) =A0Phys-Mach map: c1381000->c13c1000 >> (XEN) =A0Start info: =A0 =A0c13c1000->c13c147c >> (XEN) =A0Page tables: =A0 c13c2000->c13d3000 >> (XEN) =A0Boot stack: =A0 =A0c13d3000->c13d4000 >> (XEN) =A0TOTAL: =A0 =A0 =A0 =A0 c0000000->c1800000 >> (XEN) =A0ENTRY ADDRESS: c0100000 >> (XEN) Dom0 has maximum 1 VCPUs >> (XEN) Scrubbing Free RAM: .......done. >> (XEN) Xen trace buffers: disabled >> (XEN) Std. Loglevel: All >> (XEN) Guest Loglevel: All >> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch inpu= t to Xen) >> (XEN) Freed 116kB init memory. > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >