[Xen-devel] [linux-next test] 122463: regressions - FAIL

2018-04-28 Thread osstest service owner 
flight 122463 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122463/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemut-debianhvm-amd64 16 guest-localmigrate/x10 fail REGR. 
vs. 122395
 test-armhf-armhf-libvirt  7 xen-boot fail REGR. vs. 122395
 test-armhf-armhf-xl-vhd   7 xen-boot fail REGR. vs. 122395
 test-armhf-armhf-xl-multivcpu  7 xen-bootfail REGR. vs. 122395
 test-armhf-armhf-xl-credit2   7 xen-boot fail REGR. vs. 122395
 test-armhf-armhf-xl-cubietruck  7 xen-boot   fail REGR. vs. 122395
 test-armhf-armhf-libvirt-raw  7 xen-boot fail REGR. vs. 122395

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-xl-arndale  10 debian-install   fail  like 122358
 test-armhf-armhf-xl-rtds 10 debian-install   fail  like 122358
 test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stopfail like 122395
 test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 122395
 test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stopfail like 122395
 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stopfail like 122395
 test-armhf-armhf-libvirt-xsm 10 debian-install   fail  like 122395
 test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stopfail like 122395
 test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 122395
 test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail like 122395
 test-amd64-amd64-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-amd64-amd64-libvirt 13 migrate-support-checkfail   never pass
 test-amd64-i386-libvirt-xsm  13 migrate-support-checkfail   never pass
 test-amd64-i386-libvirt  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl-xsm  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl-credit2  13 migrate-support-checkfail   never pass
 test-arm64-arm64-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl-credit2  14 saverestore-support-checkfail   never pass
 test-arm64-arm64-xl-xsm  14 saverestore-support-checkfail   never pass
 test-arm64-arm64-libvirt-xsm 14 saverestore-support-checkfail   never pass
 test-arm64-arm64-xl  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl  14 saverestore-support-checkfail   never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-armhf-armhf-xl  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl  14 saverestore-support-checkfail   never pass
 test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2  fail never pass
 test-amd64-amd64-libvirt-vhd 12 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-xsm  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-xsm  14 saverestore-support-checkfail   never pass
 test-amd64-i386-xl-pvshim12 guest-start  fail   never pass
 test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop  fail never pass
 test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass
 test-amd64-amd64-xl-qemut-win10-i386 10 windows-installfail never pass
 test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass
 test-amd64-amd64-xl-qemuu-win10-i386 10 windows-installfail never pass

version targeted for testing:
 linux679c0aaddcc6cb92d22ec93fe6c8bc5b9f2d62c5
baseline version:
 linux6d08b06e67cd117f6992c46611dfb4ce267cd71e

Last test of basis  (not found) 
Failing since   (not found) 
Testing same since   122463  2018-04-27 09:18:50 Z1 days1 attempts

jobs:
 build-amd64-xsm  pass
 build-arm64-xsm  pass
 build-armhf-xsm  pass
 build-i386-xsm   pass
 build-amd64  pass
 build-arm64  pass
 build-armhf  pass
 build-i386   pass
 build-amd64-libvirt  pass
 build-arm64-libvirt  pass
 build-armhf-libvirt  pass
 build-i386-libvirt   pass
 build-amd64-pvops

[Xen-devel] [xen-4.6-testing test] 122461: tolerable FAIL - PUSHED

2018-04-28 Thread osstest service owner 
flight 122461 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122461/

Failures :-/ but no regressions.

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow 16 guest-localmigrate/x10 
fail baseline untested
 test-xtf-amd64-amd64-1  50 xtf/test-hvm64-lbr-tsx-vmentry fail like 121949
 test-armhf-armhf-libvirt 14 saverestore-support-checkfail  like 121991
 test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 121991
 test-armhf-armhf-xl-rtds 16 guest-start/debian.repeatfail  like 121991
 test-armhf-armhf-libvirt-raw 13 saverestore-support-checkfail  like 121991
 test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stopfail like 121991
 test-armhf-armhf-libvirt-xsm 14 saverestore-support-checkfail  like 121991
 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stopfail like 121991
 test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 121991
 test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop fail like 121991
 test-xtf-amd64-amd64-1   37 xtf/test-hvm32pae-memop-seg  fail   never pass
 test-xtf-amd64-amd64-1   52 xtf/test-hvm64-memop-seg fail   never pass
 test-xtf-amd64-amd64-2   37 xtf/test-hvm32pae-memop-seg  fail   never pass
 test-xtf-amd64-amd64-4   37 xtf/test-hvm32pae-memop-seg  fail   never pass
 test-xtf-amd64-amd64-1   76 xtf/test-pv32pae-xsa-194 fail   never pass
 test-xtf-amd64-amd64-2   52 xtf/test-hvm64-memop-seg fail   never pass
 test-xtf-amd64-amd64-4   52 xtf/test-hvm64-memop-seg fail   never pass
 test-xtf-amd64-amd64-2   76 xtf/test-pv32pae-xsa-194 fail   never pass
 test-xtf-amd64-amd64-4   76 xtf/test-pv32pae-xsa-194 fail   never pass
 test-xtf-amd64-amd64-5   37 xtf/test-hvm32pae-memop-seg  fail   never pass
 test-amd64-amd64-libvirt 13 migrate-support-checkfail   never pass
 test-xtf-amd64-amd64-3   37 xtf/test-hvm32pae-memop-seg  fail   never pass
 test-xtf-amd64-amd64-5   52 xtf/test-hvm64-memop-seg fail   never pass
 test-xtf-amd64-amd64-3   52 xtf/test-hvm64-memop-seg fail   never pass
 test-amd64-i386-libvirt  13 migrate-support-checkfail   never pass
 test-xtf-amd64-amd64-5   76 xtf/test-pv32pae-xsa-194 fail   never pass
 test-amd64-i386-libvirt-xsm  13 migrate-support-checkfail   never pass
 test-xtf-amd64-amd64-3   76 xtf/test-pv32pae-xsa-194 fail   never pass
 test-amd64-amd64-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-armhf-armhf-xl-arndale  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-arndale  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-libvirt 13 migrate-support-checkfail   never pass
 test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2  fail never pass
 test-armhf-armhf-xl-rtds 13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-rtds 14 saverestore-support-checkfail   never pass
 test-amd64-amd64-libvirt-vhd 12 migrate-support-checkfail   never pass
 test-armhf-armhf-libvirt-raw 12 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-xsm  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-xsm  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl-credit2  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-credit2  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl-cubietruck 13 migrate-support-checkfail never pass
 test-armhf-armhf-xl-cubietruck 14 saverestore-support-checkfail never pass
 test-armhf-armhf-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-vhd  12 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-vhd  13 saverestore-support-checkfail   never pass
 test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop  fail never pass
 test-armhf-armhf-xl-multivcpu 13 migrate-support-checkfail  never pass
 test-armhf-armhf-xl-multivcpu 14 saverestore-support-checkfail  never pass
 test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail never pass
 test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail never pass
 test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass
 test-amd64-amd64-xl-qemut-win10-i386 10 windows-installfail never pass
 test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass
 test-amd64-amd64-xl-qemuu-win10-i386 10

