On 20.12.2016 19:01, Julien Grall wrote:
Hi Andrii,
On 20/12/2016 19:00, Andrii Anisov wrote:
Sorry for the mess,
I mean the xen-swiotlb issue on renesas board:
Bosch: problem with xen-swiotlb. It does not work properly on renesas
board.
Stefano: please report the error on the ML
ACTION:
Hello Dirk,
Except those two issues did you face some issues with PVR KM?
ANDRII ANISOV
Lead Systems Engineer
Office: +380 44 390 5457 x 66766 Cell: +380 50 573 8852 Email:
andrii_ani...@epam.com
Kyiv, Ukraine (GMT+3) epam.com
CONFIDENTIALITY CAUTION AND DISCLAIMER
This message
This run is configured for baseline tests only.
flight 68251 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68251/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install f
This run is configured for baseline tests only.
flight 68250 xen-4.5-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68250/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-multivcpu 6 xen-boot
On 20/12/2016 18:43, Eduardo Habkost wrote:
> This moves the KVM and Xen files to the an accel/ subdir.
>
> Instead of moving the *-stubs.c file to accel/ as-is, I tried to
> move most of the stub code to libqemustub.a. This way the obj-y
> logic for accel/ is simpler: obj-y includes accel/ only
Hi Edgar,
On 20/12/2016 13:53, Edgar E. Iglesias wrote:
On Mon, Dec 19, 2016 at 04:01:00PM -0800, Stefano Stabellini wrote:
On Mon, 19 Dec 2016, Julien Grall wrote:
Hi Edgar,
On 16/12/2016 18:04, Edgar E. Iglesias wrote:
On Fri, Dec 16, 2016 at 04:12:00PM +, Julien Grall wrote:
On 15/12
flight 68252 distros-debian-squeeze real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68252/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-amd64-squeeze-netboot-pygrub 9 debian-di-install fail like
68218
test-amd64-
On Mon, Dec 19, 2016 at 03:02:01PM +, Roger Pau Monne wrote:
> FreeBSD init scripts don't have /usr/local/{bin/sbin} in it's PATH, which
> prevents `xl devd` from working properly since hotplug scripts require the set
> of xenstore cli tools to be in PATH.
>
> While there also fix the usage of
On Mon, Dec 19, 2016 at 03:02:03PM +, Roger Pau Monne wrote:
> At the moment the execution of xencommons is gated on the presence of the
> privcmd device, but that's not correct, since privcmd is available to all Xen
> domains (privileged or unprivileged). Instead of using privcmd use the
> xen
On Mon, Dec 19, 2016 at 03:02:02PM +, Roger Pau Monne wrote:
> ...because it's empty. While there also rename xendriverdomain_startcmd to
> xendriverdomain_start in order to match the nomenclature of the file.
>
> Signed-off-by: Roger Pau Monné
> ---
> Cc: Ian Jackson
> Cc: Wei Liu
> ---
>
On Mon, Dec 19, 2016 at 03:02:04PM +, Roger Pau Monne wrote:
> Those are used in order to decide which scripts are executed at init.
>
> Signed-off-by: Roger Pau Monné
Can't say I know much about FreeBSD init mechanism, but I trust your
judgement:
Acked-by: Wei Liu
__
On Tue, Dec 20, 2016 at 01:33:39PM -0800, Stefano Stabellini wrote:
> On Tue, 20 Dec 2016, Christoffer Dall wrote:
> > Hi Stefano,
> >
> > On Mon, Dec 19, 2016 at 12:24:18PM -0800, Stefano Stabellini wrote:
> > > On Mon, 19 Dec 2016, Christoffer Dall wrote:
> > > > On Fri, Dec 16, 2016 at 05:03:13
Doug Goldstein writes ("Re: [Xen-devel] [PATCH v2 1/5] Remove hardcoded strict
-Werror checking"):
> I agree with you Andrew that its good for kernel/hypervisor development.
> I also agree its good for userspace code prior to being committed or
> part of a CI loop. Where I wish there was a switch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Xen Security Advisory CVE-2016-10025 / XSA-203
version 3
x86: missing NULL pointer check in VMFUNC emulation
UPDATES IN VERSION 3
Public release.
ISSUE DESCRIPTION
==
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Xen Security Advisory CVE-2016-10024 / XSA-202
version 3
x86 PV guests may be able to mask interrupts
UPDATES IN VERSION 3
Public release.
ISSUE DESCRIPTION
==
On Tue, Dec 20, 2016 at 11:46:57AM -0800, Alistair Francis wrote:
> Signed-off-by: Alistair Francis
> ---
> config/StdGNU.mk | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/config/StdGNU.mk b/config/StdGNU.mk
> index 6be8233..a6cdd82 100644
> --- a/config/StdGNU.mk
> +++ b/config/Std
On Wed, Dec 21, 2016 at 11:49:29AM +, Wei Liu wrote:
> On Mon, Dec 19, 2016 at 03:02:04PM +, Roger Pau Monne wrote:
> > Those are used in order to decide which scripts are executed at init.
> >
> > Signed-off-by: Roger Pau Monné
>
>
> Can't say I know much about FreeBSD init mechanism,
On Wed, Dec 21, 2016 at 11:48:40AM +, Wei Liu wrote:
> On Mon, Dec 19, 2016 at 03:02:02PM +, Roger Pau Monne wrote:
> > ...because it's empty. While there also rename xendriverdomain_startcmd to
> > xendriverdomain_start in order to match the nomenclature of the file.
> >
> > Signed-off-by
On Wed, Dec 21, 2016 at 12:21:44PM +0100, Paolo Bonzini wrote:
>
>
> On 20/12/2016 18:43, Eduardo Habkost wrote:
> > This moves the KVM and Xen files to the an accel/ subdir.
> >
> > Instead of moving the *-stubs.c file to accel/ as-is, I tried to
> > move most of the stub code to libqemustub.a.
flight 103780 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103780/
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 1
On 21/12/2016 14:14, Eduardo Habkost wrote:
> On Wed, Dec 21, 2016 at 12:21:44PM +0100, Paolo Bonzini wrote:
>>
>>
>> On 20/12/2016 18:43, Eduardo Habkost wrote:
>>> This moves the KVM and Xen files to the an accel/ subdir.
>>>
>>> Instead of moving the *-stubs.c file to accel/ as-is, I tried to
On Wed, Dec 21, 2016 at 02:47:54PM +0100, Paolo Bonzini wrote:
>
>
> On 21/12/2016 14:14, Eduardo Habkost wrote:
> > On Wed, Dec 21, 2016 at 12:21:44PM +0100, Paolo Bonzini wrote:
> >>
> >>
> >> On 20/12/2016 18:43, Eduardo Habkost wrote:
> >>> This moves the KVM and Xen files to the an accel/ su
>>> On 20.12.16 at 18:39, wrote:
> On 20/12/2016 10:39, Jan Beulich wrote:
>> @@ -3032,16 +3032,16 @@ void hvm_task_switch(
>> if ( hvm_set_cr3(tss.cr3, 1) )
>> goto out;
>>
>> -regs->eip= tss.eip;
>> -regs->eflags = tss.eflags | 2;
>> -regs->eax= tss.eax;
>> -
On 21/12/2016 15:15, Eduardo Habkost wrote:
>>
>> ifeq ($(CONFIG_SOFTMMU),y)
>> obj-$(CONFIG_KVM) += kvm-all.c
>> obj-$(call lnot, $(CONFIG_KVM)) += kvm-stub.c
>> endif
>>
>> similar to what is done already in Makefile.objs?
> I assume you mean:
>
> ifeq ($(CONFIG_SOFTMMU),y)
> obj-$(CONFIG_KV
vmfunc can in principle modify register state, so should operate on the shadow
register state rather than the starting state of emulation.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Paul Durrant
---
xen/arch/x86/hvm/emulate.c | 3 ++-
xen/arch/x86/x86_emulate/x86_emulate.
The bracketing of x86_emulate() calling the ops->vmfunc() hook is wrong with
respect to the assignment to rc, which can trip the new assertions in
x86_emulate_wrapper().
The hvmemul_vmfunc() hook should only raise #UD if X86EMUL_EXCEPTION is
returned. This is only a latent bug at the moment.
Sig
On Mon, Dec 12, 2016 at 06:56:36AM -0700, Jan Beulich wrote:
> >>> On 30.11.16 at 17:49, wrote:
> > @@ -567,7 +573,7 @@ static __init void hvm_setup_e820(struct domain *d,
> > unsigned long nr_pages)
> > /*
> > * Craft the e820 memory map for Dom0 based on the hardware e820 map.
> >
On Wed, Dec 21, 2016 at 12:12:06PM +, Roger Pau Monne wrote:
> On Wed, Dec 21, 2016 at 11:49:29AM +, Wei Liu wrote:
> > On Mon, Dec 19, 2016 at 03:02:04PM +, Roger Pau Monne wrote:
> > > Those are used in order to decide which scripts are executed at init.
> > >
> > > Signed-off-by: Ro
31d41d7b tried to make debug affect tools build only but failed to move
debug_symbols (which appends "-g" to CFLAGS) to tools/Rules.mk. Do that
in this patch.
Signed-off-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Konrad Rzeszutek Wilk
Cc: Stefano
Wei Liu (2):
build: move debug_symbols to tools/Rules.mk
build: use debug_symbols to add -g3
Config.mk | 5 -
tools/Rules.mk | 7 ++-
2 files changed, 6 insertions(+), 6 deletions(-)
--
2.1.4
___
Xen-devel mailing list
Xen-devel@lis
Signed-off-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Konrad Rzeszutek Wilk
Cc: Stefano Stabellini
Cc: Tim Deegan
Cc: Wei Liu
---
INSTALL | 4
1 file changed, 4 deletions(-)
diff --git a/INSTALL b/INSTALL
index b8d2ea4..58359da 100644
---
The lto symbol is superseded by CONFIG_LTO now.
Signed-off-by: Wei Liu
---
Discovered while reviewing some other patches.
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Konrad Rzeszutek Wilk
Cc: Stefano Stabellini
Cc: Tim Deegan
Cc: Wei Liu
---
config/StdGNU.mk
While doing archeology I found 38ce7ce3, we should also make sure
debug_symbols is the responsible for adding "-g" to CFLAGS.
Move adding "-g3" from being guarded by debug to being guarded by
debug_symbols.
Signed-off-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ja
Wei Liu (2):
config/StdGNU.mk: use CONFIG_LTO
INSTALL: remove stale lto build instruction
INSTALL | 4
config/StdGNU.mk | 2 +-
2 files changed, 1 insertion(+), 5 deletions(-)
--
2.1.4
___
Xen-devel mailing list
Xen-devel@lists.xen
It should be rc_pid.
Signed-off-by: Roger Pau Monné
Reported-by: Nathan Friess
---
Cc: Ian Jackson
Cc: Wei Liu
---
tools/hotplug/FreeBSD/rc.d/xendriverdomain.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/hotplug/FreeBSD/rc.d/xendriverdomain.in
b/tools/hotpl
On Wed, Dec 21, 2016 at 04:47:26PM +, Roger Pau Monne wrote:
> It should be rc_pid.
>
> Signed-off-by: Roger Pau Monné
> Reported-by: Nathan Friess
Acked + applied.
I suspect all the patches to fix FreeBSD init script should be
backported?
> ---
> Cc: Ian Jackson
> Cc: Wei Liu
> ---
>
>>> On 21.12.16 at 17:32, wrote:
> On Mon, Dec 12, 2016 at 06:56:36AM -0700, Jan Beulich wrote:
>> >>> On 30.11.16 at 17:49, wrote:
>> > +static int __init hvm_setup_acpi_madt(struct domain *d, paddr_t *addr)
>> > +{
>> > +struct acpi_table_madt *madt;
>> > +struct acpi_table_header *tabl
flight 103789 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103789/
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 1
On Wed, 21 Dec 2016, Julien Grall wrote:
> Hi Edgar,
>
> On 20/12/2016 13:53, Edgar E. Iglesias wrote:
> > On Mon, Dec 19, 2016 at 04:01:00PM -0800, Stefano Stabellini wrote:
> > > On Mon, 19 Dec 2016, Julien Grall wrote:
> > > > Hi Edgar,
> > > >
> > > > On 16/12/2016 18:04, Edgar E. Iglesias wr
Hi Stefano,
On 20/12/2016 20:53, Stefano Stabellini wrote:
On Tue, 20 Dec 2016, Julien Grall wrote:
On 19/12/2016 21:24, Stefano Stabellini wrote:
On Mon, 19 Dec 2016, Christoffer Dall wrote:
On Fri, Dec 16, 2016 at 05:03:13PM +, Julien Grall wrote:
Finally, we cannot hijack one of the g
flight 103793 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103793/
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 1
On Tue, 20 Dec 2016, Boris Ostrovsky wrote:
> Commit d6ac8e22c7c5 ("acpi/x86: define ACPI IO registers for
> PVH guests") broke ARM64 build of mk_dsdt.c due to introduction
> of XEN_ACPI_CPU_MAP[_LEN] macros that are needed only for x86
> guests.
>
> We could fix the build by dealing specifically
Hi Stefano,
On 20/12/2016 22:33, Stefano Stabellini wrote:
On Tue, 20 Dec 2016, Christoffer Dall wrote:
On Mon, Dec 19, 2016 at 12:24:18PM -0800, Stefano Stabellini wrote:
On Mon, 19 Dec 2016, Christoffer Dall wrote:
On Fri, Dec 16, 2016 at 05:03:13PM +, Julien Grall wrote:
hvm_param is
Commit d6ac8e22c7c5 ("acpi/x86: define ACPI IO registers for
PVH guests") broke ARM64 build of mk_dsdt.c due to introduction
of XEN_ACPI_CPU_MAP[_LEN] macros that are needed only for x86
guests.
We could fix the build by dealing specifically with those macros
but since post-MADT code is not execut
flight 103783 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103783/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-xtf-amd64-amd64-2 3 host-install(3) broken in 103753 pass in 103783
test-amd64-amd64-xl-qemut-win
Fix cut-n-paste typo; changed the words "count not" to "could not".
No functional changes
Signed-off-by: Eric DeVolder
---
tools/libxc/xc_kexec.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/libxc/xc_kexec.c b/tools/libxc/xc_kexec.c
index 1cceb5d2d6..989e225192
On Wed, Dec 21, 2016 at 01:37:31PM -0800, Eric DeVolder wrote:
> Fix cut-n-paste typo; changed the words "count not" to "could not".
>
> No functional changes
>
> Signed-off-by: Eric DeVolder
Reviewed-by: Konrad Rzeszutek Wilk
>
> ---
> tools/libxc/xc_kexec.c | 4 ++--
> 1 file changed, 2 in
On Wed, 21 Dec 2016, Boris Ostrovsky wrote:
> Commit d6ac8e22c7c5 ("acpi/x86: define ACPI IO registers for
> PVH guests") broke ARM64 build of mk_dsdt.c due to introduction
> of XEN_ACPI_CPU_MAP[_LEN] macros that are needed only for x86
> guests.
>
> We could fix the build by dealing specifically
flight 103782 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103782/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qemuu-debianhvm-amd64 3 host-install(3) broken in 103772
pass in 103782
test-amd64-i386
On Wed, 21 Dec 2016, Julien Grall wrote:
> Hi Stefano,
>
> On 20/12/2016 20:53, Stefano Stabellini wrote:
> > On Tue, 20 Dec 2016, Julien Grall wrote:
> > > On 19/12/2016 21:24, Stefano Stabellini wrote:
> > > > On Mon, 19 Dec 2016, Christoffer Dall wrote:
> > > > > On Fri, Dec 16, 2016 at 05:03:1
Hi all,
the 4.9 development cycle is open, and we a number of new outstanding PV
driver protocols on the agenda. I published a proposal on the lifecycle
of PV drivers that might help speed up the process. I suggest we have a
conference call to discuss how to proceed.
Which PV protocol designs sho
On Fri, Dec 16, 2016 at 12:27:31PM +0800, George Dunlap wrote:
> On Fri, Dec 16, 2016 at 7:20 AM, Ronald Rojas wrote:
> > Create a basic Makefile to build and install libxenlight Golang
> > bindings. Also add a template.
>
> What's this template again?
I use 'template' to mean the same thing as
flight 103787 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103787/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf d0c80b8a2de8ac90f51b86cce24e6c9c267ae5b4
baseline version:
ovmf 403f54768cd5172211430
On Tue, 20 Dec 2016, Stefano Stabellini wrote:
> On Tue, 20 Dec 2016, Julien Grall wrote:
> > Hi Stefano,
> >
> > On 20/12/2016 00:22, Stefano Stabellini wrote:
> > > On Mon, 19 Dec 2016, Julien Grall wrote:
> > > > Hi Stefano,
> > > >
> > > > On 19/12/2016 23:30, Stefano Stabellini wrote:
> > >
Hi all,
this patch series fixes a lock inversion bug in Xen on ARM. The locking
order is: first rank lock, then vgic lock. The order is respected
everywhere, except for gic_update_one_lr.
gic_update_one_lr is called with the vgic lock held, but it calls
vgic_get_target_vcpu, which tries to obtain
GIC_INVALID_LR should be 0xff, but actually, defined as ~(uint8_t)0, is
0x. Fix the problem by placing the ~ operator before the cast.
Signed-off-by: Stefano Stabellini
---
xen/include/asm-arm/vgic.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/include/asm-arm/
gic_update_one_lr is called with the vgic lock held, but it calls
vgic_get_target_vcpu, which tries to obtain the rank lock. This can
cause deadlocks.
We already have a version of vgic_get_target_vcpu that doesn't take the
rank lock: __vgic_get_target_vcpu.
Solve the lock inversion problem, by no
Always take the vgic lock of the old vcpu. When more than one irq
migration is requested before the first one completes, take the vgic
lock of the oldest vcpu.
Write the new vcpu id into the rank from vgic_migrate_irq, protected by
the oldest vgic vcpu lock.
Use barriers to ensure proper ordering
We currently store the LR register number for every irq in irq_pending,
but we don't store the vcpu id. Thus, we know in which LR they are, but
we don't know the LR of which cpu. Fix this gap by adding a vcpu field
in struct pending_irq. Use the bytes that are currently used for
padding within the
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 scatterred. 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
st set (this) is for the kernel work, the second set is for the
tools/ userspace sandbox. If you would like to review all the changes in git
form you can yank them off of my linux-next 20161221-linker-tables-v5 branch on
kernel.org [3], please however note that the last patch on that tree was *not
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
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
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
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
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
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_
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 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.
v5:
o since we dropped SECTION_ORDER_ANY, use 'any
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.
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
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
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
second part to the linker table work, the first part
is the kernel work. I've split it up to make it easier to review. All the
code is present on my linux-next 20161221-linker-tables-v5 branch on
kernel.org [1], if you check that code out you can disregard the last patch
as it was a debug pat
Add a test drivers for linker tables.
v5: added this commit for the first time in this series.
Signed-off-by: Luis R. Rodriguez
---
lib/Kconfig.debug| 6 +
lib/Makefile | 1 +
lib/test_linktables/Makefile | 13 +
lib/test_link
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 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
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
Hi, xuquan.
I have tested it on my skylake server. W/o this patch the inaccurate
wall clock time issue only exists in Win7-32 guest. Win7-64, Win8-32, Win8-64,
Win10-32 ,Win10-64 and linux-4.8.0+ guests don't have this issue.
W/ this v4 patch, the issue disappears in Win7-32 guest and no wall lock
Hi Chao,
To me, it is sufficient.. thanks for your verification!!
Quan
On December 22, 2016 4:02 AM, Chao Gao wrote:
>Hi, xuquan.
>I have tested it on my skylake server. W/o this patch the inaccurate wall
>clock time issue only exists in Win7-32 guest. Win7-64, Win8-32, Win8-64,
>Win10-32 ,Win10
flight 103785 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103785/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 3 host-install(3)broken REGR. vs. 1033
flight 103784 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/103784/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl 6 xen-boot fail REGR. vs. 101737
test-amd64-amd64-qemu
hi,
Can anybody give a list of intel based boards for automotive embedded use
case in which xen could be installed?.
regards,
George
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
This run is configured for baseline tests only.
flight 68255 xen-4.6-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68255/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-520 xtf/test-hvm32-
When the xenbus driver does some special handling for a Xenstore
command any error condition related to the command should be returned
via an error response instead of letting the related write operation
fail. Otherwise the user land handler might take wrong decisions
assuming the connection to Xen
When accessing Xenstore in a transaction the user is specifying a
transaction id which he normally obtained from Xenstore when starting
the transaction. Xenstore is validating a transaction id against all
known transaction ids of the connection the request came in. As all
requests of a domain not b
Do some minor bug fixes and cleanup of xenbus driver.
Juergen Gross (3):
xen: xenbus driver must not accept invalid transaction ids
xen: return xenstore command failures via response instead of rc
xen: remove stale xs_input_avail() from header
drivers/xen/xenbus/xenbus_comms.h| 1
In drivers/xen/xenbus/xenbus_comms.h there is a stale declaration of
xs_input_avail(). Remove it.
Signed-off-by: Juergen Gross
---
drivers/xen/xenbus/xenbus_comms.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/xen/xenbus/xenbus_comms.h
b/drivers/xen/xenbus/xenbus_comms.h
index e74
Hi, Konrad!
I see no comments for almost 3 weeks now, so
probably there are no objections against this protocol.
Can we please move on on this?
Thank you in advance,
Oleksandr
On 12/08/2016 05:13 PM, Oleksandr Andrushchenko wrote:
I'm just wondering if anybody had a chance to look at the patch
Thanks a lot!
> From: Gao, Chao
> Sent: Thursday, December 22, 2016 4:02 AM
>
> Hi, xuquan.
> I have tested it on my skylake server. W/o this patch the inaccurate
> wall clock time issue only exists in Win7-32 guest. Win7-64, Win8-32, Win8-64,
> Win10-32 ,Win10-64 and linux-4.8.0+ guests don't ha
>>> On 20.12.16 at 23:50, wrote:
> On Tue, 20 Dec 2016, Jan Beulich wrote:
>> >>> On 20.12.16 at 00:01, wrote:
>> > This is actually not an ARM specific question, so changing the subject
>> > and CC'ing more people.
>> >
>> > On Wed, 14 Dec 2016, Konrad Rzeszutek Wilk wrote:
>> >> On Tue, Dec 13
sent too quick. I meant please add your tested-by here. :-)
> From: Tian, Kevin
> Sent: Thursday, December 22, 2016 3:48 PM
>
> Thanks a lot!
>
> > From: Gao, Chao
> > Sent: Thursday, December 22, 2016 4:02 AM
> >
> > Hi, xuquan.
> > I have tested it on my skylake server. W/o this patch the inac
> From: Xuquan (Quan Xu) [mailto:xuqu...@huawei.com]
> Sent: Wednesday, December 21, 2016 1:44 PM
>
> When Xen apicv is enabled, wall clock time is faster on Windows7-32
> guest with high payload (with 2vCPU, captured from xentrace, in
> high payload, the count of IPI interrupt increases rapidly b
95 matches
Mail list logo
