Xen on Arndale with SSD

Xen on Arndale with SSD

[Sander Bogaert]

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

Hi,

I was wondering if anyone managed to use an ssd in this setup yet? I
gave it a try:

- Julien's xen / dom0 / domU branches
- Comay Venus 3S SSD drive
- Changed the dts compiled in Xen to have root=/dev/sda1 for dom0
kernel parameter.
- The bootloader is on the SD card, the kernel and xen are loaded
using PXE, the dom0 rootfs is on the ssd disk.

Xen hangs on (complete log attached):
(XEN) 3... 2... 1...
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen)
(XEN) Freed 204kB init memory.

I was wondering if it would be possible at all to do this? Since the
lack of SMMU support atm and the 'hack' used on Arndale.

Thanks
Sander

[-- Attachment #2: log.txt --]
[-- Type: text/plain, Size: 5416 bytes --]

U-Boot 2012.10-rc1-g0faa5ad (Apr 02 2013 - 13:58:23) for ARNDALE5250

CPU:    Exynos5250@1000MHz

Board:  for ARNDALE5250
I2C:   ready
DRAM:  2 GiB
WARNING: Caches not enabled

Checking Boot Mode ... SDMMC
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1, EXYNOS DWMMC: 2
SATA: AHCI 0001.0300 32 slots 1 ports ? Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part 
SATA Device Info:
S/N: CHBC0N83X6JOHTVP2R
Product model number: Comay Venus 3S
Firmware version: 2.54
Capacity: 234441648 sectors
In:    serial
Out:   serial
Err:   serial
(Re)start USB...
USB:   Register 1313 NbrPorts 3
USB EHCI 1.00
scanning bus for devices... 4 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
       scanning bus for ethernet devices... 1 Ethernet Device(s) found
Hit any key to stop autoboot:  0 
Waiting for Ethernet connection... done.
Using asx0 device
TFTP from server 10.0.0.2; our IP address is 10.0.0.1
Filename 'pxelinux.cfg/linux-zImage'.
Load address: 0x60000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #########################
done
Bytes transferred = 1788192 (1b4920 hex)
Waiting for Ethernet connection... done.
Using asx0 device
TFTP from server 10.0.0.2; our IP address is 10.0.0.1
Filename 'pxelinux.cfg/xen-uImage'.
Load address: 0x50000000
Loading: #################################################################
         #################################################################
         ########################################
done
Bytes transferred = 866176 (d3780 hex)
## Booting kernel from Legacy Image at 50000000 ...
   Image Name:   
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    866112 Bytes = 845.8 KiB
   Load Address: 80200000
   Entry Point:  80200000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Startinllllllllllllllll- UART enabled -
- CPU 00000000 booting -
- Started in Hyp mode -
- Zero BSS -
- Setting up control registers -
- Turning on paging -
- Ready -
RAM: 0000000040000000 - 00000000bfffffff

MODULE[1]: 0000000060000000 - 0000000060400000 
Placing Xen at 0x00000000bfe00000-0x00000000c0000000
Xen heap: 262144 pages  Dom heap: 262144 pages
 __  __            _  _    _____                    _        _     _      
 \ \/ /___ _ __   | || |  |___ /    _   _ _ __  ___| |_ __ _| |__ | | ___ 
  \  // _ \ '_ \  | || |_   |_ \ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | | |__   _| ___) |__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_|    |_|(_)____/    \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                          
(XEN) Xen version 4.3-unstable (dzan@) (arm-linux-gnueabi-gcc (Debian 4.7.2-4) 4.7.2) debug=y Fri Apr 19 10:21:27 CEST 2013
(XEN) Latest ChangeSet: unavailable
(XEN) Console output is synchronous.
(XEN) Processor: "ARM Limited", variant: 0x0, part 0xc0f, rev 0x4
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00001031:00011011
(XEN)     Instruction Sets: AArch32 Thumb Thumb-2 ThumbEE Jazelle
(XEN)     Extensions: GenericTimer Security
(XEN)   Debug Features: 02010555
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 10201105 20000000 01240000 02102211
(XEN)  ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000
(XEN) Using generic timer at 24000 KHz
(XEN) GIC initialization:
(XEN)         gic_dist_addr=0000000010481000
(XEN)         gic_cpu_addr=0000000010482000
(XEN)         gic_hyp_addr=0000000010484000
(XEN)         gic_vcpu_addr=0000000010486000
(XEN) GIC: 128 lines, 2 cpus, secure (IID 0200043b).
(XEN) Waiting for 1 other CPUs to be ready
- CPU 00000001 booting -
- Started in Secure state -
- Entering Hyp mode -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 16 KiB.
(XEN) CPU 1 booted.
(XEN) Brought up 2 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Populate P2M 0x40000000->0x50000000(1:1 mapping for dom0)
(XEN) Device-tree contains "xen,xen" node. Ignoring.
(XEN) Loading kernel from boot module 1
(XEN) try zimage at 0x60000000, 0x400000
(XEN) Map CS2 MMIO regions 1:1 in the P2M 0x18000000->0x1bffffff
(XEN) Map CS3 MMIO regions 1:1 in the P2M 0x1c000000->0x1fffffff
(XEN) map chip id to 0x10000000
(XEN) map more
(XEN) Routing peripheral interrupts to guest
(XEN) Loading zImage from 0000000060000000 to 0000000040008000-00000000401bc920
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) **********************************************
(XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) ******* This option is intended to aid debugging of Xen by ensuring
(XEN) ******* that all output is synchronously delivered on the serial line.
(XEN) ******* However it can introduce SIGNIFICANT latencies and affect
(XEN) ******* timekeeping. It is NOT recommended for production use!
(XEN) **********************************************
(XEN) 3... 2... 1... 
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 204kB init memory.

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Xen on Arndale with SSD

[Julien Grall]

On 04/19/2013 10:11 AM, Sander Bogaert wrote:

> Hi,
> 
> I was wondering if anyone managed to use an ssd in this setup yet? I
> gave it a try:
> 
> - Julien's xen / dom0 / domU branches
> - Comay Venus 3S SSD drive
> - Changed the dts compiled in Xen to have root=/dev/sda1 for dom0
> kernel parameter.
> - The bootloader is on the SD card, the kernel and xen are loaded
> using PXE, the dom0 rootfs is on the ssd disk.
> 
> Xen hangs on (complete log attached):
> (XEN) 3... 2... 1...
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen)
> (XEN) Freed 204kB init memory.


I think linux hangs before hvc console is initialized. Could you try
to apply this hackish patch and resent the log? This patch will directly
call the console hypercall instead of buffering messages.

diff --git a/kernel/printk.c b/kernel/printk.c
index abbdd9e..6975215 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -1652,6 +1652,8 @@ asmlinkage int printk_emit(int facility, int level,
 }
 EXPORT_SYMBOL(printk_emit);

+void xen_raw_console_write(const char *buf);
+
 /**
  * printk - print a kernel message
  * @fmt: format string
@@ -1677,6 +1679,7 @@ asmlinkage int printk(const char *fmt, ...)
 {
        va_list args;
        int r;
+       static char buf[512];

 #ifdef CONFIG_KGDB_KDB
        if (unlikely(kdb_trap_printk)) {
@@ -1687,9 +1690,12 @@ asmlinkage int printk(const char *fmt, ...)
        }
 #endif
        va_start(args, fmt);
-       r = vprintk_emit(0, -1, NULL, 0, fmt, args);
+//     r = vprintk_emit(0, -1, NULL, 0, fmt, args);
+       r = vsnprintf(buf, sizeof(buf), fmt, args);
        va_end(args);

+       xen_raw_console_write(buf);
+
        return r;
 }
 EXPORT_SYMBOL(printk);

Re: Xen on Arndale with SSD

[David Park]

[-- Attachment #1.1: Type: text/plain, Size: 2399 bytes --]

2013/4/22 Julien Grall <julien.grall@linaro.org>
>
> On 04/19/2013 10:11 AM, Sander Bogaert wrote:
>
> > Hi,
> >
> > I was wondering if anyone managed to use an ssd in this setup yet? I
> > gave it a try:
> >
> > - Julien's xen / dom0 / domU branches
> > - Comay Venus 3S SSD drive
> > - Changed the dts compiled in Xen to have root=/dev/sda1 for dom0
> > kernel parameter.
> > - The bootloader is on the SD card, the kernel and xen are loaded
> > using PXE, the dom0 rootfs is on the ssd disk.
> >
> > Xen hangs on (complete log attached):
> > (XEN) 3... 2... 1...
> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> > input to Xen)
> > (XEN) Freed 204kB init memory.
>
>
> I think linux hangs before hvc console is initialized. Could you try
> to apply this hackish patch and resent the log? This patch will directly
> call the console hypercall instead of buffering messages.
>
> diff --git a/kernel/printk.c b/kernel/printk.c
> index abbdd9e..6975215 100644
> --- a/kernel/printk.c
> +++ b/kernel/printk.c
> @@ -1652,6 +1652,8 @@ asmlinkage int printk_emit(int facility, int level,
>  }
>  EXPORT_SYMBOL(printk_emit);
>
> +void xen_raw_console_write(const char *buf);
> +
>  /**
>   * printk - print a kernel message
>   * @fmt: format string
> @@ -1677,6 +1679,7 @@ asmlinkage int printk(const char *fmt, ...)
>  {
>         va_list args;
>         int r;
> +       static char buf[512];
>
>  #ifdef CONFIG_KGDB_KDB
>         if (unlikely(kdb_trap_printk)) {
> @@ -1687,9 +1690,12 @@ asmlinkage int printk(const char *fmt, ...)
>         }
>  #endif
>         va_start(args, fmt);
> -       r = vprintk_emit(0, -1, NULL, 0, fmt, args);
> +//     r = vprintk_emit(0, -1, NULL, 0, fmt, args);
> +       r = vsnprintf(buf, sizeof(buf), fmt, args);
>         va_end(args);
>
> +       xen_raw_console_write(buf);
> +
>         return r;
>  }
>  EXPORT_SYMBOL(printk);
>
> _______________________________________________
> Xen-devel > mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
>



 Hello,

 I hope following would be helpful to you.

 In my case, I'm currently using Runcore and Comay Venus SSD  in dom0
 I had a same problem when I use the Comay SSD before. (not on Runcore)
 But after updating the u-boot with latest one, I can use this well.
   (u-boot-linaro-stable, v2013.04-rc1)

 I recommend you to update the u-boot.

 Thanks,
 David

[-- Attachment #1.2: Type: text/html, Size: 3123 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Xen on Arndale with SSD

[Sander Bogaert]

Hi,

I've only been able to test this today. I can report updating uboot
does the trick.

Thanks!
Sander

On 24 April 2013 05:00, David Park <beastworld@gmail.com> wrote:
>
> 2013/4/22 Julien Grall <julien.grall@linaro.org>
>>
>> On 04/19/2013 10:11 AM, Sander Bogaert wrote:
>>
>> > Hi,
>> >
>> > I was wondering if anyone managed to use an ssd in this setup yet? I
>> > gave it a try:
>> >
>> > - Julien's xen / dom0 / domU branches
>> > - Comay Venus 3S SSD drive
>> > - Changed the dts compiled in Xen to have root=/dev/sda1 for dom0
>> > kernel parameter.
>> > - The bootloader is on the SD card, the kernel and xen are loaded
>> > using PXE, the dom0 rootfs is on the ssd disk.
>> >
>> > Xen hangs on (complete log attached):
>> > (XEN) 3... 2... 1...
>> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
>> > input to Xen)
>> > (XEN) Freed 204kB init memory.
>>
>>
>> I think linux hangs before hvc console is initialized. Could you try
>> to apply this hackish patch and resent the log? This patch will directly
>> call the console hypercall instead of buffering messages.
>>
>> diff --git a/kernel/printk.c b/kernel/printk.c
>> index abbdd9e..6975215 100644
>> --- a/kernel/printk.c
>> +++ b/kernel/printk.c
>> @@ -1652,6 +1652,8 @@ asmlinkage int printk_emit(int facility, int level,
>>  }
>>  EXPORT_SYMBOL(printk_emit);
>>
>> +void xen_raw_console_write(const char *buf);
>> +
>>  /**
>>   * printk - print a kernel message
>>   * @fmt: format string
>> @@ -1677,6 +1679,7 @@ asmlinkage int printk(const char *fmt, ...)
>>  {
>>         va_list args;
>>         int r;
>> +       static char buf[512];
>>
>>  #ifdef CONFIG_KGDB_KDB
>>         if (unlikely(kdb_trap_printk)) {
>> @@ -1687,9 +1690,12 @@ asmlinkage int printk(const char *fmt, ...)
>>         }
>>  #endif
>>         va_start(args, fmt);
>> -       r = vprintk_emit(0, -1, NULL, 0, fmt, args);
>> +//     r = vprintk_emit(0, -1, NULL, 0, fmt, args);
>> +       r = vsnprintf(buf, sizeof(buf), fmt, args);
>>         va_end(args);
>>
>> +       xen_raw_console_write(buf);
>> +
>>         return r;
>>  }
>>  EXPORT_SYMBOL(printk);
>>
>> _______________________________________________
>> Xen-devel > mailing list
>> > Xen-devel@lists.xen.org
>> > http://lists.xen.org/xen-devel
>>
>
>
>
>  Hello,
>
>  I hope following would be helpful to you.
>
>  In my case, I'm currently using Runcore and Comay Venus SSD  in dom0
>  I had a same problem when I use the Comay SSD before. (not on Runcore)
>  But after updating the u-boot with latest one, I can use this well.
>    (u-boot-linaro-stable, v2013.04-rc1)
>
>  I recommend you to update the u-boot.
>
>  Thanks,
>  David