[Xen-devel] [xen-4.7-testing test] 122459: regressions - trouble: broken/fail/pass

2018-04-28 Thread osstest service owner 
flight 122459 xen-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122459/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-xl-vhd  broken
 test-armhf-armhf-xl-vhd   4 host-install(4)broken REGR. vs. 122131
 test-xtf-amd64-amd64-3 50 xtf/test-hvm64-lbr-tsx-vmentry fail REGR. vs. 122131

Regressions which are regarded as allowable (not blocking):
 test-armhf-armhf-xl-rtds 12 guest-start  fail REGR. vs. 122131

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt-xsm 14 saverestore-support-checkfail  like 122131
 test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 122131
 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stopfail like 122131
 test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stopfail like 122131
 test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 122131
 test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop fail like 122131
 test-armhf-armhf-libvirt-raw 13 saverestore-support-checkfail  like 122131
 test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail like 122131
 test-armhf-armhf-libvirt 14 saverestore-support-checkfail  like 122131
 test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stopfail like 122131
 test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stopfail like 122131
 test-amd64-amd64-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-amd64-i386-libvirt-xsm  13 migrate-support-checkfail   never pass
 test-amd64-amd64-libvirt 13 migrate-support-checkfail   never pass
 test-amd64-i386-libvirt  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl-credit2  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl-credit2  14 saverestore-support-checkfail   never pass
 test-arm64-arm64-xl-xsm  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl-xsm  14 saverestore-support-checkfail   never pass
 test-arm64-arm64-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-arm64-arm64-libvirt-xsm 14 saverestore-support-checkfail   never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-armhf-armhf-xl-arndale  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-arndale  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl-xsm  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-xsm  14 saverestore-support-checkfail   never pass
 test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2  fail never pass
 test-amd64-amd64-libvirt-vhd 12 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-credit2  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-credit2  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl-multivcpu 13 migrate-support-checkfail  never pass
 test-armhf-armhf-xl-multivcpu 14 saverestore-support-checkfail  never pass
 test-armhf-armhf-xl-cubietruck 13 migrate-support-checkfail never pass
 test-armhf-armhf-xl-cubietruck 14 saverestore-support-checkfail never pass
 test-armhf-armhf-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-armhf-armhf-libvirt-raw 12 migrate-support-checkfail   never pass
 test-arm64-arm64-xl  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-libvirt 13 migrate-support-checkfail   never pass
 test-amd64-amd64-xl-qemut-win10-i386 10 windows-installfail never pass
 test-amd64-amd64-xl-qemuu-win10-i386 10 windows-installfail never pass
 test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass
 test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass

version targeted for testing:
 xen  a8ef07566fa8fe9a2e8db745014d93e259b66785
baseline version:
 xen  9680710bed1c174ced7a170cb94e30b4ae4fff5e

Last test of basis   122131  2018-04-09 10:53:16 Z   19 days
Failing since122353  2018-04-23 11:05:56 Z5 days4 attempts
Testing same since   122459  2018-04-27 07:28:31 Z1 days1 attempts


People who touched revisions under test:
  Andrew Cooper 
  Anthony PERARD 
  Ian Jackson 
  Jan Beulich 
  Kevin Tian

Re: [Xen-devel] [cubieboard2] Bringing up dom0

2018-04-28 Thread Andrew Cooper 
On 28/04/18 18:34, Ajay Garg wrote:
> Hi Andrew.
>
> Thanks for the reply.
>
> On Sat, Apr 28, 2018 at 10:57 PM, Andrew Cooper
> > wrote:
>
> On 28/04/18 18:12, Ajay Garg wrote:
>> Hi All.
>>
>> We have brought up the cubieboard2 from almost scratch, following
>> are the steps done :
>>
>> 
>>
>> == getting xen ready ==
>>
>> i)
>> Compiled xen on cubieboard itself, via :
>>
>>    * git clone git://xenbits.xen.org/xen.git
>> 
>>    * cd xen
>> .  * ./configure --libdir=/usr/lib
>>    * make debball CONFIG_EARLY_PRINTK=sun7i -j4
>>    * sudo dpkg -i dist/xen-upstream-4.11-unstable.deb
>>    * sudo reboot
>>
>> ii)
>> Upon reboot, "sudo xl list" gives following :
>>
>> ##
>> debian@debian-armhf:~$ sudo  xl list
>> [sudo] password for debian:
>> xencall: error: Could not obtain handle on privileged command
>> interface: No such file or directory
>> libxl: error: libxl.c:102:libxl_ctx_alloc: cannot open libxc
>> handle: No such file or directory
>> cannot init xl context
>> ##
>
> This means that /dev/xen/privcmd (or the legacy /proc/xen/privcmd)
> device isn't available.
>
> First check that you have actually booted Xen with Linux as dom0. 
> You don't show any logs in this final section, and simply
> installing the debball and rebooting won't typically cause Xen to
> be the head of the boot list.
>
>
> Yes, I haven't been able to setup xen bootup.
>
> That's why, requested help regarding the changes that are required in
> https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/sun7i-a20-cubieboard2.dts,
> that would cause dom0 to boot up.
>
>
> Sorry for the confusion.

Ah - sorry.  I misunderstood.  I'm afraid you're going to have to wait
for some people more knowledge about ARM to answer.

~Andrew
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] [cubieboard2] Bringing up dom0

2018-04-28 Thread Ajay Garg 
Hi Andrew.

Thanks for the reply.

On Sat, Apr 28, 2018 at 10:57 PM, Andrew Cooper 
wrote:

