Re: [Xen-devel] [xen-unstable test] 104131: regressions - FAIL

On Mon, Jan 16, 2017 at 06:27:23AM +, Xuquan (Quan Xu) wrote: >On January 16, 2017 1:26 PM, Tian, Kevin wrote: >>> From: Jan Beulich [mailto:jbeul...@suse.com] >>> Sent: Thursday, January 12, 2017 8:26 PM >>> >>> >>> On 12.01.17 at 13:15, wrote: >>> > On 12/01/17

Re: [Xen-devel] [xen-unstable test] 104131: regressions - FAIL

On January 16, 2017 1:26 PM, Tian, Kevin wrote: >> From: Jan Beulich [mailto:jbeul...@suse.com] >> Sent: Thursday, January 12, 2017 8:26 PM >> >> >>> On 12.01.17 at 13:15, wrote: >> > On 12/01/17 12:07, Xuquan (Quan Xu) wrote: >> >> On January 12, 2017 5:14 PM, Andrew

Re: [Xen-devel] [PATCH v2] xen-netfront: Fix Rx stall during network stress and OOM

On 13/01/17 18:55, Remanan Pillai wrote: > From: Vineeth Remanan Pillai > > During an OOM scenario, request slots could not be created as skb > allocation fails. So the netback cannot pass in packets and netfront > wrongly assumes that there is no more work to be done and it

Re: [Xen-devel] [PATCH v2] partially revert "xen: Remove event channel notification through Xen PCI platform device"

On 13/01/17 19:44, Boris Ostrovsky wrote: > On 01/13/2017 01:26 PM, Stefano Stabellini wrote: >> On Fri, 13 Jan 2017, Boris Ostrovsky wrote: >>> On 01/12/2017 04:39 PM, Stefano Stabellini wrote: The following commit: commit 72a9b186292d98494f26cfd24a1621796209 Author:

Re: [Xen-devel] [xen-unstable test] 104131: regressions - FAIL

> From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Thursday, January 12, 2017 8:26 PM > > >>> On 12.01.17 at 13:15, wrote: > > On 12/01/17 12:07, Xuquan (Quan Xu) wrote: > >> On January 12, 2017 5:14 PM, Andrew Cooper wrote: > >>> On 12/01/2017 06:46, osstest

Re: [Xen-devel] [PATCH v2 2/2] x86/cpuid: Move x86_vendor from arch_domain to cpuid_policy

> From: Andrew Cooper [mailto:andrew.coop...@citrix.com] > Sent: Friday, January 13, 2017 9:56 PM > > No functional change. > > Signed-off-by: Andrew Cooper Reviewed-by: Kevin Tian ___ Xen-devel

Re: [Xen-devel] [PATCH V3] x86/HVM: Introduce struct hvm_pi_ops

> From: Suravee Suthikulpanit [mailto:suravee.suthikulpa...@amd.com] > Sent: Thursday, January 12, 2017 12:47 PM > > The current function pointers in struct vmx_domain for managing hvm > posted interrupt can be used also by SVM AVIC. Therefore, this patch > introduces the struct hvm_pi_ops in the

[Xen-devel] [PATCH v4 2/6] tools: add init.h for tools

Start off with just __ref -- we enalbe you to override, if you do that then you can define your own. The way you'd use this, if you do override, is define your own __ref and then use include_next. Signed-off-by: Luis R. Rodriguez --- tools/include/linux/init.h | 9 +

[Xen-devel] [PATCH v4 4/6] tools: expand export.h with VMLINUX_SYMBOL()

This will be used later by the linker-table userspace sandbox. Signed-off-by: Luis R. Rodriguez --- tools/include/linux/export.h | 22 ++ 1 file changed, 22 insertions(+) diff --git a/tools/include/linux/export.h b/tools/include/linux/export.h index

[Xen-devel] [PATCH v4 3/6] tools: add __used and enable to override

This adds __used, to be used later in the userspace linker-tables sandbox. If any userspace applicaiton wants to override they can add their own definition and then use include_next. This definition should probably suffice for most uses cases though. Signed-off-by: Luis R. Rodriguez

[Xen-devel] [PATCH v7 11/14] kprobes: move kprobe declarations to asm-generic/kprobes.h

Often all is needed is these small helpers, instead of compiler.h or a full kprobes.h. This is important for asm helpers, in fact even some asm/kprobes.h make use of these helpers... instead just keep a generic asm file with helpers useful for asm code with the least amount of clutter as possible.

[Xen-devel] [PATCH v7 12/14] kprobes: port .kprobes.text to section range

kprobe makes use of two custom sections, each custom section is folded into one of the standard Linux sections types as follows, it currently relies on the linker script to fold the custom section onto the respective Linux section: type Linux-section custom section name begin

[Xen-devel] [PATCH v4 5/6] tools: add __section() to compiler.h

This will be used later by the userspace linker table. Signed-off-by: Luis R. Rodriguez --- tools/include/linux/compiler.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/include/linux/compiler.h b/tools/include/linux/compiler.h index 556c991de212..6321265df00a

[Xen-devel] [PATCH v4 0/6] tools: add linker table userspace sandbox

