於 二，2015-06-16 於 11:58 +0200，Juergen Gross 提到：
On 06/16/2015 11:32 AM, 藍挺瑋 wrote:
於 二，2015-06-16 於 11:06 +0200，Juergen Gross 提到：
On 06/16/2015 10:55 AM, Ting-Wei Lan wrote:
Juergen Gross 於 西元2015年06月16日 12:30 寫道:
On 06/15/2015 09:03 PM, Ting-Wei Lan wrote:
於 一，2015-06-15 於
Hi all,
nbsp; nbsp; nbsp; nbsp;I wan#39;t to hash the kernel code
segment of HVM DomU in Xen hypervisor, so I have to transilate the virtral
address in VM to the virtral address in xen. Is there some easy ways ?
Hi all,
I wan't to hash the kernel code segment of HVM DomU in Xen hypervisor,
so I have to transilate the virtral address in VM to the virtral address in
xen. Is there some easy ways ?
I read the source code about memory in Xen and confuse the relationship
between the paddr and
Hi all,
I wan't to hash the kernel code segment of HVM DomU in Xen
hypervisor, so I have to transilate the virtral address in VM to the virtral
address in xen. Is there some easy ways ?
I read the source code about memory in Xen and confuse the
relationship between the paddr and
flight 58941 linux-3.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58941/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-win7-amd64 6 xen-boot fail REGR. vs. 30511
Tests which are
flight 58939 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58939/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-multivcpu 15 guest-start/debian.repeat fail REGR. vs. 58451
Tests which are
flight 58938 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58938/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-xsm 4 host-build-prep fail REGR. vs. 58917
[Dario was forgotten in this email. Adding him back..:-( ]
2015-06-27 12:53 GMT-07:00 Dagaen Golomb dgol...@seas.upenn.edu:
All,
Sorry for the repeated send to the mailing list, I forgot to add some
cc's and wanted to make sure
everyone was included.
This is the new patch that works
flight 58944 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58944/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-rumpuserxen-amd64 15
rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs.
flight 58942 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58942/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 9 windows-installfail REGR. vs. 58919
Tests which are failing
There is an added timer that only handles replenishments, which is
called at the time the next
replenishment will occur. To do this, we now also keep the depletedq
sorted. If it detects it has
moved a vCPU into the first [# CPUs] slots in the runq, it tickles the
runq with the added
2015-06-28 13:17 GMT-07:00 Dagaen Golomb dgol...@seas.upenn.edu:
There is an added timer that only handles replenishments, which is
called at the time the next
replenishment will occur. To do this, we now also keep the depletedq
sorted. If it detects it has
moved a vCPU into the
flight 58955 linux-3.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58955/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-win7-amd64 6 xen-boot fail REGR. vs. 30511
Tests which are
flight 58953 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58953/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-multivcpu 15 guest-start/debian.repeat fail in 58863 REGR.
vs. 58451
Tests
[Dario was forgotten in this email. Adding him back..:-( ]
Gah, how did I forget this! I've been meaning to make a text file of the
command so I never forget anyone.
Sorry for the repeated send to the mailing list, I forgot to add some
cc's and wanted to make sure
everyone was included.
There is an added timer that only handles replenishments, which is
called at the time the next
replenishment will occur. To do this, we now also keep the depletedq
sorted. If it detects it has
moved a vCPU into the first [# CPUs] slots in the runq, it tickles the
runq with the added
flight 58948 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58948/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 15
rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs.
PCI Pass-through in Xen ARM
--
Draft 2
Index
1. Background
2. Basic PCI Support in Xen ARM
2.1 pci_hostbridge and pci_hostbridge_ops
2.2 PHYSDEVOP_HOSTBRIDGE_ADD hypercall
3. Dom0 Access PCI devices
4. DomU assignment of PCI device
4.1 Holes in guest memory space
4.2
From: David Vrabel david.vra...@citrix.com
Date: Fri, 26 Jun 2015 16:15:18 +0100
On 27/06/15 00:17, Liang Li wrote:
The function netif_set_real_num_tx_queues() will return -EINVAL if
the second parameter 1, so call this function with the second
parameter set to 0 is meaningless.
flight 58956 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58956/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 9 windows-installfail REGR. vs. 58919
Regressions which are
Just let me rephrase this,
none means we don't check any reserved regions and then all rdm
policies would be ignored, so guest just work as before.
When or why would I write:
rdm = none
in my configuration file instead of just not saying anything?
As you know we just have two
flight 58958 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58958/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-rumpuserxen-i386 15
rumpuserxen-demo-xenstorels/xenstorels.repeat fail in 58948 pass in 58958
Change main_sched_rtds and related output functions to support per-VCPU
settings.
Changes on PATCH v2:
1) Remove per-domain output functions for RTDS scheduler.
2) Users now use '-v all' to specify all VCPUs.
3) Support outputting a subset of the parameters of the VCPUs of a specific
domain.
[Goal]
The current xl sched-rtds tool can only set the VCPUs of a domain to the same
parameter
although the scheduler supports VCPUs with different parameters. This patchset
is to
enable xl sched-rtds tool to configure the VCPUs of a domain with different
parameters.
This per-VCPU settings can
Add libxl_vcpu_sched_params_get/set and sched_rtds_vcpu_get/set functions to
support
per-VCPU settings.
Changes on PATCH v2:
1) New data structure (libxl_vcpu_sched_params and libxl_sched_params) to help
per-VCPU settings.
2) sched_rtds_vcpu_get now can return a random subset of the
Add two hypercalls(XEN_DOMCTL_SCHEDOP_getvcpuinfo/putvcpuinfo) to get/set a
domain's
per-VCPU parameters.
Changes on PATCH v2:
1) Change struct xen_domctl_scheduler_op, for transferring per-vcpu parameters
between libxc and hypervisor.
2) Handler of XEN_DOMCTL_SCHEDOP_getinfo now just returns
Add xc_sched_rtds_vcpu_get/set functions to interact with Xen to get/set a
domain's
per-VCPU parameters.
Changes on PATCH v2:
1) Minor modifications due to the change of struct xen_domctl_scheduler_op.
Signed-off-by: Chong Li chong...@wustl.edu
Signed-off-by: Meng Xu men...@cis.upenn.edu
flight 58960 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58960/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-multivcpu 15 guest-start/debian.repeat fail REGR. vs. 58451
Tests which are
28 matches
Mail list logo