> On 28/04/18 18:12, Ajay Garg wrote:
>
> Hi All.
>
> We have brought up the cubieboard2 from almost scratch, following are the
> steps done :
>
> 
>
> == getting xen ready ==
>
> i)
> Compiled xen on cubieboard itself, via :
>
>* git clone git://xenbits.xen.org/xen.git
>* cd xen
> .  * ./configure --libdir=/usr/lib
>* make debball CONFIG_EARLY_PRINTK=sun7i -j4
>* sudo dpkg -i dist/xen-upstream-4.11-unstable.deb
>* sudo reboot
>
> ii)
> Upon reboot, "sudo xl list" gives following :
>
> ##
> debian@debian-armhf:~$ sudo  xl list
> [sudo] password for debian:
> xencall: error: Could not obtain handle on privileged command interface:
> No such file or directory
> libxl: error: libxl.c:102:libxl_ctx_alloc: cannot open libxc handle: No
> such file or directory
> cannot init xl context
> ##
>
>
> This means that /dev/xen/privcmd (or the legacy /proc/xen/privcmd) device
> isn't available.
>
> First check that you have actually booted Xen with Linux as dom0.  You
> don't show any logs in this final section, and simply installing the
> debball and rebooting won't typically cause Xen to be the head of the boot
> list.
>

Yes, I haven't been able to setup xen bootup.

That's why, requested help regarding the changes that are required in
https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/sun7i-a20-cubieboard2.dts,
that would cause dom0 to boot up.


Sorry for the confusion.


Thanks and Regards,
Ajay
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] [cubieboard2] Bringing up dom0

2018-04-28 Thread Andrew Cooper 
On 28/04/18 18:12, Ajay Garg wrote:
> Hi All.
>
> We have brought up the cubieboard2 from almost scratch, following are
> the steps done :
>
> 
>
> == getting xen ready ==
>
> i)
> Compiled xen on cubieboard itself, via :
>
>    * git clone git://xenbits.xen.org/xen.git
> 
>    * cd xen
> .  * ./configure --libdir=/usr/lib
>    * make debball CONFIG_EARLY_PRINTK=sun7i -j4
>    * sudo dpkg -i dist/xen-upstream-4.11-unstable.deb
>    * sudo reboot
>
> ii)
> Upon reboot, "sudo xl list" gives following :
>
> ##
> debian@debian-armhf:~$ sudo  xl list
> [sudo] password for debian:
> xencall: error: Could not obtain handle on privileged command
> interface: No such file or directory
> libxl: error: libxl.c:102:libxl_ctx_alloc: cannot open libxc handle:
> No such file or directory
> cannot init xl context
> ##

This means that /dev/xen/privcmd (or the legacy /proc/xen/privcmd)
device isn't available.

First check that you have actually booted Xen with Linux as dom0.  You
don't show any logs in this final section, and simply installing the
debball and rebooting won't typically cause Xen to be the head of the
boot list.

Beyond that, double check your Linux kernel configuration options when
it comes to Xen support.

~Andrew
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

[Xen-devel] [cubieboard2] Bringing up dom0

2018-04-28 Thread Ajay Garg 
Hi All.

We have brought up the cubieboard2 from almost scratch, following are the
steps done :


== u-boot ==

u-boot has been compiled using bleeding-edge mainline
(ec5c4a8fd64a178a4d159917cda0aa176e5a9be5), via :

* make Cubieboard2_defconfig
* make ARCH=arm
CROSS_COMPILE=/home/ajay/arm-toolchain-6.2/arm-linux-gnueabihf-

This gives us u-boot-sunxi-with-spl.bin



== kernel ==

kernel also has been compiled using bleeding-edge mainline
(6d08b06e67cd117f6992c46611dfb4ce267cd71e) via :

* make clean
* make ARCH=arm sunxi_defconfig menuconfig

  In the menu, enabled following additional features :

  * General setup => System V IPC
  * General setup => POSIX Message Queues
  * Kernel features => Xen guest support on ARM


* make -j$(nproc) ARCH=arm
CROSS_COMPILE=/home/ajay/arm-toolchain-6.2/arm-linux-gnueabihf- zImage
* make -j$(nproc) ARCH=arm
CROSS_COMPILE=/home/ajay/arm-toolchain-6.2/arm-linux-gnueabihf-
sun7i-a20-cubieboard2.dtb

This gives us zImage and sun7i-a20-cubieboard2.dtb.



== integration, and starting up ==

Followed the steps as per
https://github.com/maronai/cubieboard/wiki/3.1.-Compiling-mainline-kernel-for-CubieBoard2-and-CubieTruck,
but with following differences :

a)
Used u-boot-sunxi-with-spl.bin, zImage, sun7i-a20-cubieboard2.dtb from
above steps.

b)
Used (and compiled to boot.scr) the following boot.cmd :

fatload mmc 0 0x4600 zImage
fatload mmc 0 0x4900 sun7i-a20-cubieboard2.dtb
setenv bootargs console=ttyS0,115200 rw root=/dev/mmcblk0p2
bootz 0x4600 - 0x4900

c)
Extracted debian-wheezy-7.5-armhf.com-20140603.tar to the rootfs partition
on the sd-card.

d)
Finally, inserted the sdcard in cubieboard2, following are the brief bootup
logs :

##
U-Boot SPL 2018.05-rc2-00118-gec5c4a8 (Apr 28 2018 - 08:40:48
+0530)
DRAM: 1024
MiB
CPU: 91200Hz, AXI/AHB/APB:
3/2/2
Trying to boot from
MMC1




U-Boot 2018.05-rc2-00118-gec5c4a8 (Apr 28 2018 - 08:40:48 +0530) Allwinner
Techy


CPU:   Allwinner A20
(SUN7I)
Model: Cubietech
Cubieboard2
I2C:
ready
DRAM:  1
GiB
MMC:   SUNXI SD/MMC:
0
Loading Environment from FAT... *** Warning - bad CRC, using default
environment


Failed
(-5)
In:
serial
Out:
serial
Err:
serial
SCSI:  SATA link 0
timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA
mode
flags: ncq stag pm led clo only pmp pio slum part ccc
apst
Net:   eth0: ethernet@01c5

starting
USB...
USB0:   USB EHCI
1.00
USB1:   USB OHCI
1.0
USB2:   USB EHCI
1.00
USB3:   USB OHCI
1.0
scanning bus 0 for devices... 1 USB Device(s)
found
scanning bus 2 for devices... 1 USB Device(s)
found
   scanning usb for storage devices... 0 Storage Device(s)
found
Hit any key to stop autoboot:
0
switch to partitions #0,
OK
mmc0 is current
device
Scanning mmc
0:1...
Found U-Boot script
/boot.scr
245 bytes read in 12 ms (19.5
KiB/s)
## Executing script at
4310
4076736 bytes read in 247 ms (15.7
MiB/s)
26147 bytes read in 24 ms (1
MiB/s)
## Flattened Device Tree blob at
4900
   Booting using the fdt blob at
0x4900
   Loading Device Tree to 49ff6000, end 49fff622 ...
OK


Starting kernel
...


