This run is configured for baseline tests only.
flight 75516 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75516/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm
flight 128977 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128977/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ws16-amd64 16 guest-localmigrate/x10 fail in 128966
REGR. vs. 128900
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict
testid xen-boot
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.xen.org
On Fri, 26 Oct 2018, Julien Grall wrote:
> On 10/26/18 10:27 PM, Julien Grall wrote:
> > Hi,
> >
> > On 10/26/18 10:12 PM, Stefano Stabellini wrote:
> > > On Fri, 26 Oct 2018, Julien Grall wrote:
> > > > Hi Stefano,
> > > >
> > > > On 10/23/18 3:02 AM, Stefano Stabellini wrote:
> > > > > Make sur
On Fri, 26 Oct 2018, Julien Grall wrote:
> Hi Stefano,
>
> On 10/23/18 3:02 AM, Stefano Stabellini wrote:
> > @@ -314,12 +312,12 @@ static void __init early_print_info(void)
> >mi->bank[i].start + mi->bank[i].size - 1);
> > printk("\n");
> > for ( i = 0 ; i < mo
This run is configured for baseline tests only.
flight 75515 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75515/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm
On 10/26/18 1:49 PM, Andrii Anisov wrote:
Hello Julien
Hi,
On 25.10.18 17:11, Andrii Anisov wrote:
I guess I should make a dedicated patch applicable to mainline to reveal
the issue. I hope I'll do this nearest days.
Please find below the diff applicable to the current xenbits/smoke whic
flight 129014 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129014/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf f157f97301cc2c573977e624f859db93442ff2d5
baseline version:
ovmf b28d406b5a3b1506ce75f
> -Original Message-
> From: Jan Beulich
> Sent: Friday, October 26, 2018 7:16 AM
> To: Daniel de Graaf
> Cc: Andrew Cooper ; xen-de...@lists.xen.org
> Subject: [Non-DoD Source] Ping: Re: Flask default policy mismatch vs dummy
>
> >>> On 11.10.18 at 13:40, wrote:
> On 11.10.18 at 1
On 10/26/18 10:27 PM, Julien Grall wrote:
Hi,
On 10/26/18 10:12 PM, Stefano Stabellini wrote:
On Fri, 26 Oct 2018, Julien Grall wrote:
Hi Stefano,
On 10/23/18 3:02 AM, Stefano Stabellini wrote:
Make sure to only look for multiboot compatible nodes only under
/chosen, not under any other pa
Hi,
On 10/26/18 10:12 PM, Stefano Stabellini wrote:
On Fri, 26 Oct 2018, Julien Grall wrote:
Hi Stefano,
On 10/23/18 3:02 AM, Stefano Stabellini wrote:
Make sure to only look for multiboot compatible nodes only under
/chosen, not under any other paths (depth <= 3).
Signed-off-by: Stefano Sta
flight 128973 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128973/
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. 128955
test-armhf-armhf-
On Fri, 26 Oct 2018, Julien Grall wrote:
> Hi Stefano,
>
> On 10/23/18 3:02 AM, Stefano Stabellini wrote:
> > Make sure to only look for multiboot compatible nodes only under
> > /chosen, not under any other paths (depth <= 3).
> >
> > Signed-off-by: Stefano Stabellini
> >
> > ---
> >
> > Chan
On Fri, 26 Oct 2018, Julien Grall wrote:
> Hi Stefano,
>
> On 10/25/18 5:15 PM, Stefano Stabellini wrote:
> > On Thu, 25 Oct 2018, Julien Grall wrote:
> > > Hi Stefano,
> > >
> > > On 10/24/18 1:24 AM, Stefano Stabellini wrote:
> > > > On Tue, 23 Oct 2018, Milan Boberic wrote:
> > > > I don't hav
On Thu, Oct 25, 2018 at 03:22:17AM -0600, Jan Beulich wrote:
> >>> On 15.10.18 at 13:19, wrote:
> > On Fri, Oct 12, 2018 at 08:14:36AM -0600, Jan Beulich wrote:
> >> >>> On 04.10.18 at 17:43, wrote:
> >> > It is used by PV code only.
> >>
> >> And wrongly so - the same is needed for a PVH Dom0 a
Hi Stefano,
On 10/23/18 3:02 AM, Stefano Stabellini wrote:
@@ -314,12 +312,12 @@ static void __init early_print_info(void)
mi->bank[i].start + mi->bank[i].size - 1);
printk("\n");
for ( i = 0 ; i < mods->nr_mods; i++ )
-printk("MODULE[%d]: %"PRIpaddr" -
flight 129016 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129016/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
Hi Stefano,
On 10/23/18 3:02 AM, Stefano Stabellini wrote:
Make sure to only look for multiboot compatible nodes only under
/chosen, not under any other paths (depth <= 3).
Signed-off-by: Stefano Stabellini
---
Changes in v5:
- add patch
- add check on return value of fdt_get_path
---
xen/
Hi Stefano,
On 10/25/18 5:15 PM, Stefano Stabellini wrote:
On Thu, 25 Oct 2018, Julien Grall wrote:
Hi Stefano,
On 10/24/18 1:24 AM, Stefano Stabellini wrote:
On Tue, 23 Oct 2018, Milan Boberic wrote:
I don't have any other things to suggest right now. You should be able
to measure an overall
Hi Stefano,
On 10/26/18 7:04 PM, Stefano Stabellini wrote:
From: Stefano Stabellini
xen_create_contiguous_region has now only an implementation if
CONFIG_XEN_PV is defined. However, on ARM we never set CONFIG_XEN_PV but
we do have an implementation of xen_create_contiguous_region which is
requ
This run is configured for baseline tests only.
flight 75510 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75510/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm
Hi Stefano,
On 10/15/18 12:03 AM, Stefano Stabellini wrote:
Backport commit 3714ce1d6655098ee69ede632883e5874d67e4ab
"iommu/arm-smmu: Disable stalling faults for all endpoints" from the
Linux kernel.
Original commit message:
Enabling stalling faults can result in hardware deadlock on poorly
On Fri, Oct 26, 2018 at 03:55:32PM +, Paul Durrant wrote:
> > -Original Message-
> > From: Jan Beulich [mailto:jbeul...@suse.com]
> > Sent: 25 October 2018 11:29
> > To: Brian Woods ; Paul Durrant
> >
> > Cc: Suravee Suthikulpanit ; xen-devel > de...@lists.xenproject.org>
> > Subject:
From: Stefano Stabellini
xen_create_contiguous_region has now only an implementation if
CONFIG_XEN_PV is defined. However, on ARM we never set CONFIG_XEN_PV but
we do have an implementation of xen_create_contiguous_region which is
required for swiotlb-xen to work correctly (although it just sets
On Fri, 26 Oct 2018, Juergen Gross wrote:
> On 16/10/2018 10:38, Stefano Stabellini wrote:
> > xen_create_contiguous_region has now only an implementation if
> > CONFIG_XEN_PV is defined. However, on ARM we never set CONFIG_XEN_PV but
> > we do have an implementation of xen_create_contiguous_region
flight 75509 distros-debian-jessie real [real]
http://osstest.xensource.com/osstest/logs/75509/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-pvopsbroken
build-i386
On 10/26/2018 03:02 PM, Ian Jackson wrote:
> George Dunlap writes ("[PATCH 4/5] tools/dm_depriv: Add first cut RLIMITs"):
>> Limit the ability of a potentially compromised QEMU to consume system
>> resources. Key limits:
>> - RLIMIT_FSIZE (file size): 256KiB
>> - RLIMIT_NPROC (after uid changes
flight 129011 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129011/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
On 10/26/2018 03:00 PM, Ian Jackson wrote:
> Thanks, just tiny comments on this.
>
> George Dunlap writes ("[PATCH 3/5] tools/dm_restrict: Unshare mount and IPC
> namespaces on Linux"):
>> diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c
>> index 385643b52c..702ea75149 100644
>> --- a
On 25/09/2018 14:28, Jan Beulich wrote:
> To allow for some code sharing where possible, copy VEX.L into EVEX.LR
> even for VEX (or XOP) encoded insns. Make operand size determination
> use this right away, at the same time adding consistency checks for the
> EVEX scalar insn cases (the non-scalar
>>> On 19.10.18 at 16:28, wrote:
> @@ -1337,8 +1339,15 @@ static int fixup_page_fault(unsigned long addr, struct
> cpu_user_regs *regs)
> {
> if ( !(regs->error_code & (PFEC_user_mode | PFEC_reserved_bit)) &&
> (addr >= GDT_LDT_VIRT_START) && (addr < GDT_LDT_VIRT_END)
On 26/10/2018 16:01, Jan Beulich wrote:
On 26.10.18 at 16:51, wrote:
>> On 26/10/2018 15:37, Jan Beulich wrote:
>> On 26.10.18 at 16:22, wrote:
On 26/10/2018 14:31, Jan Beulich wrote:
On 15.10.18 at 12:36, wrote:
>> --- a/xen/arch/x86/domain.c
>> +++ b/xen/arch/x86
>>> On 19.10.18 at 16:28, wrote:
> This function is called by both PV and HVM. Unfortunately the code is
> very convoluted. We can reason that code between the call to
> hvm_set_info_guest and out label is PV only. Put that portion under
> CONFIG_PV.
>
> Signed-off-by: Wei Liu
Acked-by: Jan Beu
>>> On 19.10.18 at 16:28, wrote:
> Start by putting hypercall handlers which are supposed to be PV only
> under CONFIG_PV. Shuffle some code around to avoid introducing
> excessive numbers of CONFIG_PV.
>
> Signed-off-by: Wei Liu
Acked-by: Jan Beulich
___
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 25 October 2018 11:29
> To: Brian Woods ; Paul Durrant
>
> Cc: Suravee Suthikulpanit ; xen-devel de...@lists.xenproject.org>
> Subject: Re: [Xen-devel] [PATCH] amd-iommu: get rid of pointless
> IOMMU_PAGING_MODE_L
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 26 October 2018 16:46
> To: Paul Durrant
> Cc: Julien Grall ; Andrew Cooper
> ; George Dunlap ; Wei
> Liu ; Ian Jackson ; Jun
> Nakajima ; Kevin Tian ;
> Stefano Stabellini ; xen-devel de...@lists.xenproject.org>;
On Fri, Oct 26, 2018 at 09:48:39AM -0600, Jan Beulich wrote:
> >>> On 24.10.18 at 11:47, wrote:
> > On Wed, Oct 24, 2018 at 09:19:06AM +, Alexandru Stefan ISAILA wrote:
> >> The may_defer var was left with the older bool_t type. This patch
> >> changes the type to bool.
> >>
> >> Signed-off-b
>>> On 24.10.18 at 11:47, wrote:
> On Wed, Oct 24, 2018 at 09:19:06AM +, Alexandru Stefan ISAILA wrote:
>> The may_defer var was left with the older bool_t type. This patch
>> changes the type to bool.
>>
>> Signed-off-by: Alexandru Isaila
>
> Reviewed-by: Wei Liu
Acked-by: Jan Beulich
>>> On 17.10.18 at 10:19, wrote:
> @@ -781,28 +765,9 @@ guest_physmap_add_entry(struct domain *d, gfn_t gfn,
> mfn_t mfn,
> int rc = 0;
>
> if ( !paging_mode_translate(d) )
> -{
> -if ( need_iommu_pt_sync(d) && t == p2m_ram_rw )
> -{
> -dfn_t dfn = _dfn
From: Cleber Rosa
Signed-off-by: Cleber Rosa
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20181004161852.11673-8-cr...@redhat.com>
Signed-off-by: Laurent Vivier
---
scripts/decodetree.py | 2 --
1 file changed, 2 deletions(-)
diff --git a/scripts/decodetree.py b/scripts/decodetree.py
ind
From: Philippe Mathieu-Daudé
Patch created mechanically by rerunning:
$ spatch --sp-file scripts/coccinelle/round.cocci \
--macro-file scripts/cocci-macro-file.h \
--dir . --in-place
Signed-off-by: Philippe Mathieu-Daudé
Acked-by: Michael S. Tsirkin
Message-Id: <201
From: Philippe Mathieu-Daudé
TYPE_XEN_PT_DEVICE is a subclass of TYPE_PCI_DEVICE, the clean way
to access the PCIDevice pointer is using the PCI_DEVICE() macro.
Suggested-by: Peter Maydell
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Markus Armbruster
Acked-by: Anthony PERARD
Acked-by:
From: Stefan Weil
Fix also a grammar issue.
Signed-off-by: Stefan Weil
Reviewed-by: Alex Bennée
Message-Id: <20180713054755.23323-1...@weilnetz.de>
Signed-off-by: Laurent Vivier
---
tests/bios-tables-test.c | 2 +-
tests/docker/Makefile.include | 2 +-
tests/docker/docke
From: Paolo Bonzini
AT24c EEPROM is currently gated by CONFIG_I2C, and as such it is
being included in all emulators that use I2C, even if they do not
really need it. Separate it and, since it was added for the e500
machines, add it to qemu-system-ppc and qemu-system-ppc64.
Signed-off-by: Paolo
From: Philippe Mathieu-Daudé
qemu_log_mask(GUEST_ERROR) is more appropriate:
$ qemu -d help
Log items (comma separated):
guest_errorslog when the guest OS does something invalid (eg accessing a
non-existent register)
Signed-off-by: Philippe Mathieu-Daudé
Acked-by: Michael Walle
Mes
From: Philippe Mathieu-Daudé
Patch created mechanically by rerunning:
$ spatch --sp-file scripts/coccinelle/typecast.cocci \
--macro-file scripts/cocci-macro-file.h \
--dir . --in-place
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Markus Armbruster
Acked-by: M
From: "Emilio G. Cota"
Signed-off-by: Emilio G. Cota
Message-Id: <20180811211011.6277-1-c...@braap.org>
Signed-off-by: Laurent Vivier
---
linux-user/qemu.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/qemu.h b/linux-user/qemu.h
index 1beb6a2cfc..dde3f26f5a 100
From: Philippe Mathieu-Daudé
Patch created mechanically by rerunning:
$ spatch --sp-file scripts/coccinelle/qobject.cocci \
--macro-file scripts/cocci-macro-file.h \
--dir . --in-place
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Markus Armbruster
Acked-by: Mi
From: Stefan Weil
This is needed for builds with the mingw64-* packages from Cygwin,
but also works for Linux.
Move the zlib test also more to the end because users should
get information on the really important missing packages
(which also require zlib) first.
Signed-off-by: Stefan Weil
Revie
The following changes since commit 808ebd66e467f77c0d1f8c6346235f81e9c99cf2:
Merge remote-tracking branch 'remotes/riscv/tags/riscv-for-master-3.1-sf0'
into staging (2018-10-25 17:41:03 +0100)
are available in the Git repository at:
git://github.com/vivier/qemu.git tags/trivial-patches-pull
From: Li Qiang
Signed-off-by: Li Qiang
Reviewed-by: Peter Maydell
Message-Id: <1539080467-2976-1-git-send-email-liq...@gmail.com>
[lv: s/types/typos/]
Signed-off-by: Laurent Vivier
---
include/exec/memory.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/exec
From: Thomas Huth
We don't use CONFIG_PARALLEL_ISA in any of our Makefiles, so this
is just a dead config option which can be removed.
Fixes: a4cb773928e047b137c6998209cf2eec857fac6b
Signed-off-by: Thomas Huth
Acked-by: Richard Henderson
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <154037
From: yuchenlin
Signed-off-by: yuchenlin
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20181022080053.9379-1-yuchen...@synology.com>
Signed-off-by: Laurent Vivier
---
hw/display/vga_int.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/display/vga_int.h b/hw/display/vga_int.h
index 6
From: Cleber Rosa
Point to the right and obvious location for lm32 tests.
Signed-off-by: Cleber Rosa
Reviewed-by: Thomas Huth
Acked-by: Alex Bennée
Message-Id: <20181004161852.11673-3-cr...@redhat.com>
Signed-off-by: Laurent Vivier
---
tests/tcg/README | 2 +-
1 file changed, 1 insertion(+)
From: Li Qiang
Found by reading the code.
Signed-off-by: Li Qiang
Message-Id: <1536150548-2797-1-git-send-email-liq...@gmail.com>
Signed-off-by: Laurent Vivier
---
include/qom/cpu.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/qom/cpu.h b/include/qom/cpu.h
index
From: Cleber Rosa
Commit 990dc39c made all tests executable at the time, but 218 came in
later, and missing those permissions.
Signed-off-by: Cleber Rosa
Message-Id: <20181004161852.11673-4-cr...@redhat.com>
Signed-off-by: Laurent Vivier
---
tests/qemu-iotests/218 | 0
1 file changed, 0 inser
From: Cleber Rosa
Signed-off-by: Cleber Rosa
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20181004161852.11673-11-cr...@redhat.com>
Signed-off-by: Laurent Vivier
---
scripts/qemu.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/qemu.py b/scripts/qemu.py
index
From: Cleber Rosa
The line immediate following a ".. code::" block is considered
to contains arguments to the "code directive". The lack of a
new line gives me during at parse time:
testing.rst:63: (ERROR/3) Error in "code" directive:
maximum 1 argument(s) allowed, 3 supplied.
.. code
From: Philippe Mathieu-Daudé
Patch created mechanically by rerunning:
$ spatch --sp-file scripts/coccinelle/round.cocci \
--macro-file scripts/cocci-macro-file.h \
--dir . --in-place
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Markus Armbruster
Acked-by: Mich
From: Cleber Rosa
Commit cce293a2945 moved some functions from common.config to
common.rc, but the error messages still reference the old file
location.
Signed-off-by: Cleber Rosa
Reviewed-by: Max Reitz
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20181004161852.11673-5-cr...@redhat.com>
On 10/08/2018 05:28 PM, Anthony PERARD wrote:
> On Fri, Oct 05, 2018 at 05:57:01PM +0100, George Dunlap wrote:
>> +# TEST: Process / group id
>> +#
>> +# Read /proc//status, checking Uid and Gid lines
>> +#
>> +# Uid should be xen-qemuuser-range-base+$domid
>> +# Gid should be 65534 ("nobody")
>
>
>>> On 18.10.18 at 12:34, wrote:
> NX support in the host is required for the shadow pagetable code to handle
> SMAP correctly for guests.
>
> Signed-off-by: Andrew Cooper
> ---
> CC: Jan Beulich
> CC: Wei Liu
> CC: Roger Pau Monné
> CC: George Dunlap
> CC: Tim Deegan
>
> RFC because this
>>> On 22.10.18 at 14:58, wrote:
> --- a/xen/common/efi/boot.c
> +++ b/xen/common/efi/boot.c
> @@ -487,6 +487,7 @@ static EFI_FILE_HANDLE __init
> get_parent_handle(EFI_LOADED_IMAGE *loaded_image,
> CHAR16 **leaf)
> {
> static EFI_GUID __init
>>> On 15.10.18 at 12:36, wrote:
> @@ -970,9 +972,13 @@ int arch_set_info_guest(
> v->arch.pv.ctrlreg[4] = cr4 ? pv_guest_cr4_fixup(v, cr4) :
> real_cr4_to_pv_guest_cr4(mmu_cr4_features);
>
> -memset(v->arch.debugreg, 0, sizeof(v->arch.debugreg));
> -for ( i = 0; i < 8; i++
>>> On 26.10.18 at 17:00, wrote:
> On 10/26/18 5:47 PM, Jan Beulich wrote:
> On 23.10.18 at 15:19, wrote:
>>> xen/arch/x86/mm/p2m-ept.c | 8 +
>>> xen/arch/x86/mm/p2m.c | 83
> +++
>>> 2 files changed, 78 insertions(+), 13 deletions(-)
>>
On 10/26/18 5:54 PM, Jan Beulich wrote:
On 23.10.18 at 15:19, wrote:
>> --- a/xen/arch/x86/mm/p2m-ept.c
>> +++ b/xen/arch/x86/mm/p2m-ept.c
>> @@ -1348,6 +1348,8 @@ int ept_p2m_init(struct p2m_domain *p2m)
>> void ept_p2m_uninit(struct p2m_domain *p2m)
>> {
>> struct ept_data *ept = &p2
>>> On 26.10.18 at 16:51, wrote:
> On 26/10/2018 15:37, Jan Beulich wrote:
> On 26.10.18 at 16:22, wrote:
>>> On 26/10/2018 14:31, Jan Beulich wrote:
>>> On 15.10.18 at 12:36, wrote:
> --- a/xen/arch/x86/domain.c
> +++ b/xen/arch/x86/domain.c
> @@ -323,6 +323,18 @@ void free_
On 10/26/18 5:47 PM, Jan Beulich wrote:
On 23.10.18 at 15:19, wrote:
>> xen/arch/x86/mm/p2m-ept.c | 8 +
>> xen/arch/x86/mm/p2m.c | 83
>> +++
>> 2 files changed, 78 insertions(+), 13 deletions(-)
>
> What about p2m-pt.c?
Thank you for
flight 129004 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129004/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf b28d406b5a3b1506ce75fa71c74b489b68a2c11a
baseline version:
ovmf e5001ab7a9c17fe1cf915
>>> On 23.10.18 at 15:19, wrote:
> --- a/xen/arch/x86/mm/p2m-ept.c
> +++ b/xen/arch/x86/mm/p2m-ept.c
> @@ -1348,6 +1348,8 @@ int ept_p2m_init(struct p2m_domain *p2m)
> void ept_p2m_uninit(struct p2m_domain *p2m)
> {
> struct ept_data *ept = &p2m->ept;
> +
> +p2m_free_logdirty(p2m);
Thi
On 26/10/2018 15:37, Jan Beulich wrote:
On 26.10.18 at 16:22, wrote:
>> On 26/10/2018 14:31, Jan Beulich wrote:
>> On 15.10.18 at 12:36, wrote:
--- a/xen/arch/x86/domain.c
+++ b/xen/arch/x86/domain.c
@@ -323,6 +323,18 @@ void free_vcpu_struct(struct vcpu *v)
free
On 10/26/18 1:54 AM, Dongli Zhang wrote:
> If dom0 (or any domain) is happy, although it could try to exchange all its
> continuous dma pages back to xen hypervisor. From the perspective of each
> domain, they always would like to keep as much continuous dma page as
> possible.
>
> I am thinking
>>> On 23.10.18 at 15:19, wrote:
> xen/arch/x86/mm/p2m-ept.c | 8 +
> xen/arch/x86/mm/p2m.c | 83
> +++
> 2 files changed, 78 insertions(+), 13 deletions(-)
What about p2m-pt.c?
> @@ -287,24 +286,47 @@ int p2m_is_logdirty_range(struct p2m_do
Hi Christoph,
On 10/26/18 12:48 AM, Christoph Helwig wrote:
> On Thu, Oct 25, 2018 at 11:56:02AM -0700, Joe Jin wrote:
>> I just discussed this patch with Boris in private, his opinions(Boris,
>> please correct me if any misunderstood) are:
>>
>> 1. With/without the check, both are incorrect, he t
>>> On 26.10.18 at 16:22, wrote:
> On 26/10/2018 14:31, Jan Beulich wrote:
> On 15.10.18 at 12:36, wrote:
>>> --- a/xen/arch/x86/domain.c
>>> +++ b/xen/arch/x86/domain.c
>>> @@ -323,6 +323,18 @@ void free_vcpu_struct(struct vcpu *v)
>>> free_xenheap_page(v);
>>> }
>>>
>>> +/* Initiali
On 25/09/2018 14:27, Jan Beulich wrote:
> Fix an inverted pair of checks, drop an incorrect instance of #UD
> raising for non-64-bit mode, and add further generic checks.
>
> Note: Other than SDM Vol 2 rev 067 states, EVEX.V' is _not_ ignored
"Despite what SDM ..." would be a more normal way of ph
>>> On 23.10.18 at 04:03, wrote:
> @@ -391,31 +394,79 @@ static void dump_console_ring_key(unsigned char key)
> free_xenheap_pages(buf, order);
> }
>
> -/* CTRL- switches input direction between Xen and DOM0. */
> +/*
> + * CTRL- changes input direction, rotating among Xen, Dom0,
> + * and
George Dunlap writes ("Re: [PATCH 5/5] RFC: test/depriv: Add a tool to check
process-level depriv"):
> FYI I do agree with all of those suggestions (both `set -e` and having
> functions to handle failure in a consistent way); but I didn't want to
> fix everything up in bash only to have to write i
On 10/26/2018 03:06 PM, Ian Jackson wrote:
> George Dunlap writes ("[PATCH 5/5] RFC: test/depriv: Add a tool to check
> process-level depriv"):
>> Add a tool to check whether the various process-level deprivileging
>> operations have actually taken place on the process.
> ...
>> NB that a number o
On 26/10/2018 14:31, Jan Beulich wrote:
On 15.10.18 at 12:36, wrote:
>> --- a/xen/arch/x86/domain.c
>> +++ b/xen/arch/x86/domain.c
>> @@ -323,6 +323,18 @@ void free_vcpu_struct(struct vcpu *v)
>> free_xenheap_page(v);
>> }
>>
>> +/* Initialise various registers to their architectural
On Fri, 2018-10-26 at 06:01 -0600, Tamas K Lengyel wrote:
> On Fri, Oct 26, 2018, 1:49 AM Dario Faggioli
> wrote:
> >
> > I haven't done this kind of benchmark yet, but I'd say that, if
> > every
> > vCPU of every domain is doing 100% CPU intensive work, core-
> > scheduling
> > isn't going to ma
This run is configured for baseline tests only.
flight 75507 xen-4.11-testing real [real]
http://osstest.xensource.com/osstest/logs/75507/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64
George Dunlap writes ("[PATCH 5/5] RFC: test/depriv: Add a tool to check
process-level depriv"):
> Add a tool to check whether the various process-level deprivileging
> operations have actually taken place on the process.
...
> NB that a number of other requested changes (such as using `set -e`,
>
George Dunlap writes ("[PATCH 4/5] tools/dm_depriv: Add first cut RLIMITs"):
> Limit the ability of a potentially compromised QEMU to consume system
> resources. Key limits:
> - RLIMIT_FSIZE (file size): 256KiB
> - RLIMIT_NPROC (after uid changes to a unique uid)
Thanks.
> +static struct {
> +
Thanks, just tiny comments on this.
George Dunlap writes ("[PATCH 3/5] tools/dm_restrict: Unshare mount and IPC
namespaces on Linux"):
> diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c
> index 385643b52c..702ea75149 100644
> --- a/tools/libxl/libxl_dm.c
> +++ b/tools/libxl/libxl_dm.c
George Dunlap writes ("[PATCH 2/5] tools/dm_restrict: Ask QEMU to chroot"):
> When dm_restrict is enabled, ask QEMU to chroot into an empty directory.
>
> * Create /var/run/qemu/root-domid (deleting the old one if it's there)
> * Pass the -chroot option to QEMU
>
> Rather than running `rm -rf` on
flight 128972 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128972/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xen-xsm-freebsd broken
build-amd64-xen-freebsd
George Dunlap writes ("[PATCH 1/5] docs/qemu-deprivilege: Revise and update
with status and future plans"):
> docs/qemu-deprivilege.txt had some basic instructions for using
> dm_restrict, but it was incomplete, misleading, and stale.
Thanks for the updates to the unshare stuff.
> +### Device Mo
>>> On 15.10.18 at 12:36, wrote:
> --- a/xen/arch/x86/domain.c
> +++ b/xen/arch/x86/domain.c
> @@ -323,6 +323,18 @@ void free_vcpu_struct(struct vcpu *v)
> free_xenheap_page(v);
> }
>
> +/* Initialise various registers to their architectural INIT/RESET state. */
> +void arch_vcpu_regs_init
In order to have a link to the release notes in the feature list
generated from SUPPORT.md add that link in the "Release Support"
section of that file.
The real link needs to be adapted when the version is being released.
Signed-off-by: Juergen Gross
---
SUPPORT.md
On 26/10/2018 14:11, Jan Beulich wrote:
On 26.10.18 at 13:07, wrote:
>> --- a/SUPPORT.md
>> +++ b/SUPPORT.md
>> @@ -13,6 +13,7 @@ for the definitions of the support status levels etc.
>> Initial-Release: n/a
>> Supported-Until: TBD
>> Security-Support-Until: Unreleased - not ye
>>> On 12.10.18 at 18:37, wrote:
> Furthermore, I believe even #MC is blocked by the MOVSS shadow, because
> the purpose of the shadow is to indicate "my stack is not safe to take
> an exception".
I've just looked at the precise SDM text again, which I see has changed
compared to the prior revisi
Hello Julien
On 25.10.18 17:11, Andrii Anisov wrote:
> I guess I should make a dedicated patch applicable to mainline to reveal
> the issue. I hope I'll do this nearest days.
Please find below the diff applicable to the current xenbits/smoke which
exposes the issue.
With that diff I see (on my
flight 128970 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/128970/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict 7 xen-boot fail REGR. vs.
125898
test-amd64-
Ping? It's been nearly 3 weeks with only minor review for this series.
-George
On 10/05/2018 05:56 PM, George Dunlap wrote:
> docs/qemu-deprivilege.txt had some basic instructions for using
> dm_restrict, but it was incomplete, misleading, and stale.
>
> Update the docs in a number of ways.
>
>>> On 26.10.18 at 14:19, wrote:
> On 26/10/18 12:59, Jan Beulich wrote:
> On 26.10.18 at 13:29, wrote:
>>> On 26/10/18 10:03, Jan Beulich wrote:
>>> On 25.10.18 at 20:32, wrote:
> On 18/09/18 12:53, Jan Beulich wrote:
>> @@ -1187,6 +1188,11 @@ static int _get_fpu(
>>
On 26/10/18 12:59, Jan Beulich wrote:
On 26.10.18 at 13:29, wrote:
>> On 26/10/18 10:03, Jan Beulich wrote:
>> On 25.10.18 at 20:32, wrote:
On 18/09/18 12:53, Jan Beulich wrote:
> @@ -1187,6 +1188,11 @@ static int _get_fpu(
> return X86EMUL_UNHANDLEABLE;
>
Hi Christophe,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on xen-tip/linux-next]
[also build test ERROR on v4.19 next-20181019]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/l
>>> On 26.10.18 at 13:07, wrote:
> --- a/SUPPORT.md
> +++ b/SUPPORT.md
> @@ -13,6 +13,7 @@ for the definitions of the support status levels etc.
> Initial-Release: n/a
> Supported-Until: TBD
> Security-Support-Until: Unreleased - not yet security-supported
> +Release-Notes: n/a
On Fri, Oct 26, 2018, 1:49 AM Dario Faggioli wrote:
> On Thu, 2018-10-25 at 12:35 -0600, Tamas K Lengyel wrote:
> > On Thu, Oct 25, 2018 at 12:13 PM Andrew Cooper
> > wrote:
> > >
> > > TBH, I'd perhaps start with an admin control which lets them switch
> > > between the two modes, and some inst
1 - 100 of 156 matches
Mail list logo
