flight 94590 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94590/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-build fail REGR. vs. 94588
build-amd64
flight 94587 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94587/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REG
flight 94586 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94586/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 94554
test-amd64-i386-xl-qemuu-win
flight 94588 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94588/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 1f1ec99dea4d6d04fed96fa8a2e299212f6bc8cb
baseline version:
ovmf 4be1fbc287a2972a0cb420bc3a85372426c
flight 94580 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94580/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-rtds 9 debian-install fail blocked in 94487
build-i386-rumpuserxen
Hi Julien,
On 16 May 2016 at 19:28, Julien Grall wrote:
> Hi Fu Wei,
>
> (CC Stefano)
>
>
> On 10/05/16 15:03, fu@linaro.org wrote:
>>
>> From: Fu Wei
>>
>> delete: xen_linux, xen_initrd, xen_xsm
>> add: xen_module
>>
>> This update bases on
>> commit 0edd750e50698854068358ea53528100a91
flight 94584 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94584/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REG
On Thu, May 19, 2016 at 11:54:55PM +0300, Andrii Anisov wrote:
> Wei,
>
> Actually it should be the oldest patch in our current series, it was
> initial researches, I tried to fit the dom0 system rootfs into
> smallest possible initramfs so lean busybox was there.
>
> >> +#trap sigerr ERR
> > > -
flight 94583 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94583/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 4be1fbc287a2972a0cb420bc3a85372426c588b5
baseline version:
ovmf 758ea94651545896309725b53407e57e794
Julien,
>>We need to understand the use case and see if it is possible to generalize
>>it for everyone.
Well, the thing I would generalize is an understanding that real chips
(automotive IVI, mobile) have no or has limited SMMU functionality.
For a limited SMMU functionality I would name Renesas
Meng,
>> If the board is not supported by Xen, can we say Xen will support the
>> board with the warkaround?
I would not say boards are supported by XEN (except earlyprintk).
Rather architectures are supported in general, and SoC's are supported
in architecture implementation defined deviations (
All,
See the system details I can reveal below:
- There are two OS in the system Linux(Dom0) and Android(DomU)
- Android provides almost all infotainment functionality. Linux covers
functionality with higher reliability requirements and backup in case if
Android crashes/glitches.
-
Wei,
Actually it should be the oldest patch in our current series, it was
initial researches, I tried to fit the dom0 system rootfs into
smallest possible initramfs so lean busybox was there.
>> +#trap sigerr ERR
> > -trap sigerr ERR
>
> I know why you want to comment this out but you basically b
flight 94577 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94577/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt 3 host-install(3) broken REGR. vs. 94554
Hi Jan,
On 05/19/2016 04:09 AM, Jan Beulich wrote:
>>>+int __init amd_iommu_get_supported_ivhd_type(void)
>>>+{
>>>+if ( unlikely(acpi_gbl_FADT.boot_flags & ACPI_FADT_NO_MSI) )
>>>+return -EPERM;
>>
>>This check appears out of the blue, and isn't being mentioned in
>>the description
On Thu, May 19, 2016 at 04:07:00PM +0100, Wei Liu wrote:
> On Thu, May 19, 2016 at 10:56:06AM -0400, Konrad Rzeszutek Wilk wrote:
> > On Thu, May 19, 2016 at 03:41:49PM +0100, Andrew Cooper wrote:
> > > On 19/05/16 15:36, Konrad Rzeszutek Wilk wrote:
> > > > On Thu, May 19, 2016 at 03:29:45PM +0100
Julien,
> Thank you for your series. For the next version, can you CC the relevant
> maintainers using scripts/get_maintainer.pl for each patch?
We will take care to follow this rule further.
Andrii Anisov | Associate Manager, Engineering
GlobalLogic
Kyiv, 03038, Protasov Business Park, M.Grinc
flight 94578 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94578/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REG
Hi all,
I'm trying to install two versions of Xen, say Xen 4.6 and Xen
4.7-unstable, onto the same machine. I want them to exist at the same
time, instead of letting one override the other.
I'm thinking about this because sometimes I want to try out someone
else's code which uses an older or newe
flight 94570 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94570/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-libvirt-vhd 13 guest-saverestore fail in 94543 pass in 94570
test-amd64-i386-xl-qemuu-winxps
Hi Lurii,
On Thu, May 19, 2016 at 10:37 AM, Iurii Mykhalskyi
wrote:
> This patches introduce set of pv drivers interfaces.
Thank you very much for these pv drivers interfaces! It will be useful
for automotive applications, IMO.
However, I do have some questions:
I'm wondering how general the pv
Hello All,
I am trying to boot xen on OrangePi PC(based upon Allwinner H3). It is able
to boot on this target board but it hangs when it try to boot unmodified
linux guest(with xen configuration enable).
Please find following log for same.Can anyone guide me to debug this
problem(hang)?
Starting
On Thu, 19 May 2016, Stefano Stabellini wrote:
> On Thu, 19 May 2016, Juergen Gross wrote:
> > The pv_time_ops structure contains a function pointer for the
> > "steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86
> > uses its own mechanism to account for the "stolen" time a thre
On Thu, 19 May 2016, Juergen Gross wrote:
> The pv_time_ops structure contains a function pointer for the
> "steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86
> uses its own mechanism to account for the "stolen" time a thread wasn't
> able to run due to hypervisor scheduling.
>
flight 94575 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94575/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 758ea94651545896309725b53407e57e79477f28
baseline version:
ovmf 81c1460695f783a3f91431b2babea623556
On Thu, 19 May 2016, Juergen Gross wrote:
> On 19/05/16 12:48, Stefano Stabellini wrote:
> > On Thu, 19 May 2016, Jan Beulich wrote:
> > On 19.05.16 at 12:40, wrote:
> >>> On Thu, 19 May 2016, Juergen Gross wrote:
> > Alternatively, the easiest way will probably be to add a new VMASSIST,
>
flight 94572 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94572/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 guest-saverestorefail never pass
test-armhf-armhf-libvirt 12 migrate-sup
Hello,
While trying to solve a FreeBSD netfront bug [0] I came across a couple
of netif.h dark spots that I think should be documented in the netif.h
header. I'm willing to make those changes, but I want to make sure my
understanding is right.
Regarding checksum offloading, I had a hard time f
flight 94582 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94582/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 12
On Thu, May 19, 2016 at 4:11 AM, Dario Faggioli
wrote:
> Hey Wei,
>
> Again, I'm using an otherwise unnecessary cover letter for my analysis about
> <>. :-)
>
> I'd say yes, because the patch fixes an actual bug, in the form of a rather
> subtle race condition, which was all but trivial to spot.
On Thu, May 19, 2016 at 4:11 AM, Dario Faggioli
wrote:
> or (even in cases where there is no race, e.g., outside
> of Credit2) avoid using a time sample which may be rather
> old, and hence stale.
>
> In fact, we should only sample NOW() from _inside_
> the critical region within which the value w
On May 19, 2016 7:36 PM, Jan Beulich wrote:
> >>> On 19.05.16 at 13:26, wrote:
> > On May 19, 2016 2:13 PM, Jan Beulich wrote:
> >> >>> "Xu, Quan" 05/19/16 3:35 AM >>>
> >> >On May 19, 2016 8:33 AM, Tian, Kevin wrote:
> >> >> A single default value for both IOMMU-side and device-side is
> >> >
On Thu, May 19, 2016 at 10:56:06AM -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, May 19, 2016 at 03:41:49PM +0100, Andrew Cooper wrote:
> > On 19/05/16 15:36, Konrad Rzeszutek Wilk wrote:
> > > On Thu, May 19, 2016 at 03:29:45PM +0100, Andrew Cooper wrote:
> > >> Pandoc (version 1.12.4.2 from Debia
On 19/05/16 15:56, Konrad Rzeszutek Wilk wrote:
> On Thu, May 19, 2016 at 03:41:49PM +0100, Andrew Cooper wrote:
>> On 19/05/16 15:36, Konrad Rzeszutek Wilk wrote:
>>> On Thu, May 19, 2016 at 03:29:45PM +0100, Andrew Cooper wrote:
Pandoc (version 1.12.4.2 from Debian Jessie) complains at the e
>>> On 19.05.16 at 16:53, wrote:
> On Thu, May 19, 2016 at 08:44:59AM -0600, Jan Beulich wrote:
>> >>> On 19.05.16 at 16:34, wrote:
>> > We could even have the
>> > library name versions be set based on XEN_VERSION and XEN_SUBVERSION, so
>> > that we don't need to go around the different librar
On Thu, May 19, 2016 at 03:41:49PM +0100, Andrew Cooper wrote:
> On 19/05/16 15:36, Konrad Rzeszutek Wilk wrote:
> > On Thu, May 19, 2016 at 03:29:45PM +0100, Andrew Cooper wrote:
> >> Pandoc (version 1.12.4.2 from Debian Jessie) complains at the embedded \n
> >> in
> >> the signature checking par
On Thu, May 19, 2016 at 08:44:59AM -0600, Jan Beulich wrote:
> >>> On 19.05.16 at 16:34, wrote:
> > Currently we bump the shared library names just before the release, so ATM
> > xen-unstable is still using the library names from the 4.6 release. This is
> > an issue if someone wants to install
Sorry, re-sending the message with a proper subject line:
Hello,
Currently we bump the shared library names just before the release, so ATM
xen-unstable is still using the library names from the 4.6 release. This is
an issue if someone wants to install both Xen 4.6 and xen-unstable in the
same
On May 19, 2016 5:15 PM, Jan Beulich wrote:
> >>> On 19.05.16 at 10:30, wrote:
> > On April 28, 2016 11:13 PM, Jan Beulich wrote:
> >> >>> On 25.04.16 at 10:40, wrote:
> >> > With other patches also in place, still not work.
> >> > Jianzhong has been left and Quan will take over the task.
> >>
>>> On 19.05.16 at 15:58, wrote:
> Case 1: Dom0 is driver domain:
> There is a Ducati firmware which runs on dedicated M4 core and decodes
> video. This firmware uses hardcoded physical addresses for graphics
> buffers. Those addresses should be inside address-space of the driver
> domain (Dom0).
flight 94568 linux-3.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94568/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
build-i386-rumpuserxen6 xen-buildfail like 94027
build-amd64-rumpuserxen 6
>>> On 19.05.16 at 16:34, wrote:
> Currently we bump the shared library names just before the release, so ATM
> xen-unstable is still using the library names from the 4.6 release. This is
> an issue if someone wants to install both Xen 4.6 and xen-unstable in the
> same box (unless you use a di
On 19/05/16 15:36, Konrad Rzeszutek Wilk wrote:
> On Thu, May 19, 2016 at 03:29:45PM +0100, Andrew Cooper wrote:
>> Pandoc (version 1.12.4.2 from Debian Jessie) complains at the embedded \n in
>> the signature checking paragraph.
>>
>> /usr/bin/pandoc --number-sections --toc --standalone misc/xsp
From: Pavlo Suikov
Signed-off-by: Pavlo Suikov
Signed-off-by: Glib Golubytskyi
Signed-off-by: Iurii Konovalenko
Signed-off-by: Iurii Mykhalskyi
---
tools/libxl/libxl.c | 290 +++
tools/libxl/libxl.h | 18 +++
tools/libxl/libx
This patches introduce set of pv drivers interfaces.
Drivers interfaces list:
- PV RTC - real-time clock
- PV TTY - interface for pv version for device controlled by
via tty (e.g. GPS)
- PV Audio - sound interface virtualization
- PV DRM - direct rengering manager virtualization
- PV RPMSG
PV rtc device interface is implemented in libxl and xl with
full support for device control. No JSON parser for domain
configuration yet.
Signed-off-by: Iurii Mykhalskyi
Signed-off-by: Glib Golubytskyi
Signed-off-by: Iurii Konovalenko
---
tools/libxl/libxl.c | 287
From: Pavlo Suikov
Signed-off-by: Pavlo Suikov
Signed-off-by: Iurii Konovalenko
Signed-off-by: Iurii Mykhalskyi
---
tools/libxl/libxl.c | 282 +++
tools/libxl/libxl.h | 17 +++
tools/libxl/libxl_create.c | 40 -
From: Pavlo Suikov
Touchscreen events device configuration support. Can be further
extended to support any event device whatsoever.
Signed-off-by: Pavlo Suikov
Signed-off-by: Iurii Konovalenko
Signed-off-by: Iurii Mykhalskyi
---
tools/libxl/libxl.c | 289
On Thu, May 19, 2016 at 03:29:45PM +0100, Andrew Cooper wrote:
> Pandoc (version 1.12.4.2 from Debian Jessie) complains at the embedded \n in
> the signature checking paragraph.
>
> /usr/bin/pandoc --number-sections --toc --standalone misc/xsplice.markdown
> --output pdf/misc/xsplice.pdf
>
From: Pavlo Suikov
PV Audio device interface is implemented in libxl and xl with
full support for device control
Signed-off-by: Pavlo Suikov
Signed-off-by: Glib Golubytskyi
Signed-off-by: Iurii Konovalenko
---
tools/libxl/libxl.c | 351 ++-
to
PV tty device interface is implemented in libxl and xl with
full support for device control. No JSON parser for domain
configuration yet.
Signed-off-by: Iurii Mykhalskyi
Signed-off-by: Iurii Konovalenko
---
tools/libxl/libxl.c | 282 +++
tools/li
Hello Oleksandr,
On 19/05/16 14:58, Oleksandr Dmytryshyn wrote:
Why would a user want to allocate DOM0 RAM bank to a specific address?
If I understand correctly your patch, DOM0 will only able to allocate one bank
of the given size at the specific address. You also add this possibility for
gu
, Ian Jackson , Jan
Beulich , Konrad Rzeszutek Wilk ,
Stefano Stabellini , Tim Deegan , Wei
Liu
Bcc:
Subject: Bump library names just after branching
Reply-To:
Hello,
Currently we bump the shared library names just before the release, so ATM
xen-unstable is still using the library names fr
Pandoc (version 1.12.4.2 from Debian Jessie) complains at the embedded \n in
the signature checking paragraph.
/usr/bin/pandoc --number-sections --toc --standalone misc/xsplice.markdown
--output pdf/misc/xsplice.pdf
! Undefined control sequence.
l.1085 appended\textasciitilde{}\n
Surrou
On Thu, May 19, 2016 at 11:29:32AM +1000, Steven Haigh wrote:
> On 2016-05-09 14:22, Steven Haigh wrote:
> > On 2016-05-05 15:52, Steven Haigh wrote:
> > > On 2016-05-05 12:32, Steven Haigh wrote:
> > > > Overview
> > > >
> > > > If you're using iSCSI, you can mount a target by multiple Dom0
> > >
Multi-target non-pattern rules and Multi-target pattern rules behave rather
differently. From `Pattern Intro':
Pattern rules may have more than one target. Unlike normal rules, this does
not act as many different rules with the same prerequisites and commands.
If a pattern rule has multipl
During review of the migration feature doc, some changes were made which
should have been reflected in the template.
Signed-off-by: Andrew Cooper
---
CC: Ian Jackson
CC: Wei Liu
---
docs/features/template.pandoc | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/d
On 19/05/16 12:48, Stefano Stabellini wrote:
> On Thu, 19 May 2016, Jan Beulich wrote:
> On 19.05.16 at 12:40, wrote:
>>> On Thu, 19 May 2016, Juergen Gross wrote:
> Alternatively, the easiest way will probably be to add a new VMASSIST,
> which allows the guest to opt into the new beha
> Why would a user want to allocate DOM0 RAM bank to a specific address?
>
> If I understand correctly your patch, DOM0 will only able to allocate one
> bank of the given size at the specific address. You also add this possibility
> for guest domain (see patch #4) and try to control where the gue
On Thu, May 19, 2016 at 12:21:57PM +0200, Dario Faggioli wrote:
> Since, AFAIUI, you're interested in non-Linux guests' perspective, I'm
> adding Roger (and avoiding trimming, for his benefit), who can tell us
> what he thinks of this all, from the FreeBSD point of view.
Thanks, AFAIK vcpu_runstat
On 19/05/16 15:26, Juergen Gross wrote:
> The pv_time_ops structure contains a function pointer for the
> "steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86
> uses its own mechanism to account for the "stolen" time a thread wasn't
> able to run due to hypervisor scheduling.
>
Hello,
On 18/05/16 17:32, Andrii Anisov wrote:
From: Iurii Konovalenko
Move Xen to the end of physical memory
Can you explain why? As Ian campbell said on the previous version sent
last year [1], Xen itself (i.e .text, .bss and .data, not the xenheap
itself) is at most 2MB. Are your constr
On 19/05/16 14:46, Roger Pau Monne wrote:
> Since it might be included from different paths that have different levels
> of nestedness. Also all makefiles that include common.mk already define ROOT
> on their own.
>
> Signed-off-by: Roger Pau Monné
I really need to work on improving the build sys
Add a simple script that can list the tests relevant to the current
environment and run them. In it's current form it's functionality is quite
limited, and consists in one of this two options:
- list: list tests relevant to the current environment. This information is
fetched from each test te
Hello,
This series contains a bugfix for the build infrastructure and a basic
launcher for XTF. Patches can also be found in the following git repo:
git://xenbits.xen.org/people/royger/xen-test-framework.git launcher_v1
Thanks, Roger.
___
Xen-devel m
Since it might be included from different paths that have different levels
of nestedness. Also all makefiles that include common.mk already define ROOT
on their own.
Signed-off-by: Roger Pau Monné
---
Cc: andrew.coop...@citrix.com
---
build/common.mk | 1 -
1 file changed, 1 deletion(-)
diff --
On 05/19/2016 09:26 AM, Juergen Gross wrote:
> The pv_time_ops structure contains a function pointer for the
> "steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86
> uses its own mechanism to account for the "stolen" time a thread wasn't
> able to run due to hypervisor scheduling
Hello,
On 18/05/16 17:32, Andrii Anisov wrote:
From: Oleksandr Dmytryshyn
This setting is used to adjust starting memory address allocated
for kernel Dom0. To use 'rambase_pfn' setting just add for example
'dom0_rambase_pfn=0x8' to the hypervisor command line. Note that
'dom0_rambase_pfn'
flight 94579 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94579/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 12
The pv_time_ops structure contains a function pointer for the
"steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86
uses its own mechanism to account for the "stolen" time a thread wasn't
able to run due to hypervisor scheduling.
Add support in Xen arch independent time handling
On 19/05/16 07:43, Juergen Gross wrote:
> The pv_time_ops structure contains a function pointer for the
> "steal_clock" functionality used only by KVM and Xen on ARM. Xen on x86
> uses its own mechanism to account for the "stolen" time a thread wasn't
> able to run due to hypervisor scheduling.
>
flight 94563 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94563/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-nested-intel 9 debian-hvm-install fail REGR. vs. 94487
Regressions which ar
>>> On 19.05.16 at 14:26, wrote:
> On 19/05/16 10:41, Jan Beulich wrote:
> On 18.05.16 at 18:32, wrote:
>>> --- a/xen/arch/arm/domain_build.c
>>> +++ b/xen/arch/arm/domain_build.c
>>> @@ -27,6 +27,9 @@
>>> static unsigned int __initdata opt_dom0_max_vcpus;
>>> integer_param("dom0_max_vcpu
This run is configured for baseline tests only.
flight 44433 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44433/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 81c1460695f783a3f91431b2babea623556a7f5d
baseline version:
ovm
This run is configured for baseline tests only.
flight 44431 xen-4.6-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44431/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-xsm
Hi Jan,
On 19/05/16 10:41, Jan Beulich wrote:
On 18.05.16 at 18:32, wrote:
--- a/xen/arch/arm/domain_build.c
+++ b/xen/arch/arm/domain_build.c
@@ -27,6 +27,9 @@
static unsigned int __initdata opt_dom0_max_vcpus;
integer_param("dom0_max_vcpus", opt_dom0_max_vcpus);
+static u64 __initdata o
Hello,
On 18/05/16 17:32, Andrii Anisov wrote:
From: Andrii Tseglytskyi
Patch allows reassigning of hardware interrupts from dom0 to
other guest domain.
Can you explain why route_irq_to_guest should be able to cope with
reassigning an IRQ rather than having dom0 calling
XEN_DOMCTL_unbind_
On Thu, May 19, 2016 at 11:29:32AM +1000, Steven Haigh wrote:
> On 2016-05-09 14:22, Steven Haigh wrote:
> >On 2016-05-05 15:52, Steven Haigh wrote:
> >>On 2016-05-05 12:32, Steven Haigh wrote:
> >>>Overview
> >>>
> >>>If you're using iSCSI, you can mount a target by multiple Dom0
> >>>machines on
Hello,
On 18/05/16 17:32, Andrii Anisov wrote:
From: Oleksandr Tyshchenko
In case of missing required property in cfg file
the default value (0x4) should be used.
The memory layout for the guest is static and may change between
version. By allowing the user to specify the base of the RAM
>>> On 19.05.16 at 13:26, wrote:
> On May 19, 2016 2:13 PM, Jan Beulich wrote:
>> >>> "Xu, Quan" 05/19/16 3:35 AM >>>
>> >On May 19, 2016 8:33 AM, Tian, Kevin wrote:
>> >> A single default value for both IOMMU-side and device-side is anyway
>> >> not optimal. What about introducing a new knob e
On Wed, May 18, 2016 at 07:32:40PM +0300, Andrii Anisov wrote:
> From: Iurii Mykhalskyi
>
> This option enables separate memory allocation in
> low & over 4GB address space.
> With this option enabled in domain config files
> "memory" parameter are used to specify domain low memory
> "memory_high
On Wed, May 18, 2016 at 07:32:35PM +0300, Andrii Anisov wrote:
> From: Viktor Kleinik
>
> During domain destroy we should change its state from "alive"
> to "dying" to prevent reboot because of watchdog timeout.
>
> Signed-off-by: Viktor Kleinik
> ---
> tools/libxl/libxl.c | 4
> 1 file c
On Wed, May 18, 2016 at 07:32:27PM +0300, Andrii Anisov wrote:
> From: Oleksandr Tyshchenko
>
> In case of missing required property in cfg file
> the default value (0x4) should be used.
Assuming this is absolutely needed (whether it is the case I don't
know, I will leave that to ARM maintai
On Wed, May 18, 2016 at 07:32:29PM +0300, Andrii Anisov wrote:
> From: Viktor Kleinik
>
> We need to parse config data during domain reboot
> to get correct I/O memory regions for mapping.
>
> Signed-off-by: Viktor Kleinik
> ---
> tools/libxl/xl_cmdimpl.c | 15 +++
> 1 file changed
On Wed, May 18, 2016 at 07:32:24PM +0300, Andrii Anisov wrote:
> This patch makes virtual disks helper scripts be functional
> in busybox environment. Actually we call sh insteand of bash and
> rewrite loop with counter to be properly parsed by ash.
>
> Signed-off-by: Andrii Anisov
> Signed-off-b
On Wed, May 18, 2016 at 07:32:30PM +0300, Andrii Anisov wrote:
> From: Viktor Kleinik
>
> This change allows watchdog daemon to work thru watchdog device
> on the file system.
>
> Signed-off-by: Viktor Kleinik
The commit message is not clear enough as to why you want to delete a
bunch of code.
On Wed, May 18, 2016 at 07:32:32PM +0300, Andrii Anisov wrote:
> From: Oleksandr Dmytryshyn
>
> Signed-off-by: Oleksandr Dmytryshyn
> Signed-off-by: Iurii Konovalenko
> ---
> tools/xenstat/Makefile | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/tools/xenstat/Makef
On Wed, May 18, 2016 at 07:32:31PM +0300, Andrii Anisov wrote:
> From: Viktor Kleinik
>
> Signed-off-by: Viktor Kleinik
I have a feeling this can probably be squashed into previous patch. But
please don't squash this yet, let's start with better commit message.
Wei.
__
On May 19, 2016 2:13 PM, Jan Beulich wrote:
> >>> "Xu, Quan" 05/19/16 3:35 AM >>>
> >On May 19, 2016 8:33 AM, Tian, Kevin wrote:
> >> A single default value for both IOMMU-side and device-side is anyway
> >> not optimal. What about introducing a new knob e.g.
> >> vtd_qi_device_timeout specifica
Hello,
On 18/05/16 17:32, Andrii Anisov wrote:
From: Andrii Tseglytskyi
This is done to allow possibility of having 1 to 1 memory mapping chunks
with size 1/128/256/512 Mb what can sagnificantly decrease time of memory
significantly
allocation and fragmentation for 1-to-1 mapped domains.
On Thu, May 19, 2016 at 10:11:35AM +0200, Dario Faggioli wrote:
> or (even in cases where there is no race, e.g., outside
> of Credit2) avoid using a time sample which may be rather
> old, and hence stale.
>
> In fact, we should only sample NOW() from _inside_
> the critical region within which th
Hello,
On 18/05/16 20:17, Meng Xu wrote:
On Wed, May 18, 2016 at 12:32 PM, Andrii Anisov
wrote:
This series RFC patches from the currently ongoing production project.
This patch series presents changes needed to fit the system into
customer requirements as well as workaround limitations of the
On 18/05/2016 21:34, Peter Zijlstra wrote:
>> I don't know of any enterprise distro that is shipping anything
>> > more modern than 4.1?
> RHEL 7-- v3.10
> SLES 12 -- v3.12
> Debian Jessie -- v3.16
> Ubuntu 16.04 LTS -- v4.4
>
> But wait
On Thu, 19 May 2016, Jan Beulich wrote:
> >>> On 19.05.16 at 12:40, wrote:
> > On Thu, 19 May 2016, Juergen Gross wrote:
> >> > Alternatively, the easiest way will probably be to add a new VMASSIST,
> >> > which allows the guest to opt into the new behaviour.
> >>
> >> Aah, nice. Yes, this seems
>>> On 19.05.16 at 12:40, wrote:
> On Thu, 19 May 2016, Juergen Gross wrote:
>> > Alternatively, the easiest way will probably be to add a new VMASSIST,
>> > which allows the guest to opt into the new behaviour.
>>
>> Aah, nice. Yes, this seems to be a sensible option.
>
> If you are referring t
On Thu, 19 May 2016, Julien Grall wrote:
> Hi Peng,
>
> On 19/05/16 10:22, Peng Fan wrote:
> > CPU0 boots up secondary CPUs one by one. Before booting
> > one secondary CPU, CPU0 will assign hwid to smp_up_cpu
> > and flush cache. After the secondary CPU boots up,
>
> NIT: s/the/a/
>
> > CPU0 wi
On Thu, 19 May 2016, Juergen Gross wrote:
> > Alternatively, the easiest way will probably be to add a new VMASSIST,
> > which allows the guest to opt into the new behaviour.
>
> Aah, nice. Yes, this seems to be a sensible option.
If you are referring to VM_ASSIST, it is only available on x86. I
Hi Peng,
On 19/05/16 10:22, Peng Fan wrote:
CPU0 boots up secondary CPUs one by one. Before booting
one secondary CPU, CPU0 will assign hwid to smp_up_cpu
and flush cache. After the secondary CPU boots up,
NIT: s/the/a/
CPU0 will assign MPIDR_INVALID to smp_up_cpu and flush
cache.
There is
Since, AFAIUI, you're interested in non-Linux guests' perspective, I'm
adding Roger (and avoiding trimming, for his benefit), who can tell us
what he thinks of this all, from the FreeBSD point of view.
On Thu, May 19, 2016 at 10:49 AM, Juergen Gross wrote:
> On 19/05/16 10:09, Andrew Cooper wrote
flight 94573 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94573/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-pvops 3 host-install(3) broken REG
1 - 100 of 128 matches
Mail list logo
