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 12:07, 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 12:07, Xuquan (Quan Xu) wrote:
>> >> On January 12, 2017 5:14 PM, Andrew Cooper wrote:
>> >>> On 12/01
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 disables
> polling. T
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: KarimA
> 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 service owner wrote:
> fligh
> 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 mailing list
Xen-devel@lists.xen.org
https://lists.xen
> 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
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 +
1 file changed, 9 in
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 d07e586b9ba0..cb7d6b490e0
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
---
tools/i
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.
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
Add a test drivers for linker tables.
v7: address ./scripts/checkpatch.pl --codespell issues
v6: rename table macro as suggested by Andy Shevchenko
v5: added this commit for the first time in this series.
Signed-off-by: Luis R. Rodriguez
---
lib/Kconfig.debug| 6 +
lib
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 100644
--- a/tools/inc
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 bug.
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 t
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 Shevche
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 KBUILD_
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 CONFIG_STATIC_KEYS_SELFT
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 custom
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. Rodrig
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 avai
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 a
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 changed, 4 insertions(+)
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 a
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 b/include/linux/jump_label.h
index a05
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 statements
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 ta
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
bu
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
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. 10418
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.
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
33 matches
Mail list logo