[0.00] Booting Linux on physical CPU
0x0
[0.00] Linux version 4.17.0-rc2 (ajay@latitude-3480) (gcc version
6.2.18
[0.00] CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7),
cr=10c5387d
[0.00] CPU: div instructions available: patching division
code
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
instructie
[0.00] OF: fdt: Machine model: Cubietech
Cubieboard2
[0.00] Memory policy: Data cache
writealloc
[0.00] cma: Reserved 16 MiB at
0x7f00
[0.00] psci: probing for conduit method from
DT.
[0.00] psci: Using PSCI v0.1 Function IDs from
DT
[0.00] random: get_random_bytes called from start_kernel+0xa0/0x3fc
wit0
[0.00] percpu: Embedded 16 pages/cpu @(ptrval) s34764 r8192 d22580
u6556
[0.00] Built 1 zonelists, mobility grouping on.  Total pages:
260608
[0.00] Kernel command line: console=ttyS0,115200 rw
root=/dev/mmcblk0p2
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288
bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144
bytes)
[0.00] Memory: 1013064K/1048576K available (6144K kernel code, 427K
rwd)
[0.00] Virtual kernel memory
layout:
[0.00] vector  : 0x - 0x1000   (   4
kB)
[0.00] fixmap  : 0xffc0 - 0xfff0   (3072
kB)
[0.00] vmalloc : 0xf080 - 0xff80   ( 240
MB)
[0.00] lowmem  : 0xc000 - 0xf000   ( 768
MB)
[0.00] pkmap   : 0xbfe0 - 0xc000   (   2
MB)
[0.00] modules : 0xbf00 - 0xbfe0   (  14
MB)
[0.00]   .text : 0x(ptrval) - 0x(ptrval)   (7136
kB)
[0.00]   .init : 0x(ptrval) - 0x(ptrval)   (1024
kB)
[0.00]   .data : 0x(ptrval) - 0x(ptrval)   ( 428
kB)
[0.00].bss :

Re: [Xen-devel] [PATCH v5] x86/mm: Suppresses vm_events caused by page-walks

2018-04-28 Thread Tamas K Lengyel 
On Sat, Apr 28, 2018 at 12:13 AM, Razvan Cojocaru
 wrote:
