On 8/10/2017 6:44 PM, Julien Grall wrote:
On 08/10/2017 02:00 PM, Manish Jaggi wrote:
HI Julien,
On 8/10/2017 5:43 PM, Julien Grall wrote:
On 10/08/17 13:00, Manish Jaggi wrote:
Hi Julien,
On 8/10/2017 4:58 PM, Julien Grall wrote:
On 10/08/17 12:21, Manish Jaggi wrote:
Hi Julien,
flight 112561 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112561/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 112544
test-amd64-amd64-x
flight 112583 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112583/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm6 xen-buildfail REGR. vs. 112539
build-i386
flight 112571 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112571/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm6 xen-buildfail REGR. vs. 112539
build-i386
flight 112557 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112557/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-libvirt-xsm 1 build-check(1) blocked n/a
test-arm64-arm64-xl 1 build-ch
flight 112567 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112567/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xtf 8956f82ce1321b89deda6895d58e5788d2198477
baseline version:
xtf 11ae3010a30c89a6aef762
flight 112553 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112553/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvops 3 capture-logs broken REGR. vs. 112102
flight 112551 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112551/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-examine 7 reboot fail REGR. vs. 110515
test-amd64-amd64-xl
Hi Everyone,
I am currently exploring on bringing up XenGT for an Intel embedded board.
I came across this document relating to bringing up XenGT for the Sandy
Bridge/Ivy Bridge/Haswell platform
https://www.intel.com/content/dam/www/public/us/en/documents/guides/xgengt-for-ivi-solutions-dev-kit-g
This run is configured for baseline tests only.
flight 71960 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71960/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-examine 10 examine-serial/
On 08/08/2017 09:09 AM, Wei Liu wrote:
Ian and Stefano
Oleksandr discovered that the p9fs array in libxl_domain_config is name
p9 instead of p9s. This causes problem for his work to rework device
framework.
Given that p9fs was added only during last release and the only known
external toolstack
On 10/08/2017 21:09, Volodymyr Babchuk wrote:
Hi,
On 10.08.17 21:18, Julien Grall wrote:
Hi,
On 10/08/17 18:40, Volodymyr Babchuk wrote:
On 10.08.17 19:11, Julien Grall wrote:
On 10/08/17 16:33, Volodymyr Babchuk wrote:
Hi Julien,
On 09.08.17 13:10, Julien Grall wrote:
Hi Volodymyr,
flight 112563 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112563/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm6 xen-buildfail REGR. vs. 112539
build-i386
Hi,
On 10.08.17 21:18, Julien Grall wrote:
Hi,
On 10/08/17 18:40, Volodymyr Babchuk wrote:
On 10.08.17 19:11, Julien Grall wrote:
On 10/08/17 16:33, Volodymyr Babchuk wrote:
Hi Julien,
On 09.08.17 13:10, Julien Grall wrote:
Hi Volodymyr,
CC "THE REST" maintainers to get an opinion on
Hi,
On 10/08/17 18:40, Volodymyr Babchuk wrote:
On 10.08.17 19:11, Julien Grall wrote:
On 10/08/17 16:33, Volodymyr Babchuk wrote:
Hi Julien,
On 09.08.17 13:10, Julien Grall wrote:
Hi Volodymyr,
CC "THE REST" maintainers to get an opinion on the public headers.
On 08/08/17 21:08, Volod
On Thu, 10 Aug 2017, Boris Ostrovsky wrote:
> On 07/31/2017 06:57 PM, Stefano Stabellini wrote:
> > Hi all,
> >
> > this series introduces the frontend for the newly introduced PV Calls
> > procotol.
> >
> > PV Calls is a paravirtualized protocol that allows the implementation of
> > a set of POSIX
On Thu, Aug 10, 2017 at 11:09:20AM +, Zhang, Xiong Y wrote:
> On my SKL/KBL machine, upstream 4.12 kernel dom0 couldn't boot up using
> xen.efi which is xen 4.9
>
>
> (1) Upstream 4.11 kernel doesn't have such issue.
>
> (2) Upstream 4.12 kernel on my native uefi machine could boot
On 10/08/17 17:38, Wei Liu wrote:
On Thu, Aug 10, 2017 at 05:11:52PM +0100, Julien Grall wrote:
On 10/08/17 17:00, Wei Liu wrote:
On Thu, Aug 10, 2017 at 03:26:07PM +0100, Julien Grall wrote:
On 09/08/17 11:58, Bhupinder Thakur wrote:
Hi Julien,
Hi Bhupinder,
Thanks for the testing.
On 10/08/17 18:45, Anthony PERARD wrote:
> On Thu, Aug 10, 2017 at 03:00:56PM +0100, Anthony PERARD wrote:
>> On Wed, Aug 09, 2017 at 06:34:43PM +0200, Sander Eikelenboom wrote:
>>> L.S.,
>>>
>>> It seems the xen qemu-upstream tree got updated from qemu upstream last
>>> week.
>>> Unfortunately a
On 10.08.17 19:11, Julien Grall wrote:
On 10/08/17 16:33, Volodymyr Babchuk wrote:
Hi Julien,
On 09.08.17 13:10, Julien Grall wrote:
Hi Volodymyr,
CC "THE REST" maintainers to get an opinion on the public headers.
On 08/08/17 21:08, Volodymyr Babchuk wrote:
SMCCC (SMC Call Convention) d
On 10/08/17 18:28, Wei Liu wrote:
> On Wed, Aug 09, 2017 at 09:07:04AM +0200, Juergen Gross wrote:
>> Add a new libxl function to set hypervisor parameters at runtime
>> similar to boot time parameters via command line.
>>
>> Cc: Ian Jackson
>> Cc: Wei Liu
>> Signed-off-by: Juergen Gross
>> ---
On 10/08/17 18:17, Wei Liu wrote:
> On Wed, Aug 09, 2017 at 09:07:01AM +0200, Juergen Gross wrote:
>> Add the needed infrastructure for runtime parameter changing similar
>> to that used at boot time via cmdline. We are using the same parsing
>> functions as for cmdline parsing, but with a differen
On 10/08/17 18:29, Peter Zijlstra wrote:
> On Thu, Aug 10, 2017 at 06:24:53PM +0200, Peter Zijlstra wrote:
>> -ENTRY(xen_irq_enable_direct)
>> -FRAME_BEGIN
>> -/* Unmask events */
>> -movb $0, PER_CPU_VAR(xen_vcpu_info) + XEN_vcpu_info_mask
>> -
>> -/*
>> - * Preempt here doesn'
Add the CONFIG_X86_PIE option which builds the kernel as a Position
Independent Executable (PIE). The kernel is currently build with the
mcmodel=kernel option which forces it to stay on the top 2G of the
virtual address space. With PIE, the kernel will be able to move below
the -2G limit increasing
By default PIE generated code create only relative references so _text
points to the temporary virtual address. Instead use a global variable
so the relocation is done as expected.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memo
Change the relocation tool to correctly handle DYN/PIE kernel where
the relocation table does not reference symbols and percpu support is
not needed. Also add support for R_X86_64_RELATIVE relocations that can
be handled like a 64-bit relocation due to the usage of -Bsymbolic.
Position Independent
Add a new CONFIG_RANDOMIZE_BASE_LARGE option to benefit from PIE
support. It increases the KASLR range from 1GB to 3GB. The new range
stars at 0x just above the EFI memory region. This
option is off by default.
The boot code is adapted to create the appropriate page table spanning
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
arch/x86/kernel/relocate_kern
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Early at boot, the kernel is mapped at a temporary address while preparing
the page table. To know the changes needed for the page table with KASLR,
the boot code calculate the difference betwe
Add a new _ASM_GET_PTR macro to fetch a symbol address. It will be used
to replace "_ASM_MOV $, %dst" code construct that are not compatible
with PIE.
Signed-off-by: Thomas Garnier
---
arch/x86/include/asm/asm.h | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/x86/include/
Change assembly to use the new _ASM_GET_PTR macro instead of _ASM_MOV for
the assembly to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
arch/x86/include/asm/pm-t
Provide an option to default visibility to hidden except for key
symbols. This option is disabled by default and will be used by x86_64
PIE support to remove errors between compilation units.
Signed-off-by: Thomas Garnier
---
arch/x86/boot/boot.h | 2 +-
arch/x86/include/asm/setup.h
The x86 relocation tool generates a list of 32-bit signed integers. There
was no need to use 64-bit integers because all addresses where above the 2G
top of the memory.
This change add a large-reloc option to generate 64-bit unsigned integers.
It can be used when the kernel plan to go below the to
Add an off-by-default configuration option to use a global stack cookie
instead of the default TLS. This configuration option will only be used
with PIE binaries.
For kernel stack cookie, the compiler uses the mcmodel=kernel to switch
between the fs segment to gs segment. A PIE binary does not use
With PIE support and KASLR extended range, the modules may be further
away from the kernel than before breaking mcmodel=kernel expectations.
Add an option to build modules with mcmodel=large. The modules generated
code will make no assumptions on placement in memory.
Despite this option, modules
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
arch/x86/power/hibernate_asm_
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
arch/x86/entry/entry_64.S | 2
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
arch/x86/kernel/acpi/wakeup_6
if PIE is enabled, switch the paravirt assembly constraints to be
compatible. The %c/i constrains generate smaller code so is kept by
default.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garni
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
arch/x86/crypto/aes-x86_64-as
Perpcu uses a clever design where the .percu ELF section has a virtual
address of zero and the relocation code avoid relocating specific
symbols. It makes the code simple and easily adaptable with or without
SMP support.
This design is incompatible with PIE because generated code always try to
acc
Replace the %c constraint with %P. The %c is incompatible with PIE
because it implies an immediate value whereas %P reference a symbol.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible. Use the new _ASM_GET_PTR macro instead of
the 'mov $symbol, %dst' construct to not have an absolute reference.
Position Independent Executable (PIE) support will allow to extended the
KASLR ran
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible. The new __ASM_GET_PTR_PRE macro is used to
get the address of a symbol on both 32 and 64-bit with PIE support.
Position Independent Executable (PIE) support will allow to extended the
KASLR ran
Change the assembly code to use the new _ASM_GET_PTR macro which get a
symbol reference while being PIE compatible. Modify the RELOC macro that
was using an assignment generating a non-relative reference.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization
Changes:
- v2:
- Add support for global stack cookie while compiler default to fs without
mcmodel=kernel
- Change patch 7 to correctly jump out of the identity mapping on kexec load
preserve.
These patches make the changes necessary to build the kernel as Position
Independent Exec
Replace the %c constraint with %P. The %c is incompatible with PIE
because it implies an immediate value whereas %P reference a symbol.
Position Independent Executable (PIE) support will allow to extended the
KASLR randomization range below the -2G memory limit.
Signed-off-by: Thomas Garnier
---
They don't belong there. Removing them causes build errors in several
places. Add the forward declarations in those places.
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
On Wed, Aug 02, 2017 at 09:07:54AM -0600, Jan Beulich wrote:
> >>> Roger Pau Monne 06/30/17 5:01 PM >>>
> >Note that accesses to the Table Offset, Table BIR, PBA Offset and PBA
> >BIR are not trapped by Xen at the moment.
>
> They're mandated r/o by the spec anyway.
>
> >@@ -113,6 +148,35 @@ st
On Thu, Aug 10, 2017 at 03:00:56PM +0100, Anthony PERARD wrote:
> On Wed, Aug 09, 2017 at 06:34:43PM +0200, Sander Eikelenboom wrote:
> > L.S.,
> >
> > It seems the xen qemu-upstream tree got updated from qemu upstream last
> > week.
> > Unfortunately a change breaks pci-passthrough for HVM's:
>
flight 112559 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112559/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
build-arm64-pvops 2 hos
On Wed, Aug 09, 2017 at 09:06:14AM +0200, Juergen Gross wrote:
> Currently parameters of the hypervisor (e.g. console log level) can be
> set via boot command line. Instead of having to reboot the system in
> case another setting is desired, being able to modify many of those
> parameters at runtim
On Thu, Aug 10, 2017 at 02:24:04PM +0100, Wei Liu wrote:
> They don't belong there. Removing them causes build error in compat.h.
> Add a struct domain declaration there because including sched.h
> doesn't work.
>
> Signed-off-by: Wei Liu
Unfortunately this version is broken on ARM. I will send
On Thu, Aug 10, 2017 at 05:11:52PM +0100, Julien Grall wrote:
>
>
> On 10/08/17 17:00, Wei Liu wrote:
> > On Thu, Aug 10, 2017 at 03:26:07PM +0100, Julien Grall wrote:
> > >
> > >
> > > On 09/08/17 11:58, Bhupinder Thakur wrote:
> > > > Hi Julien,
> > >
> > > Hi Bhupinder,
> > >
> > > > Thank
On Wed, Aug 09, 2017 at 09:07:06AM +0200, Juergen Gross wrote:
> Support modifying conswitch, console_timestamps, loglvl and
> guest_loglvl at runtime.
>
> Cc: Andrew Cooper
> Cc: George Dunlap
> Cc: Ian Jackson
> Cc: Jan Beulich
> Cc: Konrad Rzeszutek Wilk
> Cc: Stefano Stabellini
> Cc: Tim
flight 112558 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112558/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm6 xen-buildfail REGR. vs. 112539
build-i386
On Wed, Aug 09, 2017 at 09:07:05AM +0200, Juergen Gross wrote:
> Add a new xl command "set-parameters" to set hypervisor parameters at
> runtime similar to boot time parameters via command line.
>
> Cc: Ian Jackson
> Cc: Wei Liu
> Signed-off-by: Juergen Gross
Acked-by: Wei Liu
__
On Thu, Aug 10, 2017 at 02:52:52PM +0200, Juergen Gross wrote:
> Xen's paravirt patch function xen_patch() does some special casing for
> irq_ops functions to apply relocations when those functions can be
> patched inline instead of calls.
>
> Unfortunately none of the special case function replac
On Thu, Aug 10, 2017 at 06:24:53PM +0200, Peter Zijlstra wrote:
> -ENTRY(xen_irq_enable_direct)
> - FRAME_BEGIN
> - /* Unmask events */
> - movb $0, PER_CPU_VAR(xen_vcpu_info) + XEN_vcpu_info_mask
> -
> - /*
> - * Preempt here doesn't matter because that will deal with any
> -
On Wed, Aug 09, 2017 at 09:07:04AM +0200, Juergen Gross wrote:
> Add a new libxl function to set hypervisor parameters at runtime
> similar to boot time parameters via command line.
>
> Cc: Ian Jackson
> Cc: Wei Liu
> Signed-off-by: Juergen Gross
> ---
> tools/libxl/libxl.c | 14 ++
Hi Andre,
On 21/07/17 20:59, Andre Przywara wrote:
Currently there is a gic_raise_inflight_irq(), which serves the very
special purpose of handling a newly injected interrupt while an older
one is still handled. This has only one user, in vgic_vcpu_inject_irq().
Now with the introduction of the
On Wed, Aug 09, 2017 at 09:07:03AM +0200, Juergen Gross wrote:
> Add a new libxc function to set hypervisor parameters at runtime
> similar to boot time parameters via command line.
>
> Cc: Ian Jackson
> Cc: Wei Liu
> Signed-off-by: Juergen Gross
Acked-by: Wei Liu
___
On Thu, Aug 10, 2017 at 02:52:52PM +0200, Juergen Gross wrote:
> Xen's paravirt patch function xen_patch() does some special casing for
> irq_ops functions to apply relocations when those functions can be
> patched inline instead of calls.
>
> Unfortunately none of the special case function replac
flight 112552 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112552/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xtf 11ae3010a30c89a6aef762dd03727a5b49e9d8d8
baseline version:
xtf 0e04400b8575048ed0b10e
On Wed, Aug 09, 2017 at 09:07:01AM +0200, Juergen Gross wrote:
> Add the needed infrastructure for runtime parameter changing similar
> to that used at boot time via cmdline. We are using the same parsing
> functions as for cmdline parsing, but with a different array of
> parameter definitions.
>
On 10/08/17 17:00, Wei Liu wrote:
On Thu, Aug 10, 2017 at 03:26:07PM +0100, Julien Grall wrote:
On 09/08/17 11:58, Bhupinder Thakur wrote:
Hi Julien,
Hi Bhupinder,
Thanks for the testing.
On 8 August 2017 at 21:29, Julien Grall wrote:
Hi Bhupinder,
I gave another and I have a couple
On 10/08/17 16:33, Volodymyr Babchuk wrote:
Hi Julien,
On 09.08.17 13:10, Julien Grall wrote:
Hi Volodymyr,
CC "THE REST" maintainers to get an opinion on the public headers.
On 08/08/17 21:08, Volodymyr Babchuk wrote:
SMCCC (SMC Call Convention) describes how to handle both HVCs and SMCs.
On Wed, Aug 09, 2017 at 09:07:00AM +0200, Juergen Gross wrote:
> In order to support generic parameter parsing carve out the parser from
> _cmdline_parse(). As this generic function might be called after boot
> remove the __init annotations from all called sub-functions.
>
> Cc: Andrew Cooper
> C
On Thu, Aug 10, 2017 at 03:26:07PM +0100, Julien Grall wrote:
>
>
> On 09/08/17 11:58, Bhupinder Thakur wrote:
> > Hi Julien,
>
> Hi Bhupinder,
>
> > Thanks for the testing.
> >
> > On 8 August 2017 at 21:29, Julien Grall wrote:
> > > Hi Bhupinder,
> > >
> > > I gave another and I have a cou
flight 112544 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112544/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-libvirt-xsm 1 build-check(1) blocked n/a
test-arm64-arm64-xl 1 build-che
On Thu, Aug 10, 2017 at 03:31:57PM +0100, Julien Grall wrote:
> Hi,
>
> On 10/08/17 14:01, Wei Liu wrote:
> > On Thu, Aug 10, 2017 at 01:40:07PM +0100, Julien Grall wrote:
> > > Hi Wei,
> > >
> > > On 10/08/17 12:40, Wei Liu wrote:
> > > > On Thu, Aug 10, 2017 at 01:29:04PM +0530, Bhupinder Thaku
Hi,
On 21/07/17 20:59, Andre Przywara wrote:
Currently we protect the pending_irq structure with the corresponding
VGIC VCPU lock. There are problems in certain corner cases (for
instance if an IRQ is migrating), so let's introduce a per-IRQ lock,
which will protect the consistency of this struc
Hi Julien,
On 09.08.17 13:10, Julien Grall wrote:
Hi Volodymyr,
CC "THE REST" maintainers to get an opinion on the public headers.
On 08/08/17 21:08, Volodymyr Babchuk wrote:
SMCCC (SMC Call Convention) describes how to handle both HVCs and SMCs.
SMCCC states that both HVC and SMC are valid c
On 10/08/17 17:28, Shai Fultheim (s...@scalemp.com) wrote:
> NACK. This is needed and used by thousands of installations.
Okay, thanks for reacting so fast. Will drop the patch.
Juergen
>
>
>
> Shai Fultheim | M +1 (408) 480-1612 | E s
NACK. This is needed and used by thousands of installations.
Shai Fultheim | M +1 (408) 480-1612 | E s...@scalemp.com
This email message and any attachments to it are ScaleMP confidential
information.
-Original Message-
From: In
Hi Andre,
On 21/07/17 20:59, Andre Przywara wrote:
Currently we protect the pending_irq structure with the corresponding
VGIC VCPU lock. There are problems in certain corner cases (for
instance if an IRQ is migrating), so let's introduce a per-IRQ lock,
which will protect the consistency of this
Hi,
On 10/08/17 15:27, Oleksandr Tyshchenko wrote:
On Tue, Aug 8, 2017 at 2:34 PM, Julien Grall wrote:
On 26/07/17 16:09, Oleksandr Tyshchenko wrote:
@@ -355,6 +557,10 @@ static struct hw_register
*root_pgtable[IPMMU_CTX_MAX] = {
static bool ipmmu_is_root(struct ipmmu_vmsa_device *mmu)
{
+
On 07/31/2017 06:57 PM, Stefano Stabellini wrote:
> Hi all,
>
> this series introduces the frontend for the newly introduced PV Calls
> procotol.
>
> PV Calls is a paravirtualized protocol that allows the implementation of
> a set of POSIX functions in a different domain. The PV Calls frontend
> se
flight 112554 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112554/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
build-arm64-pvops 2 hos
On 06/28/2017 07:16 AM, Andrew Cooper wrote:
Signed-off-by: Andrew Cooper
Acked-by: Daniel De Graaf
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
Hi,
On 10/08/17 14:01, Wei Liu wrote:
On Thu, Aug 10, 2017 at 01:40:07PM +0100, Julien Grall wrote:
Hi Wei,
On 10/08/17 12:40, Wei Liu wrote:
On Thu, Aug 10, 2017 at 01:29:04PM +0530, Bhupinder Thakur wrote:
Hi Wei,
On 9 August 2017 at 16:33, Wei Liu wrote:
On Wed, Aug 09, 2017 at 04:28:1
Hi, Julien
On Tue, Aug 8, 2017 at 2:34 PM, Julien Grall wrote:
> Hi,
>
> On 26/07/17 16:09, Oleksandr Tyshchenko wrote:
>>
>> From: Oleksandr Tyshchenko
>>
>> Modify the Linux IPMMU driver to be functional inside Xen.
>> All devices within a single Xen domain must use the same
>> IOMMU context n
On 09/08/17 11:58, Bhupinder Thakur wrote:
Hi Julien,
Hi Bhupinder,
Thanks for the testing.
On 8 August 2017 at 21:29, Julien Grall wrote:
Hi Bhupinder,
I gave another and I have a couple of comments.
Booting Linux with earlycon enabled take quite a while. I can see the
characters comi
flight 112547 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112547/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm6 xen-buildfail REGR. vs. 112539
build-i386
flight 112543 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/112543/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-localmigrate/x10 fail REGR. vs.
112456
Tests which
On 10/08/17 15:09, Daniel De Graaf wrote:
> On 08/10/2017 09:17 AM, Andrew Cooper wrote:
>> avc_current_has_perm() takes 4 arguments, not 3. Spotted by a Travis
>> randconfig run which actually turned XSM on.
>>
>> Signed-off-by: Andrew Cooper
>
> Whoops, looks like I sent the non-build-tested pa
On 08/10/2017 09:17 AM, Andrew Cooper wrote:
avc_current_has_perm() takes 4 arguments, not 3. Spotted by a Travis
randconfig run which actually turned XSM on.
Signed-off-by: Andrew Cooper
Whoops, looks like I sent the non-build-tested patch by accident.
Thanks for catching this!
Acked-by: D
On Wed, Aug 09, 2017 at 06:34:43PM +0200, Sander Eikelenboom wrote:
> L.S.,
>
> It seems the xen qemu-upstream tree got updated from qemu upstream last week.
> Unfortunately a change breaks pci-passthrough for HVM's:
> libxl: error: libxl_qmp.c:287:qmp_handle_error_response: Domain
> 20:rece
On Wed, 2017-08-09 at 19:34 +0200, Dario Faggioli wrote:
> On Mon, 2017-08-07 at 02:54 -0600, Jan Beulich wrote:
> > > > > Dario Faggioli 07/27/17 10:01 AM
> > > +/*
> > > + * Timer for making sure the CPU where a callback is queued does
> > > + * periodically poke rcu_pedning(), so that it will i
Hello All,
I am struggling with fixing the allocation of pages to some known physical
pages used for mapping and granting access between guests.
I want to fix the allocation of pages i.e. their frame numbers to be be mapped
to fixed physical pages. I only want to do this for pages shared betwee
Hello All,
I am struggling with fixing the allocation of pages to some known physical
pages used for mapping and granting access between guests.
I want to fix the allocation of pages i.e. their frame numbers to be be mapped
to fixed physical pages. I only want to do this for pages shared betwee
On Thu, Aug 10, 2017 at 01:24:27PM +0200, Juergen Gross wrote:
> When the record length for sending the p2m frames in a migration
> stream is too large, the issued error message is not very helpful:
>
> xc: Record (0x0003, x86 PV P2M frames) length 0x8 exceeds max
> (0x80): Internal er
On Thu, Aug 10, 2017 at 03:24:05PM +0200, Juergen Gross wrote:
> On 10/08/17 15:02, Wei Liu wrote:
> > On Wed, Aug 09, 2017 at 09:06:53AM +0200, Juergen Gross wrote:
> >> Where possible check validity of parameters in _cmdline_parse() and
> >> issue a warning message in case of an error detected.
>
>>> On 10.08.17 at 13:09, wrote:
> On my SKL/KBL machine, upstream 4.12 kernel dom0 couldn't boot up using
> xen.efi which is xen 4.9
>
>
> (1) Upstream 4.11 kernel doesn't have such issue.
>
> (2) Upstream 4.12 kernel on my native uefi machine could boot up.
>
> After some debug, I
On 10/08/17 15:32, Jan Beulich wrote:
On 10.08.17 at 15:24, wrote:
>> @@ -176,7 +200,8 @@ int __init parse_bool(const char *s)
>> !strcmp("on", s) ||
>> !strcmp("true", s) ||
>> !strcmp("enable", s) ||
>> - !strcmp("1", s) )
>> + !strcmp("1", s) |
>>> On 10.08.17 at 15:24, wrote:
> They don't belong there. Removing them causes build error in compat.h.
> Add a struct domain declaration there because including sched.h
> doesn't work.
>
> Signed-off-by: Wei Liu
Acked-by: Jan Beulich
___
Xen-de
>>> On 10.08.17 at 15:24, wrote:
> @@ -176,7 +200,8 @@ int __init parse_bool(const char *s)
> !strcmp("on", s) ||
> !strcmp("true", s) ||
> !strcmp("enable", s) ||
> - !strcmp("1", s) )
> + !strcmp("1", s) ||
> + !strcmp("", s) )
But not strcm
They don't belong there. Removing them causes build error in compat.h.
Add a struct domain declaration there because including sched.h
doesn't work.
Signed-off-by: Wei Liu
---
Cc: Andrew Cooper
Cc: George Dunlap
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Konrad Rzeszutek Wilk
Cc: Stefano Stabellini
On 10/08/17 15:02, Wei Liu wrote:
> On Wed, Aug 09, 2017 at 09:06:53AM +0200, Juergen Gross wrote:
>> Where possible check validity of parameters in _cmdline_parse() and
>> issue a warning message in case of an error detected.
>>
>> Cc: Andrew Cooper
>> Cc: George Dunlap
>> Cc: Ian Jackson
>> Cc
On 10/08/17 14:17, Andrew Cooper wrote:
> avc_current_has_perm() takes 4 arguments, not 3. Spotted by a Travis
> randconfig run which actually turned XSM on.
Sorry - I intended to add this link to the commit message.
~Andrew
https://travis-ci.org/xen-project/xen/jobs/263063220
>
> Signed-off-b
1 - 100 of 151 matches
Mail list logo
