flight 131594 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131594/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
Hello Jairo,
On 25.12.18 18:07, LOPEZ, FUENTES NACARINO Jairo Eduardo wrote:
I believe this is the SoC information. If there is any other method of
extracting the information, please let me know so I can transmit it.
That output gives a full set of required information. Actually, I worried yo
flight 131597 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131597/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-armhf-armhf-xl 1
On Tue, Dec 25, 2018 at 11:12:20PM +0100, Tom Psyborg wrote:
> there was discussion about this just some days ago. CC 4-5 lists is
> more than enough
>
I don't know who you were discussing this with...
You should CC the 0th patch to all the mailinglists. That much is a
clear rule.
For the rest
flight 131584 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131584/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvshim7 xen-boot fail REGR. vs. 131534
test-amd64-amd64-lib
No functional change.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Wei Liu
---
xen/arch/x86/hvm/dom0_build.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/x86/hvm/dom0_build.c b/xen/arch/x86/hvm/dom0_build.c
index 24cc15f28b..c0eb9cb9
No functional change.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Wei Liu
---
xen/arch/x86/hvm/dom0_build.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/x86/hvm/dom0_build.c b/xen/arch/x86/hvm/dom0_build.c
index 12c20a4b66..91dc27dc
As long as the memory stolen is always above 1MB. This allows the PVH
Dom0 builder to be used on a memory map that only has a single RAM
region starting at 0.
Reported-by: Andrew Cooper
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Wei Liu
---
xen/arch/x86/hvm/dom0
No functional change.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Wei Liu
---
xen/arch/x86/hvm/dom0_build.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/x86/hvm/dom0_build.c b/xen/arch/x86/hvm/dom0_build.c
index c0eb9cb953..7ea29c44
Hello,
This series contains some trivial bug fixes for the PVH dom0 builder and
an improvement when filling the p2m so that alignment is taken into
account when allocating and populating the p2m.
Thanks, Roger.
Roger Pau Monne (5):
x86/dom0: fix wording of PVH Dom0 error message
x86/dom0: al
Current code that allocates memory and populates the p2m for PVH Dom0
doesn't take the address alignment into account, this can lead to high
order allocations that start on a non-aligned address to be broken
down into lower order entries on the p2m page tables.
Fix this by taking into account the
This implies there's no need to forcefully reserve the VGA MMIO
region, since the memory map provided will be correct.
Reported-by: Andrew Cooper
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
Cc: Wei Liu
---
xen/arch/x86/e820.c | 11 ++-
1 file changed, 6 inser
When running Xen as a guest it's not necessary to mark such pages as
RAM because they won't be assigned to the initial domain memory map.
While there move the functions to the PV shim specific file and rename
them accordingly.
No functional change expected.
Reported-by: Andrew Cooper
Signed-off
This function is based on the Linux e820__range_remove function,
modified to fit Xen coding style.
Signed-off-by: Roger Pau Monné
---
---
xen/arch/x86/e820.c| 56 ++
xen/include/asm-x86/e820.h | 2 ++
2 files changed, 58 insertions(+)
diff --git a/xe
Hello,
This series includes some miscellaneous fixes for the pv-shim mode,
specially regarding the handling of the memory map.
Thanks, Roger.
Roger Pau Monne (4):
x86/e820: introduce a function to remove ranges from e820
x86/e820: do not fixup memmap in copy_e820_map
x86/e820: assume memma
And instead introduce a new helper to mark the low 1MB VGA/ROM region
as reserved. Note this might be a slight change from current functionality
where copy_e820_map would just leave a hole in the [640KB, 1MB) region
if it was found to be reported as RAM in the memory map.
No functional change expe
flight 131596 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131596/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
On Wed, Dec 26, 2018 at 07:42:14PM +0800, Pu Wen wrote:
> On 2018/12/21 18:20, Andrew Cooper wrote:
> >> + /* Hygon CPUs do not support SYSENTER outside of legacy mode. */
> >> + __clear_bit(X86_FEATURE_SEP, c->x86_capability);
> >> +
> >> + /* Hygon processors have APIC timer running in deep C
flight 131587 linux-4.19 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131587/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-shadow7 xen-boot fail REGR. vs. 129313
test-amd64-amd64-xl-
On 27/12/2018 15:26, Roger Pau Monne wrote:
> No functional change.
>
> Signed-off-by: Roger Pau Monné
Acked-by: Andrew Cooper
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
On 27/12/2018 15:26, Roger Pau Monne wrote:
> No functional change.
>
> Signed-off-by: Roger Pau Monné
Reviewed-by: Andrew Cooper
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
On 27/12/2018 15:26, Roger Pau Monne wrote:
> As long as the memory stolen is always above 1MB. This allows the PVH
> Dom0 builder to be used on a memory map that only has a single RAM
> region starting at 0.
>
> Reported-by: Andrew Cooper
> Signed-off-by: Roger Pau Monné
Reviewed-by: Andrew Coo
On 27/12/2018 15:26, Roger Pau Monne wrote:
> No functional change.
>
> Signed-off-by: Roger Pau Monné
Acked-by: Andrew Cooper
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
On 27/12/2018 15:26, Roger Pau Monne wrote:
> Current code that allocates memory and populates the p2m for PVH Dom0
> doesn't take the address alignment into account, this can lead to high
> order allocations that start on a non-aligned address to be broken
> down into lower order entries on the p2
On 27/12/2018 15:56, Roger Pau Monne wrote:
> This function is based on the Linux e820__range_remove function,
> modified to fit Xen coding style.
>
> Signed-off-by: Roger Pau Monné
> ---
> ---
> xen/arch/x86/e820.c| 56 ++
> xen/include/asm-x86/e820.h
On 27/12/2018 15:56, Roger Pau Monne wrote:
> And instead introduce a new helper to mark the low 1MB VGA/ROM region
> as reserved. Note this might be a slight change from current functionality
> where copy_e820_map would just leave a hole in the [640KB, 1MB) region
> if it was found to be reported
On 27/12/2018 15:56, Roger Pau Monne wrote:
> This implies there's no need to forcefully reserve the VGA MMIO
> region, since the memory map provided will be correct.
>
> Reported-by: Andrew Cooper
> Signed-off-by: Roger Pau Monné
> ---
> Cc: Jan Beulich
> Cc: Andrew Cooper
> Cc: Wei Liu
> ---
On 27/12/2018 15:56, Roger Pau Monne wrote:
> When running Xen as a guest it's not necessary to mark such pages as
> RAM because they won't be assigned to the initial domain memory map.
>
> While there move the functions to the PV shim specific file and rename
> them accordingly.
>
> No functional
On 26/12/2018 11:42, Pu Wen wrote:
> On 2018/12/21 18:20, Andrew Cooper wrote:
>
>>> + /* Hygon CPUs do not support SYSENTER outside of legacy mode. */
>>> + __clear_bit(X86_FEATURE_SEP, c->x86_capability);
>>> +
>>> + /* Hygon processors have APIC timer running in deep C states. */
>>>
So,
On 12/24/18 1:32 AM, Hans van Kranenburg wrote:
>
> On 12/21/18 6:54 PM, Hans van Kranenburg wrote:
>>
>> We've been tracking down a live migration bug during the last three days
>> here at work, and here's what we found so far.
>>
>> 1. Xen version and dom0 linux kernel version don't matter.
flight 131598 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131598/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
On 20/12/2018 13:15, Pu Wen wrote:
> The Hygon Dhyana CPU don't save/restore FDP/FIP/FOP unless an exception
> is pending. So add support for it in the function xrstor.
Really?
Zen was the first AMD processor to fix this (mis)feature, and the Xen
code doesn't appear to have caught up yet.
I'm pu
flight 131600 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131600/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-armhf-armhf-xl 1
flight 131601 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131601/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131602 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131602/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131603 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131603/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131604 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131604/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131605 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131605/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131606 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131606/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131607 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131607/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131608 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131608/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131609 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131609/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131610 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131610/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
Hello Andrii,
Thanks again for responding and for clarifying some of the underlying
workings of Yocto.
2018年12月27日(木) 20:07 Andrii Anisov :
> Hello Jairo,
>
> On 25.12.18 18:07, LOPEZ, FUENTES NACARINO Jairo Eduardo wrote:
> > I believe this is the SoC information. If there is any other method o
flight 131611 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131611/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131589 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131589/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-rumprun-amd64 7 xen-boot fail REGR. vs. 125898
test-amd64-amd64-am
flight 131612 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131612/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
47 matches
Mail list logo
