flight 91860 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91860/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 91479
build-i386-libvirt
>>> Konrad Rzeszutek Wilk 04/18/16 7:55 AM >>>
>> >+ if ( delta > elf->len )
>> >+ {
>> >+ dprintk(XENLOG_ERR, XSPLICE "%s: Section table is past end of payload!\n",
>> >+ elf->name);
>> >+ return -EINVAL;
>> >+ }
>> >+
>> >+ for ( i = 1; i < elf->hdr->e_shnum; i++ )
>> >+ {
>> >+ delta = elf->hdr
>>> Konrad Rzeszutek Wilk 04/14/16 12:04 AM >>>
>--- a/xen/arch/x86/Makefile
>+++ b/xen/arch/x86/Makefile
>@@ -64,6 +64,7 @@ obj-y += vm_event.o
>obj-y += xstate.o
>
>obj-$(crash_debug) += gdbstub.o
>+obj-$(CONFIG_XSPLICE) += xsplice.o
This should be added in the main section, somewhere ahea
. snip..
> >+static int elf_resolve_sections(struct xsplice_elf *elf, const void *data)
> >+{
> >+ struct xsplice_elf_sec *sec;
> >+ unsigned int i;
> >+ Elf_Off delta;
> >+ int rc;
> >+
> >+ /* xsplice_elf_load sanity checked e_shnum. */
> >+ sec = xmalloc_array(struct xsplice_elf_sec, elf->hdr->e
This run is configured for baseline tests only.
flight 44341 linux-3.18 real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44341/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm 17
On 2016/4/12 11:35, Zhenzhong Duan wrote:
On 2016/4/11 19:27, Wei Liu wrote:
On Mon, Apr 11, 2016 at 09:42:57AM +0800, Zhenzhong Duan wrote:
It's tool's duty to pass a correct cpumap to XEN. On a host with
less than
64
CPUS, it just shows below error.
[root@localhost /]# xm vcpu-pin 3 all all
hi
this may help you。。。
hvm_vcpu_initialise
- .vcpu_initialise = vmx_vcpu_initialise,
- vmx_create_vmcs
- construct_vmcs
- if ( paging_mode_hap(d) )
{
struct p2m_domain *p2m = p2m_get_hostp2m(d);
struct ept_data *ept = &p2m->ept;
flight 91836 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91836/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
test-amd64-i386-xl-qemuu-ovm
On April 15, 2016 10:03pm, wrote:
> On 31/03/16 10:06, Xu, Quan wrote:
> > All,
> >
> > Here is a summary of my investigation of the abstract model:
> >
> > Below policies are adopted when deciding whether to rollback a callchain:
> >
> > 1. Domain will be crashed immediately within iommu_{,un}map
flight 91779 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91779/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 59254
test-amd64-amd64-xl-x
flight 91786 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91786/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
test-amd64-i386-xl-qemuu-ovm
On Fri, Apr 15, 2016 at 8:43 AM, Shannon Zhao wrote:
> Hi Rafael，
>
> Could you please give your comments on this patch? Thanks in advanced!
I was traveling last week, sorry for the slow response.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http
On Thu, Apr 7, 2016 at 2:03 PM, Shannon Zhao wrote:
> From: Shannon Zhao
>
> ACPI 6.0 introduces a new table STAO to list the devices which are used
> by Xen and can't be used by Dom0. On Xen virtual platforms, the physical
> UART is used by Xen. So here it hides UART from Dom0.
>
> CC: "Rafael J
Fix errors like:
/local/work/xen.git/dist/install/usr/local/include/libxl_uuid.h:59:1: error:
'static' is not at beginning of declaration [-Werror=old-style-declaration]
void static inline libxl_uuid_copy_0x040400(libxl_uuid *dst,
^
/local/work/xen.git/dist/install/usr/local/include/libxl_uuid.
branch xen-unstable
xenbranch xen-unstable
job build-i386-libvirt
testid libvirt-build
Tree: libvirt git://libvirt.org/libvirt.git
Tree: libvirt_gnulib git://git.sv.gnu.org/gnulib.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen
flight 91757 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91757/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail in 91675 pass in 91757
test-armhf-armhf-xl-rtds 16 gues
>>> Konrad Rzeszutek Wilk 04/14/16 12:03 AM >>>
>+static int elf_verify_strtab(const struct xsplice_elf_sec *sec)
>+{
>+ const Elf_Shdr *s;
>+ const uint8_t *contents;
Considering it's a string table, perhaps better const char *?
>+ s = sec->sec;
>+
>+ if ( s->sh_type != SHT_STRTAB )
>+ return -
flight 91745 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91745/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemuu-winxpsp3 3 host-install(3) broken pass in 91660
test-armhf-armhf-xl-xsm 15 gu
>>> Konrad Rzeszutek Wilk 04/14/16 12:03 AM >>>
>Signed-off-by: Konrad Rzeszutek Wilk
>Suggested-by: Jan Beulich
>Acked-by: Julien Grall [ARM]
>Reviewed-by: Andrew Cooper
Is that really the case? I think it was Andrew who suggested to not expose a
second variant of vfree(), as the address typ
>>> Roger Pau Monne 04/15/16 8:27 PM >>>
>Previously HOSTCC was always hardcoded to gcc
So what is the goal here? Be able to build on a gcc-free system? Or else, how
does it matter what compiler build elements get built with?
>--- a/Config.mk
>+++ b/Config.mk
>@@ -36,7 +36,6 @@ CONFIG_$(XEN_OS)
On Sun, Apr 17, 2016 at 1:15 PM, Razvan Cojocaru
wrote:
> Previously, subscribing to MSR write events was an all-or-none
> approach, with special cases for introspection MSR-s. This patch
> allows the vm_event consumer to specify exactly what MSR-s it is
> interested in, and as a side-effect gets
Previously, subscribing to MSR write events was an all-or-none
approach, with special cases for introspection MSR-s. This patch
allows the vm_event consumer to specify exactly what MSR-s it is
interested in, and as a side-effect gets rid of the
vmx_introspection_force_enabled_msrs[] special case.
T
Hi,
I know that scheduling is done via two main functions and their effective
interaction:
one 'schedule()' in schedule.c and another 'do_schedule(...)', which is
specific for every scheduling policy.
my question is that (although it may seem clear and very common for kernel
developers, but not
flight 91725 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91725/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-xsm 15 guest-localmigratefail REGR. vs. 60684
build-i386
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-xl-qemut-win7-amd64
testid leak-check/check
Tree: linux
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/qemu-x
flight 91727 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91727/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
test-amd64-i386-xl-qemuu-ovm
Please don't top post.
On Sun, Apr 17, 2016 at 06:28:15PM +0430, Maryam Masoudian wrote:
> Well, yes memshr is at tools/memshr .
> Then , after modifying this c file, should I compile Xen from scratch?
No, you only need to compile the tools -- or, just that tool.
> And is the sharing feature ena
Well, yes memshr is at tools/memshr .
Then , after modifying this c file, should I compile Xen from scratch?
And is the sharing feature enabled by default in Xen 4.6 ? If not, how to
enable it?
On Sun, Apr 17, 2016 at 4:45 PM, Wei Liu wrote:
> On Sun, Apr 17, 2016 at 03:55:00PM +0430, Maryam Ma
flight 91700 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91700/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 59254
test-amd64-amd64-xl-x
On Sun, Apr 17, 2016 at 10:28:24AM +, Sunguodong wrote:
> Hi all,
>
> I have a question about oxenstored, please help if someone knows.
> Oxenstored saves store information to "/var/run/xenstored/db" when it quits,
> but the contents is reversed.
> For example,
> before restart oxenstored, t
On Sun, Apr 17, 2016 at 03:55:00PM +0430, Maryam Masoudian wrote:
> Hi,
>
> I have some questions about memory de-duplication in xen.
> Firstly, I want to know if this feature is available in Xen .
> If it is, how can I enable it in Xen 4.6 HVM mode.
>
> Also, if I want to do some logging or othe
Hi,
I have some questions about memory de-duplication in xen.
Firstly, I want to know if this feature is available in Xen .
If it is, how can I enable it in Xen 4.6 HVM mode.
Also, if I want to do some logging or other action whenever a COW happens
on shared memory, where should I add my codes? (
Hi all,
I have a question about oxenstored, please help if someone knows.
Oxenstored saves store information to "/var/run/xenstored/db" when it quits,
but the contents is reversed.
For example,
before restart oxenstored, the output of 'xenstore-ls -f' is:
...
/local/domain/0/memory/target = "838
flight 91751 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91751/
Perfect :-)
All tests in this flight passed
version targeted for testing:
xen f3a7ca02400d1c416e97451b4aebfaf608fc8192
baseline version:
xen ac703c285a4fbfcb85
This run is configured for baseline tests only.
flight 44340 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44340/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-qemuu-nested-intel 13 xen-boot/l1
>>> Roger Pau Monne 04/15/16 8:29 PM >>>
>I've also noticed that Xen always sets "-no-integrated-as" when using clang,
>because previous versions (<3.8.0) didn't support .code16/.code32/.code64
>in inline asm. This is solved at least in version 3.8.0 (haven't tested
>older versions). The problem n
flight 91722 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91722/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 91479
build-i386-libvirt
flight 91675 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91675/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-win7-amd64 20 leak-check/check fail in 91420 REGR.
vs. 86513
Tests which ar
>>> Andrew Cooper 04/15/16 7:12 PM >>>
>On 08/04/16 13:10, Jan Beulich wrote:
>> http://lists.xen.org/archives/html/xen-devel/2016-03/msg02167.html
>> (with the 1st patch having gone in already)
>
>Apologies for the delay on this. I now have results in.
>
>The 64bit performance hit is within the
>>> Konrad Rzeszutek Wilk 04/15/16 4:29 AM >>>
>On Thu, Apr 14, 2016 at 10:36:46AM -0600, Jan Beulich wrote:
>> >>> Konrad Rzeszutek Wilk 04/14/16 12:05 AM >>>
>> > @@ -460,6 +461,11 @@ long do_sysctl(XEN_GUEST_HANDLE_PARAM(xen_sysctl_t)
>> > u_sysctl)
>> > ret = tmem_control(&op->u.tmem
>>> Konrad Rzeszutek Wilk 04/15/16 2:55 AM >>>
>On Thu, Apr 14, 2016 at 09:17:14AM -0600, Jan Beulich wrote:
>> >>> Andrew Cooper 04/14/16 5:14 PM >>>
>> >On 14/04/16 15:26, Konrad Rzeszutek Wilk wrote:
>> >> @@ -312,8 +307,8 @@ struct xsplice_patch_func {
>> >> };
>> >>
>> >>
>> >> -The s
flight 91660 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/91660/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
build-amd64-rumpuserxen 6 xen-buildfail like 91545
build-i386-rumpuserxen
>>> Ben Sanda 04/14/16 10:03 PM >>>
>>> +void put_pg_owner(struct domain *pg_owner) {
>>> +rcu_unlock_domain(pg_owner);
>>> +}
> I cannot see why this then can't just become an inline function.
>
>I investigated this but making put_pg_owner() static inline creates a
>circular dependency on rcu
>>> George Dunlap 04/15/16 1:23 PM >>>
>On Thu, Apr 14, 2016 at 6:01 PM, Jan Beulich wrote:
>>>Sure, mistakes happen; but I hope it's not being to controversial to
>>>say that in general, the procedure should be arranged such that the
>>>person who makes the mistake is the one who has to do deal
>>> Ian Jackson 04/14/16 8:12 PM >>>
>Jan Beulich writes ("Re: [Xen-devel] REST MAINTAINERS feedback requested Was:
>> And btw., considering that Konrad has already posted a revert patch,
>> and I have ack-ed that one, this could now go in right away (and the
>> discussion could either be settled
45 matches
Mail list logo
