flight 105444 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105444/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 105279
build-amd64
On 17-01-30 15:39:28, Konrad Rzeszutek Wilk wrote:
> > > +# Testing
> > > +
> > > +L2 CAT uses same xl interfaces as L3 CAT/CDP. So, we can execute these
> > > +commands to verify L2 CAT and L3 CAT/CDP on different HWs support them.
> > > +
> > > +For example:
> > > +root@:~$ xl psr-hwinfo --ca
Thanks a lot for reviewing the patches! Sorry for late to reply. I am on
vacation for Chinese New Year now. :)
On 17-01-30 13:10:33, Konrad Rzeszutek Wilk wrote:
> On Thu, Jan 19, 2017 at 02:01:03PM +0800, Yi Sun wrote:
> > + 2. Feature list node
> > +
> > + ```
> > + struct feat_node
flight 105405 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105405/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit2 14 guest-saverestore fail REGR. vs. 59254
test-amd64-amd64-xl
branch xen-unstable
xenbranch xen-unstable
job build-i386
testid xen-build
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://git.qemu.org/qemu.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: xen git://xenbits
flight 105422 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105422/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 105279
build-amd64
flight 105416 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105416/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 105279
build-amd64
This run is configured for baseline tests only.
flight 68509 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68509/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-pair 5 host-ping-check
flight 105403 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105403/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 105279
build-amd64
flight 105376 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105376/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail like 105331
test-amd64-i386-xl-qemuu-wi
On Fri, Feb 03, 2017 at 07:18:46PM +, Julien Grall wrote:
> There are multiple path disable ACPI on error. Consolidate in a single
> place, this will help in a follow-up patch to add more code on the error
> path.
>
> Signed-off-by: Julien Grall
> ---
> xen/arch/arm/acpi/boot.c | 25
flight 105353 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105353/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-xsm 15 guest-localmigratefail REGR. vs. 59254
test-armhf-armhf-li
flight 105380 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105380/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 105279
build-amd64
On Fri, Feb 03, 2017 at 08:52:29PM +, Andrew Cooper wrote:
> __func__ is standard C99, whereas __FUNCTION__ is a GCCism.
>
> No functional change.
>
> Signed-off-by: Andrew Cooper
Reviewed-by: Konrad Rzeszutek Wilk
___
Xen-devel mailing list
Xen
On Fri, 3 Feb 2017, Andrew Cooper wrote:
> __func__ is standard C99, whereas __FUNCTION__ is a GCCism.
>
> No functional change.
>
> Signed-off-by: Andrew Cooper
Acked-by: Stefano Stabellini
> CC: George Dunlap
> CC: Jan Beulich
> CC: Konrad Rzeszutek Wilk
> CC: Stefano Stabellini
> CC:
__func__ is standard C99, whereas __FUNCTION__ is a GCCism.
No functional change.
Signed-off-by: Andrew Cooper
---
CC: George Dunlap
CC: Jan Beulich
CC: Konrad Rzeszutek Wilk
CC: Stefano Stabellini
CC: Tim Deegan
CC: Wei Liu
---
xen/common/grant_table.c | 4 ++--
xen/common/libel
On 03/02/17 19:18, Julien Grall wrote:
> @@ -260,16 +257,22 @@ int __init acpi_boot_table_init(void)
> error = acpi_table_init();
> if ( error )
> {
> -disable_acpi();
> -return error;
> +printk("%s: Unable to initialize table parser (%d)\n",
> +
Since commit 4557c22 "xen: arm: rewrite start of day page table and cpu
bring up", Xen requires to be launched in NS HYP/EL2.
xen.axf is generated in order to directly boot Xen on ARM models (e.g
Foundation). However they usually start in secure mode, which mean Xen
cannot boot.
The way forward t
The build option CONFIG_LOAD_ADDRESS is defined but never plumbed
through.
Signed-off-by: Julien Grall
---
config/arm32.mk| 2 --
config/arm64.mk| 2 --
xen/arch/arm/Makefile | 2 +-
xen/arch/arm/xen.lds.S | 4 ++--
4 files changed, 3 insertions(+), 7 deletions(-)
diff --git a/
Currently the acpi banks are stored in a separate variable and have an
header just for them.
This variable can be moved in the structure bootinfo removing an header
and a global variable.
Signed-off-by: Julien Grall
---
xen/arch/arm/efi/efi-boot.h | 3 +--
xen/arch/arm/efi/efi-dom0.c | 12
On ARM, when the user put 'acpi=force' Xen will use ACPI over DT.
Currently, if Xen fails to initialize ACPI it will fallback on DT.
This behavior makes difficult for a user to notice Xen didn't used ACPI
has requested on platform where the firmware is providing both ACPI and DT.
Rather than fall
On Thu, Feb 02, 2017 at 11:15:41AM -0700, Jim Fehlig wrote:
On 02/02/2017 04:42 AM, Wei Liu wrote:
I saw this mail but didn't realise it required my input, sorry.
I suppose it didn't and I was shamelessly fishing for a review - so you have my
apologies :-). But the patch does fix an annoying,
Make it easier to figure out whether Xen is booting using ACPI or DT by
printing a message on the console.
Signed-off-by: Julien Grall
---
xen/arch/arm/setup.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
index 049e449..41aa1dd 100644
--- a
There are multiple path disable ACPI on error. Consolidate in a single
place, this will help in a follow-up patch to add more code on the error
path.
Signed-off-by: Julien Grall
---
xen/arch/arm/acpi/boot.c | 25 ++---
1 file changed, 14 insertions(+), 11 deletions(-)
diff -
The code to add a new bank is duplicated twice. Add a new helper that
checks if the maximum of bank has not reached and adds the bank.
Signed-off-by: Julien Grall
---
xen/arch/arm/efi/efi-boot.h | 34 ++
1 file changed, 18 insertions(+), 16 deletions(-)
diff --gi
The code contains a lot of memory_map[offset]. This could be simplified
by incrementing the descriptor pointer every time.
Signed-off-by: Julien Grall
---
xen/arch/arm/efi/efi-dom0.c | 17 -
1 file changed, 8 insertions(+), 9 deletions(-)
diff --git a/xen/arch/arm/efi/efi-dom0.c
When the GICv3 is not GICv2 compatible, the associated field in the MADT
will be zeroed. However, the rest of the code expects the variable to
be set to INVALID_PADDR.
This will result to false detection of GICv2 and give I/O access to page
0 for the hardware domain.
Thankfully, it will fail beca
The code to add a new memory descriptor is duplicated three times. Add a
new helper that adds the descriptor.
Signed-off-by: Julien Grall
---
xen/arch/arm/efi/efi-dom0.c | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/xen/arch/arm/ef
Make it easier to figure out whether Xen is booting using ACPI or DT by
printing a message on the console.
Signed-off-by: Julien Grall
---
xen/arch/arm/setup.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
index 049e449..41aa1dd 100644
--- a
Hi all,
This patch series contains a bunch of fix and clean-up for ACPI and EFI on
ARM64.
Note that the patch "xen/arm64: Don't zero BSS when booting using EFI" [1] is
required in order to test this series.
Cheers,
[1] https://lists.xenproject.org/archives/html/xen-devel/2017-02/msg00228.html
Currently the acpi banks are stored in a separate variable and have an
header just for them.
This variable can be moved in the structure bootinfo removing an header
and a global variable.
Signed-off-by: Julien Grall
---
xen/arch/arm/efi/efi-boot.h | 3 +--
xen/arch/arm/efi/efi-dom0.c | 12
The code to add a new bank is duplicated twice. Add a new helper that
checks if the maximum of bank has not reached and adds the bank.
Signed-off-by: Julien Grall
---
xen/arch/arm/efi/efi-boot.h | 34 ++
1 file changed, 18 insertions(+), 16 deletions(-)
diff --gi
There are multiple path disable ACPI on error. Consolidate in a single
place, this will help in a follow-up patch to add more code on the error
path.
Signed-off-by: Julien Grall
---
xen/arch/arm/acpi/boot.c | 25 ++---
1 file changed, 14 insertions(+), 11 deletions(-)
diff -
On ARM, when the user put 'acpi=force' Xen will use ACPI over DT.
Currently, if Xen fails to initialize ACPI it will fallback on DT.
This behavior makes difficult for a user to notice Xen didn't used ACPI
has requested on platform where the firmware is providing both ACPI and DT.
Rather than fall
The code contains a lot of memory_map[offset]. This could be simplified
by incrementing the descriptor pointer every time.
Signed-off-by: Julien Grall
---
xen/arch/arm/efi/efi-dom0.c | 17 -
1 file changed, 8 insertions(+), 9 deletions(-)
diff --git a/xen/arch/arm/efi/efi-dom0.c
Hi Stefano,
On 03/02/17 19:14, Stefano Stabellini wrote:
On Fri, 3 Feb 2017, Julien Grall wrote:
Hi Stefano,
On 02/02/17 23:25, Stefano Stabellini wrote:
On Thu, 2 Feb 2017, Julien Grall wrote:
---
xen/arch/arm/arm64/head.S | 23 +++
1 file changed, 19 insertions(+), 4 d
On Fri, 3 Feb 2017, Julien Grall wrote:
> Hi Stefano,
>
> On 02/02/17 23:25, Stefano Stabellini wrote:
> > On Thu, 2 Feb 2017, Julien Grall wrote:
> > > ---
> > > xen/arch/arm/arm64/head.S | 23 +++
> > > 1 file changed, 19 insertions(+), 4 deletions(-)
> > >
> > > diff --git
Hi Stefano,
On 02/02/17 23:25, Stefano Stabellini wrote:
On Thu, 2 Feb 2017, Julien Grall wrote:
---
xen/arch/arm/arm64/head.S | 23 +++
1 file changed, 19 insertions(+), 4 deletions(-)
diff --git a/xen/arch/arm/arm64/head.S b/xen/arch/arm/arm64/head.S
index 3f63d2a..8cb46
On 03/02/17 16:40, Juergen Gross wrote:
> On 03/02/17 17:20, Boris Ostrovsky wrote:
+
+ __HEAD
+
+/* Entry point for PVH guests. */
>>> Could you add some comments about register conetnts at entry?
>> Reference to Xen's docs/misc/hvmlite.markdown would be sifficient?
> I think
On 02/03/2017 03:54 AM, Jan Beulich wrote:
> A negative return value indicates an error; in fact the function at
> present won't ever return zero.
>
> Signed-off-by: Jan Beulich
> Reviewed-by: Juergen Gross
Applied to for-linus-4.11.
-boris
___
Xen
flight 105344 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105344/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit2 14 guest-saverestorefail REGR. vs. 105295
build-i386-pvops
On 03/02/17 17:20, Boris Ostrovsky wrote:
>
>>> +
>>> + __HEAD
>>> +
>>> +/* Entry point for PVH guests. */
>> Could you add some comments about register conetnts at entry?
>
> Reference to Xen's docs/misc/hvmlite.markdown would be sifficient?
I think the corresponding lines should be copied t
>> +
>> +__HEAD
>> +
>> +/* Entry point for PVH guests. */
> Could you add some comments about register conetnts at entry?
Reference to Xen's docs/misc/hvmlite.markdown would be sifficient?
>> +gdt:
>> +.word gdt_end - gdt
>> +.long _pa(gdt)
> This is a rather strange construc
flight 105354 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105354/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 105279
build-amd64
flight 105331 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105331/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-rtds 9 debian-install fail like 105224
test-amd64-i386-xl-qemut-wi
On Thu, Feb 02, 2017 at 08:42:44PM +, Julien Grall wrote:
> There are quite a few usage of "lenght" instead of "length" in different
> part of the repo. Correct it once for all.
>
> Signed-off-by: Julien Grall
Applied.
___
Xen-devel mailing list
X
>>> On 03.02.17 at 16:27, wrote:
> On Fri, 2017-02-03 at 01:41 -0700, Jan Beulich wrote:
>> > > > On 17.01.17 at 18:26, wrote:
>> > ---
>> > This is a bugfix, and should be backported to 4.8.
>>
>> While I did manage to backport "xen: credit2: use the correct scratch
>> cpumask" and "xen: credit
On Fri, 2017-02-03 at 01:41 -0700, Jan Beulich wrote:
> > > > On 17.01.17 at 18:26, wrote:
> > ---
> > This is a bugfix, and should be backported to 4.8.
>
> While I did manage to backport "xen: credit2: use the correct scratch
> cpumask" and "xen: credit2: fix shutdown/suspend when playing with
On Thu, 2017-02-02 at 20:42 +, Julien Grall wrote:
> There are quite a few usage of "lenght" instead of "length" in
> different
> part of the repo.
>
Most of which, in code I wrote! :-/
> Correct it once for all.
>
Thanks. :-)
> Signed-off-by: Julien Grall
>
Acked-by: Dario Faggioli
Dar
branch xen-unstable
xenbranch xen-unstable
job build-amd64
testid xen-build
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://git.qemu.org/qemu.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: xen git://xenbit
>>> On 03.02.17 at 15:35, wrote:
> On 03/02/17 14:31, Jan Beulich wrote:
> On 03.02.17 at 15:24, wrote:
>>> On 03/02/17 07:41, Jan Beulich wrote:
>>> On 02.02.17 at 20:25, wrote:
> @@ -261,6 +265,8 @@ GLOBAL(init_secondary)
> sub x20, x19, x0 /* x20 := phys-o
On 03/02/17 14:31, Jan Beulich wrote:
On 03.02.17 at 15:24, wrote:
On 03/02/17 07:41, Jan Beulich wrote:
On 02.02.17 at 20:25, wrote:
@@ -261,6 +265,8 @@ GLOBAL(init_secondary)
sub x20, x19, x0 /* x20 := phys-offset */
mov x22, #1/* x22 := i
>>> On 03.02.17 at 15:24, wrote:
> On 03/02/17 07:41, Jan Beulich wrote:
> On 02.02.17 at 20:25, wrote:
>>> @@ -261,6 +265,8 @@ GLOBAL(init_secondary)
>>> sub x20, x19, x0 /* x20 := phys-offset */
>>>
>>> mov x22, #1/* x22 := is_secondary_cpu */
Hi Jan,
On 03/02/17 07:41, Jan Beulich wrote:
On 02.02.17 at 20:25, wrote:
@@ -261,6 +265,8 @@ GLOBAL(init_secondary)
sub x20, x19, x0 /* x20 := phys-offset */
mov x22, #1/* x22 := is_secondary_cpu */
+/* Skip zero BSS on secondary CPUs
On Fri, Feb 3, 2017 at 2:53 PM, Bhupinder Thakur
wrote:
> Hi,
>
>>> Hi,
>>>
>>> I have done the changes for emulating pl011 in Xen. Currently, I have
>>> verified the emulation code by manually reading/writing data to
>>> /dev/ttyAMA0 which is the device file for pl011 device. The data is
>>> flow
On 03/02/17 13:53, Bhupinder Thakur wrote:
Hi,
Hi Bhupinder,
Hi,
I have done the changes for emulating pl011 in Xen. Currently, I have
verified the emulation code by manually reading/writing data to
/dev/ttyAMA0 which is the device file for pl011 device. The data is
flowing fine between xe
>>> On 27.01.17 at 19:06, wrote:
> On 27/01/17 16:40, Jan Beulich wrote:
>> So what we'll need to do then, as I understand it from the
>> discussion so far:
>>
>> - vmx_set_segment_register() will need to set a correct limit
>> - vmx_set_segment_register() should initialize the TSS every
>> time
Hi,
>> Hi,
>>
>> I have done the changes for emulating pl011 in Xen. Currently, I have
>> verified the emulation code by manually reading/writing data to
>> /dev/ttyAMA0 which is the device file for pl011 device. The data is
>> flowing fine between xenconsoled and the guest domain.
>>
>> As a next
>>> On 03.02.17 at 12:53, wrote:
> --- a/tools/fuzz/x86_instruction_emulator/Makefile
> +++ b/tools/fuzz/x86_instruction_emulator/Makefile
> @@ -11,16 +11,20 @@ endif
> x86_emulate/x86_emulate.c x86_emulate/x86_emulate.h:
> [ -L x86_emulate ] || ln -sf $(XEN_ROOT)/xen/arch/x86/x86_emulate .
>>> On 03.02.17 at 12:53, wrote:
> Signed-off-by: Wei Liu
Reviewed-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
>>> On 03.02.17 at 12:53, wrote:
> f4497d6b74 added x86_emulate.h private header but didn't add dependency
> for it.
>
> Use macro to reduce repetition.
>
> Signed-off-by: Wei Liu
Reviewed-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@list
On 03/02/17 14:23, Ian Jackson wrote:
> Juergen Gross writes ("Re: [Xen-devel] memory hotplug for domUs"):
>> As user interface we are starting with "xl mem-set" which will use
>> memory hotplug if necessary and supported by the guest (guest indicates
>> support via a Xenstore entry). A "force" par
This run is configured for baseline tests only.
flight 68508 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68508/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf f1d91f33a19b91a204237d9226cfc3351ec5f591
baseline v
Juergen Gross writes ("Re: [Xen-devel] memory hotplug for domUs"):
> As user interface we are starting with "xl mem-set" which will use
> memory hotplug if necessary and supported by the guest (guest indicates
> support via a Xenstore entry). A "force" parameter can be used with
> "xl mem-set" in c
On 03/02/17 13:19, Ian Jackson wrote:
> Juergen Gross writes ("Re: [Xen-devel] memory hotplug for domUs"):
>> While the syntax for "xl mem-add" (or however we would call it) could
>> be rather clear and simple:
>>
>> xl mem-add [--host-node ] [--guest-node ]
>>
>> I don't see how this would be th
On 2 February 2017 at 18:35, Stefano Stabellini wrote:
> The following changes since commit 3aca12f841fcd6f3a7477076dad0d564360500de:
>
> Merge remote-tracking branch
> 'remotes/pmaydell/tags/pull-target-arm-20170127' into staging (2017-01-27
> 16:59:17 +)
>
> are available in the git repo
Juergen Gross writes ("Re: [Xen-devel] memory hotplug for domUs"):
> While the syntax for "xl mem-add" (or however we would call it) could
> be rather clear and simple:
>
> xl mem-add [--host-node ] [--guest-node ]
>
> I don't see how this would be the case for xl mem-set. Imagine a guest
> bal
Signed-off-by: Wei Liu
Acked-by: Jan Beulich
---
tools/fuzz/README.afl | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/tools/fuzz/README.afl b/tools/fuzz/README.afl
index 431b4a8cbf..68e0fa396f 100644
--- a/tools/fuzz/README.afl
+++ b/tools/fuzz/README.afl
@@ -20,9 +20,1
Provide the fuzzer with more ops, and more sophisticated input
structure.
Based on a patch originally written by Andrew and George.
Signed-off-by: Andrew Cooper
Signed-off-by: George Dunlap
Signed-off-by: Wei Liu
---
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: George Dunlap
v2:
... so that users can know how big the initial input should be.
Signed-off-by: Wei Liu
Reviewed-by: Jan Beulich
---
.../fuzz/x86_instruction_emulator/afl-x86-insn-emulator-fuzzer.c | 8
tools/fuzz/x86_instruction_emulator/x86-insn-emulator-fuzzer.c| 5 +
2 files changed, 13 in
Forgot to CC people on this one.
On Fri, Feb 03, 2017 at 11:53:03AM +, Wei Liu wrote:
> f4497d6b74 added x86_emulate.h private header but didn't add dependency
> for it.
>
> Use macro to reduce repetition.
>
> Signed-off-by: Wei Liu
> ---
> tools/tests/x86_emulator/Makefile | 6 --
> 1
On Thu, Feb 02, 2017 at 03:46:35PM +, Wei Liu wrote:
> Wei Liu (2):
> xl: free event in DOMAIN_RESTART_RENAME error path
> xl: disable events earlier for shutdown event
>
> tools/libxl/xl_cmdimpl.c | 9 ++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
Pushed the most up to dat
flight 105345 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105345/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 105279
build-amd64
flight 105321 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105321/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-winxpsp3 3 host-install(3)broken REGR. vs. 59254
test-amd64-i386-qem
Wei Liu writes ("[PATCH 1/2] xl: free event in DOMAIN_RESTART_RENAME error
path"):
> Otherwise it is leaked. Found by code inspection.
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
No functional change.
Signed-off-by: Wei Liu
---
Cc: Jan Beulich
Cc: Andrew Cooper
V4: introduce x86.h macro
V3: link asm-x86 to working directory
---
tools/fuzz/x86_instruction_emulator/Makefile | 12
tools/tests/x86_emulator/Makefile| 12
tools/tests/x
Change the names used in code according to numeric values. Remove the
now unused macros in x86_emualte.c and fix indentation. This in turns
requires including msr-index.h and removing duplicates in userspace
x86_emulate.c in userspace harness program.
No functional change.
Signed-off-by: Wei Liu
The first few patches refactor x86emul code so that more code can be shared
between xen and userspace tools.
I have run XTF suite (tests subject to availability on the testbox I use, and
xsa-195 was skipped because qemu segfault -- a known issue) against this
series, no issue is found.
Please see
Basically this patch does 's/EFLG_/X86_EFLAGS_/g' and with indentation
fixed up. And remove the duplicates in x86_emualte.c. This in turn
requires userspace test harness to include x86-defns.h. Also remove a
few duplicates in userspace harness program.
No functional change.
Signed-off-by: Wei Li
f4497d6b74 added x86_emulate.h private header but didn't add dependency
for it.
Use macro to reduce repetition.
Signed-off-by: Wei Liu
---
tools/tests/x86_emulator/Makefile | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tools/tests/x86_emulator/Makefile
b/tools/tests
They will be shared between xen and userspace programs.
This is not strictly necessary, but it helps reduce overall code size.
No functional change.
Signed-off-by: Wei Liu
Acked-by: Jan Beulich
---
xen/include/asm-x86/processor.h | 11 +--
xen/include/asm-x86/x86-vendors.h | 13
And remove the duplicates.
No functional change.
Signed-off-by: Wei Liu
Reviewed-by: Jan Beulich
---
xen/arch/x86/x86_emulate/x86_emulate.c | 45 --
1 file changed, 15 insertions(+), 30 deletions(-)
diff --git a/xen/arch/x86/x86_emulate/x86_emulate.c
b/xen/arc
... so that they can be used by userspace x86 instruction emulator test
program and fuzzer as well.
No functional change.
Signed-off-by: Wei Liu
Reviewed-by: Jan Beulich
---
xen/include/asm-x86/processor.h | 65 ++-
xen/include/asm-x86/x86-defns.h | 68 +
Signed-off-by: Wei Liu
---
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Andrew Cooper
---
tools/fuzz/x86_instruction_emulator/Makefile | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tools/fuzz/x86_instruction_emulator/Makefile
b/tools/fuzz/x86_instruction_emulator/Makefile
i
It will be used later to remove duplicates in x86emul.
Signed-off-by: Wei Liu
Reviewed-by: Jan Beulich
---
xen/include/asm-x86/x86-defns.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/xen/include/asm-x86/x86-defns.h b/xen/include/asm-x86/x86-defns.h
index 48ea5ea03b..70453e8dfb 100644
--
On Thu, Feb 02, 2017 at 08:42:44PM +, Julien Grall wrote:
> There are quite a few usage of "lenght" instead of "length" in different
> part of the repo. Correct it once for all.
>
> Signed-off-by: Julien Grall
>
Acked-by: Wei Liu
___
Xen-devel m
On Fri, Feb 03, 2017 at 12:04:04AM -0700, Jan Beulich wrote:
> >>> On 02.02.17 at 18:12, wrote:
> > On Thu, Feb 02, 2017 at 10:01:46AM -0700, Jan Beulich wrote:
> >> >>> On 02.02.17 at 17:50, wrote:
> >> > On Thu, Feb 02, 2017 at 05:20:56AM -0700, Jan Beulich wrote:
> >> >> >>> On 01.02.17 at 13:
branch xen-unstable
xenbranch xen-unstable
job build-i386-xsm
testid xen-build
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://git.qemu.org/qemu.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: xen git://xen
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm
testid guest-localmigrate/x10
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.
On Fri, Feb 03, 2017 at 10:46:14AM +0100, Fatih Acar wrote:
> On 02/02/2017 17:22, Wei Liu wrote:
> >
> > The other solution is to have a dedicated counter for diskws instead of
> > relying on num_disks.
> >
>
> It's all good, both patches fix the issue, thank you.
>
Cool, I will add a Tested-
flight 105332 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105332/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf f1d91f33a19b91a204237d9226cfc3351ec5f591
baseline version:
ovmf 7fcb735412998d536cb34
>>> On 01.02.17 at 12:14, wrote:
> This aims at covering most MMX/SSEn/AVX instructions in the 0x0f-escape
> space with memory operands.
Which, as I've realized only now, means the title should also say
SSE3 (also in patch 04, i.e. the series also completely covers that
ISA extension, except for
>>> On 02.02.17 at 23:43, wrote:
> /*
> - * Now trampoline_phys points to the following structure (lowest
> - * address is at the top):
> + * Now trampoline_phys points to the following structure (lowest
> address
> + * is at the bottom):
> *
>
On 25/01/17 14:02, Dario Faggioli wrote:
> On Tue, 2017-01-24 at 16:03 -0700, Jim Fehlig wrote:
>> On 01/20/2017 09:06 AM, Juergen Gross wrote:
>>> On 20/01/17 16:54, Ian Jackson wrote:
Juergen Gross writes ("memory hotplug for domUs"):
> We first thought to enhance "xl mem-set", but after
flight 105335 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105335/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm5 xen-buildfail REGR. vs. 105279
build-amd64
On 02/02/2017 17:22, Wei Liu wrote:
>
> The other solution is to have a dedicated counter for diskws instead of
> relying on num_disks.
>
It's all good, both patches fix the issue, thank you.
--
Fatih ACAR
Gandi
fatih.a...@gandi.net
___
Xen-devel ma
On 02/02/2017 16:40, George Dunlap wrote:
>
> Sorry, I just want to clarify: Is it the case that before you tried to
> upgrade, you often migrated VMs between your Xen 4.1 hosts without
> problems?
>
> In other words, is it *4.8* that's the problem, or is it *migration*
> that's the problem?
>
>
On 30/01/17 18:45, Boris Ostrovsky wrote:
> rx_refill_timer should be deleted as soon as we disconnect from the
> backend since otherwise it is possible for the timer to go off before
> we get to xennet_destroy_queues(). If this happens we may dereference
> queue->rx.sring which is set to NULL in x
flight 68507 distros-debian-jessie real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68507/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-armhf-jessie-netboot-pygrub 1 build-check(1) blocked n/a
build-arm64
flight 105325 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/105325/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt-xsm 13 saverestore-support-checkfail like 105262
test-armhf-armhf-libvirt 13
1 - 100 of 102 matches
Mail list logo