> On 04/28/2018 12:30 AM, Tamas K Lengyel wrote:
>>
>> On Mon, Apr 23, 2018 at 2:00 AM, Alexandru Isaila
>>  wrote:
>>>
>>> This patch is adding a way to enable/disable inguest pagefault
>>> events. It introduces the xc_monitor_inguest_pagefault function
>>> and adds the inguest_pagefault_disabled in the monitor structure.
>>> This is needed by the introspection so it will only get gla
>>> faults and not get spammed with other faults.
>>> In p2m_mem_access_check() we emulate so no event will get sent.
>>
>>
>> This looks good to me, but is the emulator able to handle all
>> instructions that may trigger it here?
>
>
> That's a very good question. We think not, but we now have the UNIMPLEMENTED
> emulator event. The thought here is that the emulator would be able to
> handle most cases, and then the ones it can't handle we can handle with
> altp2m.
>
> Of course, it's not ideal - we'd rather have a mechanism that's consistently
> foolproof, but I believe that Jan's objection is correct: we can't really be
> sure that the first time we get into access_check() with a specific
> [RIP:GLA] pair we need to set the A bit and the second time the D bit
> (interrupts may trip this logic up). Furthermore, with SVM the GLA is not
> available for page faults (although that's fixable by comparing GPAs).
>
> If there's a better way to do this optimization that we haven't seen we'd be
> happy to switch the implementation. Suggestions are welcome.

My only worry is that this interface as-is will give someone the false
impression that this will "just work" all the time. Which is not the
case. If it needs the UNIMPLEMENTED event to be enabled as well I
would either make that a requirement for enabling this feature, or at
the minimum extensively documenting how that should be setup,
including an example in xen-access.c

Tamas

___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

[Xen-devel] [libvirt test] 122455: tolerable all pass - PUSHED

2018-04-28 Thread osstest service owner 
flight 122455 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122455/

Failures :-/ but no regressions.

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt-xsm 14 saverestore-support-checkfail  like 122404
 test-armhf-armhf-libvirt 14 saverestore-support-checkfail  like 122404
 test-armhf-armhf-libvirt-raw 13 saverestore-support-checkfail  like 122404
 test-amd64-amd64-libvirt 13 migrate-support-checkfail   never pass
 test-amd64-i386-libvirt  13 migrate-support-checkfail   never pass
 test-amd64-i386-libvirt-xsm  13 migrate-support-checkfail   never pass
 test-amd64-amd64-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-arm64-arm64-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-arm64-arm64-libvirt-xsm 14 saverestore-support-checkfail   never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-arm64-arm64-libvirt-qcow2 12 migrate-support-checkfail never pass
 test-arm64-arm64-libvirt-qcow2 13 saverestore-support-checkfail never pass
 test-amd64-amd64-libvirt-vhd 12 migrate-support-checkfail   never pass
 test-armhf-armhf-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-armhf-armhf-libvirt 13 migrate-support-checkfail   never pass
 test-arm64-arm64-libvirt 13 migrate-support-checkfail   never pass
 test-arm64-arm64-libvirt 14 saverestore-support-checkfail   never pass
 test-armhf-armhf-libvirt-raw 12 migrate-support-checkfail   never pass

version targeted for testing:
 libvirt  f94e5b215720c91c60219f1694783a603f0b619c
baseline version:
 libvirt  a762701791a44c0fddb8f87d4442d58fdcd41aa7

Last test of basis   122404  2018-04-25 06:21:45 Z3 days
Testing same since   122455  2018-04-26 18:27:32 Z1 days1 attempts


People who touched revisions under test:
  Ján Tomko 
  Martin Kletzander 

jobs:
 build-amd64-xsm  pass
 build-arm64-xsm  pass
 build-armhf-xsm  pass
 build-i386-xsm   pass
 build-amd64  pass
 build-arm64  pass
 build-armhf  pass
 build-i386   pass
 build-amd64-libvirt  pass
 build-arm64-libvirt  pass
 build-armhf-libvirt  pass
 build-i386-libvirt   pass
 build-amd64-pvopspass
 build-arm64-pvopspass
 build-armhf-pvopspass
 build-i386-pvops pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm   pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsmpass
 test-amd64-amd64-libvirt-xsm pass
 test-arm64-arm64-libvirt-xsm pass
 test-armhf-armhf-libvirt-xsm pass
 test-amd64-i386-libvirt-xsm  pass
 test-amd64-amd64-libvirt pass
 test-arm64-arm64-libvirt pass
 test-armhf-armhf-libvirt pass
 test-amd64-i386-libvirt  pass
 test-amd64-amd64-libvirt-pairpass
 test-amd64-i386-libvirt-pair pass
 test-arm64-arm64-libvirt-qcow2   pass
 test-armhf-armhf-libvirt-raw pass
 test-amd64-amd64-libvirt-vhd pass



sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary

Re: [Xen-devel] [PATCH] [v3] x86: Convert x86_platform_ops to timespec64

2018-04-28 Thread Arnd Bergmann 
On Sat, Apr 28, 2018 at 12:21 AM, Joao Martins
 wrote:
> On 04/27/2018 09:13 PM, Arnd Bergmann wrote:
>> diff --git a/arch/x86/kernel/pvclock.c b/arch/x86/kernel/pvclock.c
>> index 761f6af6efa5..637982efecd8 100644
>> --- a/arch/x86/kernel/pvclock.c
>> +++ b/arch/x86/kernel/pvclock.c
>> @@ -123,28 +123,35 @@ u64 pvclock_clocksource_read(struct 
>> pvclock_vcpu_time_info *src)
>>
>>  void pvclock_read_wallclock(struct pvclock_wall_clock *wall_clock,
>>   struct pvclock_vcpu_time_info *vcpu_time,
>> - struct timespec *ts)
>> + struct timespec64 *ts)
>>  {
>>   u32 version;
>>   u64 delta;
>> - struct timespec now;
>> + struct timespec64 now;
>>
>>   /* get wallclock at system boot */
>>   do {
>>   version = wall_clock->version;
>>   rmb();  /* fetch version before time */
>> + /*
>> +  * Note: wall_clock->sec is a u32 value, so it can
>> +  * only store dates between 1970 and 2106. To allow
>> +  * times beyond that, we need to create a new hypercall
>> +  * interface with an extended pvclock_wall_clock structure
>> +  * like ARM has.
>> +  */
>>   now.tv_sec  = wall_clock->sec;
>
> IIUC the interface you're probably speaking about is common to both ARM and 
> x86
> on Xen[*] (since Xen 4.6) i.e.
>
> now.tv_sec  = ((uint64_t)s->wc_sec_hi << 32) | s->wc_sec;
>
> s representing struct shared_info like on ARM (there's a 32-bit hole where
> wc_sec_hi is placed on x86_64/ARM). Except on x86 32-bit guests wc_sec_hi is
> located elsewhere.
>
> Joao
>
> [*]
> https://xenbits.xen.org/docs/4.6-testing/hypercall/x86_64/include,public,xen.h.html#incontents_startofday_shared

Ah, good. How portable is that? Will it do the right thing (i.e.
guarantee to have
zeroes on the upper half, or the epoch if supported) on all versions of both KVM
and Xen, or do we need an additional check in there?

I'd suggest leaving the implementation of that to a follow-up patch that you
can add once my patch is merged.

Arnd

___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

[Xen-devel] [xen-unstable test] 122451: regressions - FAIL

2018-04-28 Thread osstest service owner 
flight 122451 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122451/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-libvirt-raw  6 xen-install  fail REGR. vs. 122343

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stopfail like 122332
 test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stopfail like 122343
 test-armhf-armhf-libvirt-xsm 14 saverestore-support-checkfail  like 122343
 test-armhf-armhf-libvirt 14 saverestore-support-checkfail  like 122343
 test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 122343
 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stopfail like 122343
 test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stopfail like 122343
 test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 122343
 test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail like 122343
 test-amd64-amd64-xl-pvhv2-intel 12 guest-start fail never pass
 test-amd64-amd64-xl-pvhv2-amd 12 guest-start  fail  never pass
 test-amd64-i386-xl-pvshim12 guest-start  fail   never pass
 test-amd64-i386-libvirt-xsm  13 migrate-support-checkfail   never pass
 test-amd64-i386-libvirt  13 migrate-support-checkfail   never pass
 test-amd64-amd64-libvirt 13 migrate-support-checkfail   never pass
 test-amd64-amd64-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl  14 saverestore-support-checkfail   never pass
 test-arm64-arm64-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-arm64-arm64-libvirt-xsm 14 saverestore-support-checkfail   never pass
 test-arm64-arm64-xl-xsm  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl-xsm  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl-arndale  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-arndale  14 saverestore-support-checkfail   never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2  fail never pass
 test-amd64-amd64-libvirt-vhd 12 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-cubietruck 13 migrate-support-checkfail never pass
 test-armhf-armhf-xl-cubietruck 14 saverestore-support-checkfail never pass
 test-armhf-armhf-xl-xsm  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-xsm  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl-rtds 13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-rtds 14 saverestore-support-checkfail   never pass
 test-armhf-armhf-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-multivcpu 13 migrate-support-checkfail  never pass
 test-armhf-armhf-xl  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl-multivcpu 14 saverestore-support-checkfail  never pass
 test-armhf-armhf-libvirt 13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl-credit2  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl-credit2  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl-credit2  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-credit2  14 saverestore-support-checkfail   never pass
 test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop  fail never pass
 test-armhf-armhf-xl-vhd  12 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-vhd  13 saverestore-support-checkfail   never pass
 test-amd64-amd64-xl-qemut-win10-i386 10 windows-installfail never pass
 test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass
 test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass
 test-amd64-amd64-xl-qemuu-win10-i386 10 windows-installfail never pass

version targeted for testing:
 xen  0d16ece0c5adb960ee4e45f12183bcac8fe6d50a
baseline version:
 xen  a6aa678fa380e9369cc44701a181142322b3a4b0

Last test of basis   122343  2018-04-17 04:06:26 Z   11 days
Failing since122363  2018-04-23 12:06:44 Z4 days3 attempts
Testing same since   122451  2018-04-26 15:16:29 Z1 days1 attempts


People who touched revisions under test:
  Andrew Cooper 
  Anthony PERARD

[Xen-devel] [distros-debian-stretch test] 74646: tolerable FAIL

2018-04-28 Thread Platform Team regression test user 
flight 74646 distros-debian-stretch real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74646/

Failures :-/ but no regressions.

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-armhf-stretch-netboot-pygrub 10 debian-di-install fail like 
74635
 test-amd64-amd64-amd64-stretch-netboot-pvgrub 10 debian-di-install fail like 
74635
 test-amd64-amd64-i386-stretch-netboot-pygrub 10 debian-di-install fail like 
74635
 test-amd64-i386-amd64-stretch-netboot-pygrub 10 debian-di-install fail like 
74635
 test-amd64-i386-i386-stretch-netboot-pvgrub 10 debian-di-install fail like 
74635

baseline version:
 flight   74635

jobs:
 build-amd64  pass
 build-armhf  pass
 build-i386   pass
 build-amd64-pvopspass
 build-armhf-pvopspass
 build-i386-pvops pass
 test-amd64-amd64-amd64-stretch-netboot-pvgrubfail
 test-amd64-i386-i386-stretch-netboot-pvgrub  fail
 test-amd64-i386-amd64-stretch-netboot-pygrub fail
 test-armhf-armhf-armhf-stretch-netboot-pygrubfail
 test-amd64-amd64-i386-stretch-netboot-pygrub fail



sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images

Logs, config files, etc. are available at
http://osstest.xs.citrite.net/~osstest/testlogs/logs

Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Push not applicable.


___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

[Xen-devel] [PATCH] xen: char: Remove unnecessary (uart->irq > 0) check

2018-04-28 Thread Amit Singh Tomar 
While working on MVEBU uart driver, Julien pointed out that (uart->irq > 0)
check is unnecessary during irq set up.if ever there is an invalid irq, driver
initialization itself would be bailed out from platform_get_irq.

This patch would remove similar check for other uart drivers present in XEN.

Signed-off-by: Amit Singh Tomar 
---
* This patch is only compiled tested.
---
 xen/drivers/char/cadence-uart.c | 15 ---
 xen/drivers/char/ns16550.c  | 35 ++-
 xen/drivers/char/omap-uart.c|  2 +-
 xen/drivers/char/pl011.c| 13 +++--
 4 files changed, 30 insertions(+), 35 deletions(-)

diff --git a/xen/drivers/char/cadence-uart.c b/xen/drivers/char/cadence-uart.c
index 22905ba..1575787 100644
--- a/xen/drivers/char/cadence-uart.c
+++ b/xen/drivers/char/cadence-uart.c
@@ -72,13 +72,14 @@ static void __init cuart_init_postirq(struct serial_port 
*port)
 struct cuart *uart = port->uart;
 int rc;
 
-if ( uart->irq > 0 )
+uart->irqaction.handler = cuart_interrupt;
+uart->irqaction.name= "cadence-uart";
+uart->irqaction.dev_id  = port;
+
+if ( (rc = setup_irq(uart->irq, 0, >irqaction)) != 0 )
 {
-uart->irqaction.handler = cuart_interrupt;
-uart->irqaction.name= "cadence-uart";
-uart->irqaction.dev_id  = port;
-if ( (rc = setup_irq(uart->irq, 0, >irqaction)) != 0 )
-printk("ERROR: Failed to allocate cadence-uart IRQ %d\n", 
uart->irq);
+printk("ERROR: Failed to allocate cadence-uart IRQ %d\n", uart->irq);
+return;
 }
 
 /* Clear pending error interrupts */
@@ -130,7 +131,7 @@ static int __init cuart_irq(struct serial_port *port)
 {
 struct cuart *uart = port->uart;
 
-return ( (uart->irq > 0) ? uart->irq : -1 );
+return uart->irq;
 }
 
 static const struct vuart_info *cuart_vuart(struct serial_port *port)
diff --git a/xen/drivers/char/ns16550.c b/xen/drivers/char/ns16550.c
index f32dbd3..ba50a1e 100644
--- a/xen/drivers/char/ns16550.c
+++ b/xen/drivers/char/ns16550.c
@@ -714,18 +714,12 @@ static void __init ns16550_init_preirq(struct serial_port 
*port)
 
 static void ns16550_setup_postirq(struct ns16550 *uart)
 {
-if ( uart->irq > 0 )
-{
-/* Master interrupt enable; also keep DTR/RTS asserted. */
-ns_write_reg(uart,
- UART_MCR, UART_MCR_OUT2 | UART_MCR_DTR | UART_MCR_RTS);
-
-/* Enable receive interrupts. */
-ns_write_reg(uart, UART_IER, UART_IER_ERDAI);
-}
+/* Master interrupt enable; also keep DTR/RTS asserted. */
+ns_write_reg(uart, UART_MCR, UART_MCR_OUT2 | UART_MCR_DTR | UART_MCR_RTS);
+/* Enable receive interrupts. */
+ns_write_reg(uart, UART_IER, UART_IER_ERDAI);
 
-if ( uart->irq >= 0 )
-set_timer(>timer, NOW() + MILLISECS(uart->timeout_ms));
+set_timer(>timer, NOW() + MILLISECS(uart->timeout_ms));
 }
 
 static void __init ns16550_init_postirq(struct serial_port *port)
@@ -733,9 +727,6 @@ static void __init ns16550_init_postirq(struct serial_port 
*port)
 struct ns16550 *uart = port->uart;
 int rc, bits;
 
-if ( uart->irq < 0 )
-return;
-
 serial_async_transmit(port);
 
 init_timer(>timer, ns16550_poll, port, 0);
@@ -746,13 +737,14 @@ static void __init ns16550_init_postirq(struct 
serial_port *port)
 uart->timeout_ms = max_t(
 unsigned int, 1, (bits * uart->fifo_size * 1000) / uart->baud);
 
-if ( uart->irq > 0 )
+uart->irqaction.handler = ns16550_interrupt;
+uart->irqaction.name= "ns16550";
+uart->irqaction.dev_id  = port;
+
+if ( (rc = setup_irq(uart->irq, 0, >irqaction)) != 0 )
 {
-uart->irqaction.handler = ns16550_interrupt;
-uart->irqaction.name= "ns16550";
-uart->irqaction.dev_id  = port;
-if ( (rc = setup_irq(uart->irq, 0, >irqaction)) != 0 )
-printk("ERROR: Failed to allocate ns16550 IRQ %d\n", uart->irq);
+printk("ERROR: Failed to allocate ns16550 IRQ %d\n", uart->irq);
+return;
 }
 
 ns16550_setup_postirq(uart);
@@ -874,7 +866,8 @@ static void __init ns16550_endboot(struct serial_port *port)
 static int __init ns16550_irq(struct serial_port *port)
 {
 struct ns16550 *uart = port->uart;
-return ((uart->irq > 0) ? uart->irq : -1);
+
+return uart->irq;
 }
 
 static void ns16550_start_tx(struct serial_port *port)
diff --git a/xen/drivers/char/omap-uart.c b/xen/drivers/char/omap-uart.c
index d6a5d59..2ce4e71 100644
--- a/xen/drivers/char/omap-uart.c
+++ b/xen/drivers/char/omap-uart.c
@@ -294,7 +294,7 @@ static int __init omap_uart_irq(struct serial_port *port)
 {
 struct omap_uart *uart = port->uart;
 
-return ((uart->irq > 0) ? uart->irq : -1);
+return uart->irq;
 }
 
 static const struct vuart_info *omap_vuart_info(struct serial_port *port)
diff --git a/xen/drivers/char/pl011.c b/xen/drivers/char/pl011.c
index be67242..e007918 100644
---

Re: [Xen-devel] [PATCH] [v3] x86: Convert x86_platform_ops to timespec64

2018-04-28 Thread Jan Kiszka 
On 2018-04-27 22:13, Arnd Bergmann wrote:
> The x86 platform operations are fairly isolated, so we can
> change them from using timespec to timespec64. I checked that
> All the users and callers are safe, and there is only one
> critical function that is broken beyond 2106:
> 
> pvclock_read_wallclock() uses a 32-bit number of seconds since
> the epoch to communicate the boot time between host and guest
> in a virtual environment. This will work until 2106, but we
> should ideally find a replacement anyway. I've added a comment
> about it there.
> 
> Reviewed-by: Boris Ostrovsky 
> Signed-off-by: Arnd Bergmann 
> ---
> v2 changes:
> - move comment block (Boris)
> - remove unnecessary type cast (Boris)
> - fix format string (0day bot)
> - fix include order (0day bot)
> 
> v3 changes:
> - add jailhouse specific change
> - avoid include file header by relying on another
>   patch ("timekeeping: Remove timespec64 hack")
> 
> Not sure how we want to merge this (assuming the last modification
> worked, this has seen little testing). The "timekeeping: Remove
> timespec64 hack" patch should go through the timekeeping branch
> in tip, while this one is for x86. I assume the linux-tip maintainers
> can come up with a plan.
> ---
>  arch/x86/include/asm/intel_mid_vrtc.h|  4 ++--
>  arch/x86/include/asm/mc146818rtc.h   |  4 ++--
>  arch/x86/include/asm/pvclock.h   |  2 +-
>  arch/x86/include/asm/x86_init.h  |  6 +++---
>  arch/x86/kernel/jailhouse.c  |  2 +-
>  arch/x86/kernel/kvmclock.c   |  4 ++--
>  arch/x86/kernel/pvclock.c| 15 +++
>  arch/x86/kernel/rtc.c| 10 +-
>  arch/x86/platform/intel-mid/intel_mid_vrtc.c | 12 ++--
>  arch/x86/xen/time.c  | 10 +-
>  10 files changed, 38 insertions(+), 31 deletions(-)
> 
> diff --git a/arch/x86/include/asm/intel_mid_vrtc.h 
> b/arch/x86/include/asm/intel_mid_vrtc.h
> index 3016b1be..0b44b1abe4d9 100644
> --- a/arch/x86/include/asm/intel_mid_vrtc.h
> +++ b/arch/x86/include/asm/intel_mid_vrtc.h
> @@ -4,7 +4,7 @@
>  
>  extern unsigned char vrtc_cmos_read(unsigned char reg);
>  extern void vrtc_cmos_write(unsigned char val, unsigned char reg);
> -extern void vrtc_get_time(struct timespec *now);
> -extern int vrtc_set_mmss(const struct timespec *now);
> +extern void vrtc_get_time(struct timespec64 *now);
> +extern int vrtc_set_mmss(const struct timespec64 *now);
>  
>  #endif
> diff --git a/arch/x86/include/asm/mc146818rtc.h 
> b/arch/x86/include/asm/mc146818rtc.h
> index 1775a32f7ea6..97198001e567 100644
> --- a/arch/x86/include/asm/mc146818rtc.h
> +++ b/arch/x86/include/asm/mc146818rtc.h
> @@ -95,8 +95,8 @@ static inline unsigned char current_lock_cmos_reg(void)
>  unsigned char rtc_cmos_read(unsigned char addr);
>  void rtc_cmos_write(unsigned char val, unsigned char addr);
>  
> -extern int mach_set_rtc_mmss(const struct timespec *now);
> -extern void mach_get_cmos_time(struct timespec *now);
> +extern int mach_set_rtc_mmss(const struct timespec64 *now);
> +extern void mach_get_cmos_time(struct timespec64 *now);
>  
>  #define RTC_IRQ 8
>  
> diff --git a/arch/x86/include/asm/pvclock.h b/arch/x86/include/asm/pvclock.h
> index a7471dcd2205..b6033680d458 100644
> --- a/arch/x86/include/asm/pvclock.h
> +++ b/arch/x86/include/asm/pvclock.h
> @@ -12,7 +12,7 @@ void pvclock_set_flags(u8 flags);
>  unsigned long pvclock_tsc_khz(struct pvclock_vcpu_time_info *src);
>  void pvclock_read_wallclock(struct pvclock_wall_clock *wall,
>   struct pvclock_vcpu_time_info *vcpu,
> - struct timespec *ts);
> + struct timespec64 *ts);
>  void pvclock_resume(void);
>  
>  void pvclock_touch_watchdogs(void);
> diff --git a/arch/x86/include/asm/x86_init.h b/arch/x86/include/asm/x86_init.h
> index ce8b4da07e35..2d27236c16a3 100644
> --- a/arch/x86/include/asm/x86_init.h
> +++ b/arch/x86/include/asm/x86_init.h
> @@ -170,7 +170,7 @@ struct x86_cpuinit_ops {
>   void (*fixup_cpu_id)(struct cpuinfo_x86 *c, int node);
>  };
>  
> -struct timespec;
> +struct timespec64;
>  
>  /**
>   * struct x86_legacy_devices - legacy x86 devices
> @@ -264,8 +264,8 @@ struct x86_hyper_runtime {
>  struct x86_platform_ops {
>   unsigned long (*calibrate_cpu)(void);
>   unsigned long (*calibrate_tsc)(void);
> - void (*get_wallclock)(struct timespec *ts);
> - int (*set_wallclock)(const struct timespec *ts);
> + void (*get_wallclock)(struct timespec64 *ts);
> + int (*set_wallclock)(const struct timespec64 *ts);
>   void (*iommu_shutdown)(void);
>   bool (*is_untracked_pat_range)(u64 start, u64 end);
>   void (*nmi_init)(void);
> diff --git a/arch/x86/kernel/jailhouse.c b/arch/x86/kernel/jailhouse.c
> index fa183a131edc..a0b05bf185ac 100644
> --- a/arch/x86/kernel/jailhouse.c
> +++

Re: [Xen-devel] [PATCH v5] x86/mm: Suppresses vm_events caused by page-walks

2018-04-28 Thread Razvan Cojocaru 

On 04/28/2018 09:13 AM, Razvan Cojocaru wrote:

On 04/28/2018 12:30 AM, Tamas K Lengyel wrote:

On Mon, Apr 23, 2018 at 2:00 AM, Alexandru Isaila
 wrote:

This patch is adding a way to enable/disable inguest pagefault
events. It introduces the xc_monitor_inguest_pagefault function
and adds the inguest_pagefault_disabled in the monitor structure.
This is needed by the introspection so it will only get gla
faults and not get spammed with other faults.
In p2m_mem_access_check() we emulate so no event will get sent.


This looks good to me, but is the emulator able to handle all
instructions that may trigger it here?


That's a very good question. We think not, but we now have the 
UNIMPLEMENTED emulator event. The thought here is that the emulator 
would be able to handle most cases, and then the ones it can't handle we 
can handle with altp2m.


Of course, it's not ideal - we'd rather have a mechanism that's 
consistently foolproof, but I believe that Jan's objection is correct: 
we can't really be sure that the first time we get into access_check() 
with a specific [RIP:GLA] pair we need to set the A bit and the second 
time the D bit (interrupts may trip this logic up). Furthermore, with 
SVM the GLA is not available for page faults (although that's fixable by 
comparing GPAs).


If there's a better way to do this optimization that we haven't seen 
we'd be happy to switch the implementation. Suggestions are welcome.


The only surefire way we have here is to single-step with the monitor 
trap flag set and with an unrestricted altp2m - or similar. We're doing 
something like that with XenServer:


https://github.com/xenserver/xen.pg/blob/XS-7.1.x/master/xen-reexecute-instn-under-monitor-trap.patch

But IIRC that patch had basically been nacked at the time, and I don't 
see a nice way of making the same logic work with alt2pm _without_ 
having vm_events triggered (which is what this optimization is about), 
due to, mainly, the fact that hostp2m changes propagate into altp2ms.



Thanks,
Razvan

___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] [PATCH v5] x86/mm: Suppresses vm_events caused by page-walks

2018-04-28 Thread Razvan Cojocaru 

On 04/28/2018 12:30 AM, Tamas K Lengyel wrote:

On Mon, Apr 23, 2018 at 2:00 AM, Alexandru Isaila
 wrote:

This patch is adding a way to enable/disable inguest pagefault
events. It introduces the xc_monitor_inguest_pagefault function
and adds the inguest_pagefault_disabled in the monitor structure.
This is needed by the introspection so it will only get gla
faults and not get spammed with other faults.
In p2m_mem_access_check() we emulate so no event will get sent.


This looks good to me, but is the emulator able to handle all
instructions that may trigger it here?


That's a very good question. We think not, but we now have the 
UNIMPLEMENTED emulator event. The thought here is that the emulator 
would be able to handle most cases, and then the ones it can't handle we 
can handle with altp2m.


Of course, it's not ideal - we'd rather have a mechanism that's 
consistently foolproof, but I believe that Jan's objection is correct: 
we can't really be sure that the first time we get into access_check() 
with a specific [RIP:GLA] pair we need to set the A bit and the second 
time the D bit (interrupts may trip this logic up). Furthermore, with 
SVM the GLA is not available for page faults (although that's fixable by 
comparing GPAs).


If there's a better way to do this optimization that we haven't seen 
we'd be happy to switch the implementation. Suggestions are welcome.



Thanks,
Razvan

___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

[Xen-devel] [xen-4.10-testing test] 122449: regressions - FAIL

2018-04-28 Thread osstest service owner 
flight 122449 xen-4.10-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122449/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemut-debianhvm-amd64 16 guest-localmigrate/x10 fail REGR. 
vs. 122255
 build-armhf-xsm   6 xen-buildfail REGR. vs. 122255

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-xl-xsm   1 build-check(1)   blocked  n/a
 test-armhf-armhf-libvirt-xsm  1 build-check(1)   blocked  n/a
 test-amd64-amd64-xl-pvhv2-intel 12 guest-start fail never pass
 test-amd64-amd64-xl-pvhv2-amd 12 guest-start  fail  never pass
 test-amd64-i386-libvirt  13 migrate-support-checkfail   never pass
 test-amd64-amd64-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-amd64-i386-libvirt-xsm  13 migrate-support-checkfail   never pass
 test-amd64-amd64-libvirt 13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl  14 saverestore-support-checkfail   never pass
 test-arm64-arm64-libvirt-xsm 13 migrate-support-checkfail   never pass
 test-arm64-arm64-libvirt-xsm 14 saverestore-support-checkfail   never pass
 test-arm64-arm64-xl-xsm  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl-xsm  14 saverestore-support-checkfail   never pass
 test-arm64-arm64-xl-credit2  13 migrate-support-checkfail   never pass
 test-arm64-arm64-xl-credit2  14 saverestore-support-checkfail   never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-armhf-armhf-xl  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl-arndale  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-arndale  14 saverestore-support-checkfail   never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2  fail never pass
 test-amd64-amd64-libvirt-vhd 12 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-rtds 13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-rtds 14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl-cubietruck 13 migrate-support-checkfail never pass
 test-armhf-armhf-xl-cubietruck 14 saverestore-support-checkfail never pass
 test-armhf-armhf-xl-credit2  13 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-credit2  14 saverestore-support-checkfail   never pass
 test-armhf-armhf-xl-multivcpu 13 migrate-support-checkfail  never pass
 test-armhf-armhf-xl-multivcpu 14 saverestore-support-checkfail  never pass
 test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop  fail never pass
 test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop  fail never pass
 test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stop fail never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail never pass
 test-armhf-armhf-libvirt-raw 12 migrate-support-checkfail   never pass
 test-armhf-armhf-libvirt-raw 13 saverestore-support-checkfail   never pass
 test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop  fail never pass
 test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail never pass
 test-armhf-armhf-xl-vhd  12 migrate-support-checkfail   never pass
 test-armhf-armhf-xl-vhd  13 saverestore-support-checkfail   never pass
 test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail never pass
 test-armhf-armhf-libvirt 13 migrate-support-checkfail   never pass
 test-armhf-armhf-libvirt 14 saverestore-support-checkfail   never pass
 test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop  fail never pass
 test-amd64-amd64-xl-qemut-win10-i386 10 windows-installfail never pass
 test-amd64-amd64-xl-qemuu-win10-i386 10 windows-installfail never pass
 test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass
 test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass

version targeted for testing:
 xen  c30ab3d97c8ff0d2ed8948dd013737befc7a2223
baseline version:
 xen  8d37ee1d101248ba9cf44d79352ade3b376db55c

Last test of basis   122255  2018-04-13 14:59:05 Z   14 days
Failing since122356  2018-04-23 11:06:42 Z4 days3 attempts
Testing same since   122449  2018-04-26 13:36:26 Z1 days1 attempts


People who touched revisions under test:
  Andrew Cooper 
  Anthony PERARD