flight 105921 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105921/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt-xsm 13 saverestore-support-checkfail like 105902
test-armhf-armhf-libvirt 13
This run is configured for baseline tests only.
flight 68582 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68582/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf c035e37335ae43229d7e68de74a65f2c01ebc0af
baseline v
On 01/30/17 15:33 +, Julien Grall wrote:
> This email only tracks big items for xen.git tree. Please reply for items you
> woulk like to see in 4.9 so that people have an idea what is going on and
> prioritise accordingly.
>
> You're welcome to provide description and use cases of the feature
On 17/02/17 20:47, Dmitry Torokhov wrote:
> On Mon, Jan 30, 2017 at 01:27:29PM +0200, Oleksandr Andrushchenko wrote:
>> On 01/30/2017 01:23 PM, Juergen Gross wrote:
>>> On 27/01/17 17:10, Dmitry Torokhov wrote:
On January 27, 2017 12:31:19 AM PST, Juergen Gross wrote:
> On 27/01/17 09:26,
flight 105920 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105920/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf c035e37335ae43229d7e68de74a65f2c01ebc0af
baseline version:
ovmf eb470e05a3c7c251cfa50
>Feb 10, 2017 02:00，"Roger Pau Monné" wrote:
>
>On Thu, Feb 09, 2017 at 07:58:56AM -0700, Jan Beulich wrote:
>> >>> On 09.02.17 at 15:46, wrote:
>> > BTW -- I think that fix should not be conflicting with your debug change,
>> > right?
>>
>> Yes - ideally you'd keep that one in place along with a
On 02/17/17 03:21 -0700, Jan Beulich wrote:
> >>> On 17.02.17 at 07:39, wrote:
> > --- a/xen/arch/x86/cpu/mcheck/mcaction.c
> > +++ b/xen/arch/x86/cpu/mcheck/mcaction.c
> > @@ -88,21 +88,21 @@ mc_memerr_dhandler(struct mca_binfo *binfo,
> > goto vmce_failed;
> >
On 02/17/17 03:08 -0700, Jan Beulich wrote:
> >>> On 17.02.17 at 07:39, wrote:
> > Use uint32_t rather than int to align to the type of
> > xen_mc_physcpuinfo.ncpus.
>
> I'm not sure about policies in the tool stack, but in the hypervisor I
> would request to use unsigned int instead of fixed wid
On 02/17/17 03:07 -0700, Jan Beulich wrote:
> >>> On 17.02.17 at 07:39, wrote:
> > @@ -804,7 +800,7 @@ static void mcinfo_clear(struct mc_info *mi)
> > x86_mcinfo_nentries(mi) = 0;
> > }
> >
> > -void *x86_mcinfo_reserve(struct mc_info *mi, int size)
> > +void *x86_mcinfo_reserve(struct mc
On 02/17/17 03:01 -0700, Jan Beulich wrote:
> >>> On 17.02.17 at 07:39, wrote:
> > Implementations of these two functions are effectively the same, so
> > unify them by a common intel_default_mce_handler().
>
> Them being the same right now may also be an issue with the
> earlier authors never ha
On 02/17/17 02:55 -0700, Jan Beulich wrote:
> >>> On 17.02.17 at 07:39, wrote:
> > Signed-off-by: Haozhong Zhang
>
> Not sure here, I can't imagine the function being here without
> reason, even if the plans perhaps never got carried out. Could
> you please identify in the commit message here wh
On 02/17/17 02:58 -0700, Jan Beulich wrote:
On 17.02.17 at 07:39, wrote:
The second loop that gets MSR_IA32_MCG_R8 to MSR_IA32_MCG_R15 was
surrounded by '#ifdef __X86_64__ ... #endif' and had to be seperated
from the first loop that gets MSR_IA32_MCG_EAX to MSR_IA32_MCG_MISC.
Because Xen had dr
On 20/02/2017 00:26, Andrew Cooper wrote:
> On 20/02/2017 00:20, Andrew Cooper wrote:
>> On 19/02/2017 23:20, osstest service owner wrote:
>>> branch xen-unstable
>>> xenbranch xen-unstable
>>> job test-amd64-amd64-xl-pvh-intel
>>> testid guest-start
>>>
>>> Tree: linux
>>> git://git.kernel.org/pu
On 20/02/2017 00:20, Andrew Cooper wrote:
> On 19/02/2017 23:20, osstest service owner wrote:
>> branch xen-unstable
>> xenbranch xen-unstable
>> job test-amd64-amd64-xl-pvh-intel
>> testid guest-start
>>
>> Tree: linux
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>> Tre
On 19/02/2017 23:20, osstest service owner wrote:
> branch xen-unstable
> xenbranch xen-unstable
> job test-amd64-amd64-xl-pvh-intel
> testid guest-start
>
> Tree: linux
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-xl-pvh-intel
testid guest-start
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditiona
flight 105905 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105905/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 59254
test-amd64-amd64-xl
Hi Stefano,
I have CCed another ARM person who has more knowledge than me on
scheduling/power.
On 02/17/2017 10:50 PM, Stefano Stabellini wrote:
CC'ing xen-devel, I forgot on the original patch
On Fri, 17 Feb 2017, Julien Grall wrote:
Hi Stefano,
On 02/16/2017 11:04 PM, Stefano Stabellini
Hi Dario,
On 02/18/2017 01:47 AM, Dario Faggioli wrote:
On Fri, 2017-02-17 at 14:50 -0800, Stefano Stabellini wrote:
On Fri, 17 Feb 2017, Julien Grall wrote:
Please explain in which context this will be beneficial. My gut
feeling is
only will make performance worst if a multiple vCPU of the sa
Hi Stefano,
On 02/18/2017 01:29 AM, Stefano Stabellini wrote:
The default dom0_mem is 128M which is not sufficient to boot a Ubuntu
based Dom0. It is not clear what a better default value could be.
Instead, loadly warn the user when dom0_mem is unspecified and wait 3
secs. Then use 512M.
Signe
flight 105901 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105901/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 59254
test-armhf-armhf-xl
flight 105903 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105903/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 75da1b150e646bb9aaa26c5b2452f0c3e782d302
baseline version:
xen bdbc
flight 105900 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105900/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-rtds 6 xen-boot fail in 105896 pass in 105900
test-amd64-i386-pair21 guest
flight 105902 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105902/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt-xsm 13 saverestore-support-checkfail like 105895
test-armhf-armhf-libvirt 13
24 matches
Mail list logo