This v4 also addresses some spelling / checkpatch comlplains. The remaining checkpatch complaints are not valid for the code in question. This applies after the series: [PATCH v7 00/14] linux: generalize sections, ranges and linker tables Luis R. Rodriguez (6): tools: add a userspace tools

[Xen-devel] [PATCH v4 1/6] tools: add a userspace tools bug.h

This will be used later by the userspace linker-tables sandbox. As a convenience, include bug.h on kernel.h -- this is not done on upstream kernel.h, however most header files do include bug.h eventually, if we were to only add the ones that need it we'd need to copy a lot of headers to tools for

[Xen-devel] [PATCH v7 07/14] firmware: port built-in section to linker table

This ports built-in firmware to use linker tables, this replaces the custom section solution with a generic solution. This also demos the use of the .rodata linker table. Tested with 0 built-in firmware, 1 and 2 built-in firmwares successfully. v6: rename table macro as suggested by Andy

[Xen-devel] [PATCH v7 10/14] dynamic_debug: port to use linker tables

This removes the custom vmlinux.lds.h hacks and uses the generalized solution for .data entries. There is much more potential for further fine tuning here in the future though. For instance, linker tables enable an extra postfix for order level annotations, this could easily be used as the

[Xen-devel] [PATCH v7 09/14] jump_label: port __jump_table to linker tables

Move the __jump_table from the a custom section solution to a generic solution, this avoiding extra vmlinux.lds.h customizations. This also demos the use of the .data linker table and of the shared asm call push_section_tbl(). Built-in kernel functionality was tested with

[Xen-devel] [PATCH v7 13/14] kprobes: port blacklist kprobes to linker table

kprobe makes use of two sections, the one dealing with the actual kprobes was recently ported using the standard section range API. The blacklist functionality of kprobes is still using a custom section and declaring its custom section using the linker script as follows: type Linux-section

[Xen-devel] [PATCH v7 06/14] firmware/Makefile: force recompilation if makefile changes

If you modify the target asm we currently do not force the recompilation of the firmware files. The target asm is in the firmware/Makefile, peg this file as a dependency to require re-compilation of firmware targets when the asm changes. v3: introduced in this series Signed-off-by: Luis R.

[Xen-devel] [PATCH v7 00/14] linux: generalize sections, ranges and linker tables

This v7 addresses spelling / minor checkpatch complaints, as requested. checkpatch still complains but the remaining complaints are not valid for the code in question. A respective userspace sandbox for the kernel's tools/ follows this series. A branch based on linux-next tag next-20170113 is

[Xen-devel] [PATCH v7 03/14] ranges.h: add helpers to build and identify Linux section ranges

Section ranges are on one of the types of custom sections types used in Linux. This provides a series of helpers for defining them and using them. Most importantly this also enables us to avoid modifying the linker script when we add a new section range. It turns out a lot of custom sections are

[Xen-devel] [PATCH v7 02/14] xtensa: skip adding literal when SORT() is used

When SORT(foo.*) is used the current sed replacements add SORT(foo.literal foo.*), this breaks linking. Avoid adding literals for SORT globs, if needed, these need to be added manually. Signed-off-by: Luis R. Rodriguez --- arch/xtensa/kernel/Makefile | 8 1 file

[Xen-devel] [PATCH v7 01/14] generic-sections: add section core helpers

Linux makes extensive use of custom ELF header sections, documentation for these are well scattered. Unify this documentation in a central place and provide helpers to build custom Linux sections. This also generalizes sections code to enable avoiding modifying the linker scripts when we want to

[Xen-devel] [PATCH v7 08/14] jump_label: move guard #endif down where it belongs

The ending header guard is misplaced. This has no functional change, this is just an eye-sore. Signed-off-by: Luis R. Rodriguez --- include/linux/jump_label.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/include/linux/jump_label.h

[Xen-devel] [PATCH v7 05/14] kbuild: enable option to force compile force-obj-y and force-lib-y

Linux provides a rich array of features, enabling each feature however increases the size of the kernel and there are many features which users often want disabled. The traditional solution to this problem is for each feature to have its own Kconfig symbol, followed by a series of #ifdef

[Xen-devel] [PATCH v7 04/14] tables.h: add linker table support

A linker table is a data structure that is stitched together from items in multiple object files. Linux has historically implicitly used linker tables for ages, however they were all built in an adhoc manner which requires linker script modifications, per architecture. This adds a general linker

[Xen-devel] [libvirt test] 104184: trouble: blocked/broken

flight 104184 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/104184/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvops 3 host-install(3)broken REGR. vs. 104179

[Xen-devel] [xen-unstable baseline-only test] 68370: trouble: blocked/broken

This run is configured for baseline tests only. flight 68370 xen-unstable real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68370/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvops

[Xen-devel] [xen-unstable test] 104183: trouble: blocked/broken

flight 104183 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/104183/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvops 3 host-install(3)broken REGR. vs.

[Xen-devel] [xen-unstable-coverity test] 104185: trouble: broken

flight 104185 xen-unstable-coverity real [real] http://logs.test-lab.xenproject.org/osstest/logs/104185/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: coverity-amd643 host-install(3)broken REGR.

[Xen-devel] [qemu-mainline baseline-only test] 68369: trouble: blocked/broken

This run is configured for baseline tests only. flight 68369 qemu-mainline real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68369/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvops