[Xen-devel] Possible bug on ARM with irq passthrough

2017-07-04 Thread Ivan Pavić2
Hello, I'm testing IRQ latency on exynos5422. I'm using Xen 4.10-unstable. I used device passthrough for SPI irq 64. For guest domain I used  FreeRTOS. When I use credit scheduler after destruction of domain, IRQ is released. I changed scheduler to credit2 and rtds at boot time and IRQ wasn't r

[Xen-devel] Odgovor: Basic bare metal ARM domain interface

2016-05-30 Thread Ivan Pavić2
Hello, >> I used FreeRTOS code for console output. It is based on Mini OS code. There >> are two problems as I've >determined >> with debugging. First is that vsnprintf blocks for some reason in print >> function so i commented it out. After the >snprintf blocks... >> hypercall function block

Re: [Xen-devel] Basic bare metal ARM domain interface

2016-05-28 Thread Ivan Pavić2
Hello, > I used FreeRTOS code for console output. It is based on Mini OS code. There > are two problems as I've determined > with debugging. First is that vsnprintf blocks for some reason in print > function so i commented it out. After the snprintf blocks... > hypercall function blocked as

Re: [Xen-devel] Basic bare metal ARM domain interface

2016-05-27 Thread Ivan Pavić2
Hello, Jullien, thanks for docs and references. I used FreeRTOS code for console output. It is based on Mini OS code. There are two problems as I've determined with debugging. First is that vsnprintf blocks for some reason in print function so i commented it out. After the hypercall function

[Xen-devel] Basic bare metal ARM domain interface

2016-05-25 Thread Ivan Pavić2
Hello, I'm working on bare metal application for ARM Cortex A7/15 on Odroid XU3 platform. I'm using Xen 4.6. After successfully creating bare metal example(by successful I mean I've stuck processor in while loop in main function), I probably should initialize memory management unit and similiar

[Xen-devel] ARM bare metal application test

2016-05-09 Thread Ivan Pavić2
Hello, > I don't think toolstack tries to load kernel to that guest physical > address -- reading from Ivan's log it suggests toolstack loaded the > kernel to 0x40008000. > That (0x8000800) is the address set in PC, right? I don't think > toolstack is in a position to sanitise that nor should it

[Xen-devel] ARM bare metal application test

2016-05-09 Thread Ivan Pavić2
Hello Julien, Julien Grall wrote: > Guest are booting with MMU disabled, so 0x80008000 will be the physical > address. > The toolstack will load the kernel at this physical address. However, > the start of the guest RAM for Xen 4.7 is 0x4000 (see > include/public/arch-arm.h). Can you try to

[Xen-devel] Odgovor: ARM bare metal application test

2016-05-09 Thread Ivan Pavić2
Hello, > Correct, so the end of the RAM bank would be 0x4200. I am a bit > surprised that the toolstack does not complain when trying to load the > kernel at 0x80008000. > Can you paste the dump of xl -vvv create... ? $ xl -vvv create dom.cfg Parsing config from dom.cfg libxl: debug: libxl_c

[Xen-devel] Odgovor: ARM bare metal application test

2016-05-09 Thread Ivan Pavić2
Konrad Rzeszutek Wilk wrote: > OK, but that makes an ELF file. I believe (based on the Booting) you need to > extract > the binary code out and also fixup the branch instructions (maybe make > __Start = 0;?). > The Booting says: > - The boot loader is expected to call the kernel image by jumpi

[Xen-devel] ARM bare metal application test

2016-05-09 Thread Ivan Pavić2
Julien Grail wrote: > You can dump the registers of a vCPU with xenctx. > $PREFIX/lib/xen/bin/xenctx domid > $PREFIX is the path where xen tools have been installed (i.e --prefix on > the configure). The default path is /usr/local/ Thanks for advice. I discovered that the PC has value 0x0C and

[Xen-devel] ARM bare metal application test

2016-05-09 Thread Ivan Pavić2
Hello, I'm trying to build simple bare metal application on ARM Cortex A7. I reached the phase in which I successfully created domain. Now, I would like to check if application is really running (it runs according xl list). But i need some simple interaction or at least console output. So far thi

Re: [Xen-devel] Odroid XU3 support

2016-04-28 Thread Ivan Pavić2
> Xen is not ready for big.LITTLE, so I would highly recommend you to > disable either all the Cortex-A15 or Cortex-A7. > For your information, I am planning to send a patch to park any CPUs > whose MIDR is not matching the boot CPU one. > Julien Grall Ok, I decided to use A15s... How can I

[Xen-devel] Odroid XU3 support

2016-04-25 Thread Ivan Pavić2
Hello, i'm trying to boot dom0 linux on exynos5422 platform on A15 (big cpu cluster). From the past mailing lists on this link: http://lists.xen.org/archives/html/xen-devel/2016-02/msg02275.html) I'm not sure that is well defined how to change A7's for A15's. Should change be in DTS or should