Re: [Xen-devel] [PATCH V2] x86/p2m: fixed p2m_change_type_range() start / end check

On 04/18/2018 04:12 PM, Razvan Cojocaru wrote: > p2m_change_type_range() handles end > max_mapped_pfn, but not > start > max_mapped_pfn. Check the latter just after grabbing the > lock and bail if true. > > Signed-off-by: Razvan Cojocaru > Suggested-by: George Dunlap

Re: [Xen-devel] [PATCH v2 0/5] ALSA: xen-front: Add Xen para-virtualized frontend driver

On 04/18/2018 06:15 PM, Oleksandr Andrushchenko wrote: On 04/16/2018 09:24 AM, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko Please note: this patch series depends on [3]. The dependency is now merged into Xen kernel tree [4] for-linus-4.17

Re: [Xen-devel] [RFC v2 7/9] libxl_qmp: Implement query-status command

On Mon, Apr 16, 2018 at 06:32:25PM +0100, Anthony PERARD wrote: > It check via QMP if QEMU as reach the intended status. Some typos. "... checks ... if QEMU has reached ..." > > Signed-off-by: Anthony PERARD > --- > tools/libxl/libxl_internal.h | 3 +++ >

Re: [Xen-devel] [Bug 198497] handle_mm_fault / xen_pmd_val / radix_tree_lookup_slot Null pointer

On 20/04/18 17:20, Jason Andryuk wrote: > Adding xen-devel and the Linux Xen maintainers. > > Summary: Some Xen users (and maybe others) are hitting a BUG in > __radix_tree_lookup() under do_swap_page() - example backtrace is > provided at the end. Matthew Wilcox provided a band-aid patch that >

Re: [Xen-devel] [PATCH V2] x86/p2m: fixed p2m_change_type_range() start / end check

>>> On 23.04.18 at 09:23, wrote: > On 04/18/2018 04:12 PM, Razvan Cojocaru wrote: >> p2m_change_type_range() handles end > max_mapped_pfn, but not >> start > max_mapped_pfn. Check the latter just after grabbing the >> lock and bail if true. >> >> Signed-off-by: Razvan

Re: [Xen-devel] [PATCH v2] Input: xen-kbdfront - allow better run-time configuration

On 23/04/18 10:02, Oleksandr Andrushchenko wrote: > Juergen, Jason, Dmitry > any comment on this? Oleksandr, please give us some time. I can't speak for others, but I am not sitting here idling and hoping that some work (e.g. patches to review) might appear. I have a lot of other stuff to do and

Re: [Xen-devel] [PATCH v3] shim: don't let build modify shim.config

On Fri, Apr 20, 2018 at 05:47:55PM +0200, Juergen Gross wrote: > Currently building the shim will modify shim.config in case some config > option was added or modified in the hypervisor. > > Avoid that by copying shim.config to an intermediate file instead. > > Signed-off-by: Juergen Gross

Re: [Xen-devel] [RFC v2 5/9] libxl: Learned to send FD through QMP to QEMU

On Mon, Apr 16, 2018 at 06:32:23PM +0100, Anthony PERARD wrote: > Adding the ability to send a file descriptor from libxl to QEMU via the > QMP interface. This will be use with the "add-fd" QMP command. > > Signed-off-by: Anthony PERARD > --- Acked-by: Wei Liu

Re: [Xen-devel] [PATCH v2] Input: xen-kbdfront - allow better run-time configuration

Juergen, Jason, Dmitry any comment on this? Thank you, Oleksandr On 04/19/2018 04:39 PM, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko It is now only possible to control if multi-touch virtual device is created or not (via the corresponding

Re: [Xen-devel] [PATCH v2] Input: xen-kbdfront - allow better run-time configuration

On 04/23/2018 11:23 AM, Juergen Gross wrote: On 23/04/18 10:02, Oleksandr Andrushchenko wrote: Juergen, Jason, Dmitry any comment on this? Oleksandr, please give us some time. I can't speak for others, but I am not sitting here idling and hoping that some work (e.g. patches to review) might

Re: [Xen-devel] [PATCH 3/8] x86/SVM: Add AVIC vmexit handlers

>>> On 20.04.18 at 22:02, wrote: > On 4/17/2018 7:58 AM, Jan Beulich wrote: > On 04.04.18 at 01:01, wrote: >>> --- a/xen/include/asm-x86/hvm/vlapic.h >>> +++ b/xen/include/asm-x86/hvm/vlapic.h >>> @@ -137,6 +137,10 @@ void vlapic_ipi(struct

[Xen-devel] [PATCH v5] x86/mm: Suppresses vm_events caused by page-walks

This patch is adding a way to enable/disable inguest pagefault events. It introduces the xc_monitor_inguest_pagefault function and adds the inguest_pagefault_disabled in the monitor structure. This is needed by the introspection so it will only get gla faults and not get spammed with other faults.

Re: [Xen-devel] Setting up a call to discuss PCI Emulation - Future Direction

Hi all, so it seems we have no perfect slot proposals, but 2 semi-perfect. May 2nd: 16:00 - 17:00 Christopher can't attend May 2nd: 17:00 - 18:00 Chao can't attend Maybe a compromise would be 16:30 to 17:30 Regards Lars On 21/04/2018, 05:47, "Alexey G" wrote: On Fri, 13

Re: [Xen-devel] [PATCH v2 for-4.11] libxl: fix memory map reported to PVH guests

On Fri, Apr 20, 2018 at 03:57:19PM +0100, Roger Pau Monne wrote: > PVH guests with 4GB of RAM or more get a memory map like the > following: > > 0x00 - 0x00fee0 RAM > 0x00fee0 - 0x01 RESERVED > 0x00fc009000 - 0x00fc009040 ACPI > 0x00fc00 -

[Xen-devel] [distros-debian-sid test] 74636: tolerable FAIL

flight 74636 distros-debian-sid real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/74636/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-i386-i386-sid-netboot-pvgrub 10 debian-di-install fail like 74625

Re: [Xen-devel] RFC Xen signature verification for kexec

>>> On 20.04.18 at 21:12, wrote: > Two options for signature verification in Xen > > This proposal outlines two options under consideration for enhancing > Xen to support signature verification of kexec loaded images. The > first option is essentially to mirror Linux

Re: [Xen-devel] [PATCH 2/3] xen netback: add fault injection facility

On Fri, Apr 20, 2018 at 10:47:31AM +, Stanislav Kinsburskii wrote: > > #include > #include > @@ -1649,6 +1650,7 @@ static int __init netback_init(void) > PTR_ERR(xen_netback_dbg_root)); > #endif /* CONFIG_DEBUG_FS */ > > + (void) xen_netbk_fi_init(); If you

Re: [Xen-devel] [PATCH v5] x86/mm: Suppresses vm_events caused by page-walks

On Mon, Apr 23, 2018 at 11:00:50AM +0300, Alexandru Isaila wrote: > This patch is adding a way to enable/disable inguest pagefault > events. It introduces the xc_monitor_inguest_pagefault function > and adds the inguest_pagefault_disabled in the monitor structure. > This is needed by the

Re: [Xen-devel] osstest outage,

The work is complete and a test job seems to have gone well. I have therefore un-stopped it. The Xen Project osstest is now operational and will start picking up work from the staging branches. Please let me know if you spot anything untoward. Ian.

Re: [Xen-devel] [PATCH v2 04/10] xen/arm: Remove __initdata and __init to enable CPU hotplug

Hi Mirela, On 20/04/18 13:25, Mirela Simonovic wrote: CPU up flow is currently used during the initial boot to start secondary CPUs. However, the same flow should be used for CPU hotplug, e.g. when hotplugging secondary CPUs within the resume procedure (resume from the suspend to RAM).

[Xen-devel] [PATCH-for-4.11] xpti: fix bug in double fault handling

When entering the hypervisor via the double fault handler resetting xen_cr3 was missing. This led to switching to pv_cr3 when returning from the next following interrupt, e.g. after re-enabling interrupts in machine_restart(). Signed-off-by: Juergen Gross ---

Re: [Xen-devel] [PATCH v2 09/10] xen/arm: Free memory allocated for sibling/core maps on CPU hot-unplug

Hi, On 20/04/18 13:25, Mirela Simonovic wrote: The memory allocated in setup_cpu_sibling_map() when a CPU is hotplugged has to be freed when the CPU is hot-unplugged. This is done in remove_cpu_sibling_map() and called from __cpu_disable() on CPU hot-unplug. Signed-off-by: Mirela Simonovic

Re: [Xen-devel] [PATCH V2] x86/p2m: fixed p2m_change_type_range() start / end check

On 04/18/2018 02:12 PM, Razvan Cojocaru wrote: > p2m_change_type_range() handles end > max_mapped_pfn, but not > start > max_mapped_pfn. Check the latter just after grabbing the > lock and bail if true. > > Signed-off-by: Razvan Cojocaru > Suggested-by: George Dunlap

Re: [Xen-devel] [PATCH-for-4.11 v2] xpti: fix bug in double fault handling

On 23/04/18 14:49, Jan Beulich wrote: On 23.04.18 at 14:38, wrote: >> When entering the hypervisor via the double fault handler resetting >> xen_cr3 was missing. This led to switching to pv_cr3 when returning >> from the next following interrupt. So repair this in order to

Re: [Xen-devel] [PATCH-for-4.11 v2] xpti: fix bug in double fault handling

On 23/04/18 13:38, Juergen Gross wrote: > When entering the hypervisor via the double fault handler resetting > xen_cr3 was missing. This led to switching to pv_cr3 when returning > from the next following interrupt. So repair this in order to allow > interrupt handling to work even after a double

Re: [Xen-devel] [PATCH] x86: correct assertion in destroy_perdomain_mapping()

On 20/04/18 16:03, Jan Beulich wrote: > hvm_domain_initialise() may call this with nr being zero, which triggers > the "does not cross L3 boundary" check. > > Signed-off-by: Jan Beulich Acked-by: Andrew Cooper

Re: [Xen-devel] [PATCH-for-4.11 v2] xpti: fix bug in double fault handling

On 23/04/18 15:06, Andrew Cooper wrote: > On 23/04/18 13:38, Juergen Gross wrote: >> When entering the hypervisor via the double fault handler resetting >> xen_cr3 was missing. This led to switching to pv_cr3 when returning >> from the next following interrupt. So repair this in order to allow >>

Re: [Xen-devel] [PATCH] x86: correct assertion in destroy_perdomain_mapping()

On 23/04/18 15:39, Andrew Cooper wrote: > On 20/04/18 16:03, Jan Beulich wrote: >> hvm_domain_initialise() may call this with nr being zero, which triggers >> the "does not cross L3 boundary" check. >> >> Signed-off-by: Jan Beulich > > Acked-by: Andrew Cooper

Re: [Xen-devel] RFC Xen signature verification for kexec

On Mon, Apr 23, 2018 at 12:55:45AM -0600, Jan Beulich wrote: > >>> On 20.04.18 at 21:12, wrote: > > Two options for signature verification in Xen > > > > This proposal outlines two options under consideration for enhancing > > Xen to support signature verification of

Re: [Xen-devel] [PATCH v2 03/10] xen/arm: Implement CPU_OFF PSCI call (physical interface)

Hi Mirela, On 20/04/18 13:25, Mirela Simonovic wrote: During the system suspend to RAM non-boot CPUs will be hotplugged. This will be triggered via disable_nonboot_cpus() call. When hotplugged the CPU will end up in an infinite wfi loop in stop_cpu(). This patch adds PSCI CPU_OFF call to the

Re: [Xen-devel] [PATCH v2 05/10] xen/arm: Setup virtual paging for non-boot CPUs on hotplug/resume

Hi Mirela, On 20/04/18 13:25, Mirela Simonovic wrote: In existing code the paging for non-boot CPUs is setup only on boot. The setup is triggered from start_xen() after all CPUs are brought online. In other words, the initialization of VTCR_EL2 register is done out of the

Re: [Xen-devel] [PATCH v2 10/10] xen/arm: Call check_local_cpu_errata for secondary CPU only on boot

Hi, On 20/04/18 13:25, Mirela Simonovic wrote: Checking CPU errata should be done only when a CPU is initially booted. It is assumed that the CPU which is hotplugged after the system/Xen boots, was initially hotplugged during the system/Xen boot, so errata is checked by each CPU only once, on

Re: [Xen-devel] [PATCH v2 01/10] xen/arm64: Added handling of the trapped access to OSLSR register

Hi Mirela, On 20/04/18 13:25, Mirela Simonovic wrote: Linux/dom0 accesses OSLSR register when saving CPU context during the suspend procedure. Xen traps access to this register, but has no handling for it. Consequently, Xen injects undef exception to linux, causing it to crash. This patch adds

Re: [Xen-devel] [PATCH v2 02/10] xen/arm: Ignore write to GICD_ISACTIVERn registers (vgic-v2)

Hi Mirela, On 20/04/18 13:25, Mirela Simonovic wrote: Guests attempt to write into these registers on resume (for example Linux). Without this patch a data abort exception will be raised to the guest. This patch handles the write access by ignoring it, but only if the value to be written is

Re: [Xen-devel] [PATCH 0/1] drm/xen-zcopy: Add Xen zero-copy helper DRM driver

On Fri, Apr 20, 2018 at 02:25:20PM +0300, Oleksandr Andrushchenko wrote: > > > the gntdev. > > > > > > I think this is generic enough that it could be implemented by a > > > device not tied to Xen. AFAICT the hyper_dma guys also wanted > > > something similar to this. > > You can't just wrap

Re: [Xen-devel] [PATCH-for-4.11] xpti: fix bug in double fault handling

On 23/04/18 14:11, Jan Beulich wrote: On 23.04.18 at 13:37, wrote: >> When entering the hypervisor via the double fault handler resetting >> xen_cr3 was missing. This led to switching to pv_cr3 when returning >> from the next following interrupt, e.g. after re-enabling

Re: [Xen-devel] RFC Xen signature verification for kexec

>>> On 23.04.18 at 12:25, wrote: > On Mon, Apr 23, 2018 at 12:55:45AM -0600, Jan Beulich wrote: >> >>> On 20.04.18 at 21:12, wrote: >> > Two options for signature verification in Xen >> > >> > This proposal outlines two options under

Re: [Xen-devel] [PATCH 0/1] drm/xen-zcopy: Add Xen zero-copy helper DRM driver

On 04/23/2018 02:52 PM, Wei Liu wrote: On Fri, Apr 20, 2018 at 02:25:20PM +0300, Oleksandr Andrushchenko wrote: the gntdev. I think this is generic enough that it could be implemented by a device not tied to Xen. AFAICT the hyper_dma guys also wanted something similar to this. You can't

[Xen-devel] [PATCH-for-4.11 v2] xpti: fix bug in double fault handling

When entering the hypervisor via the double fault handler resetting xen_cr3 was missing. This led to switching to pv_cr3 when returning from the next following interrupt. So repair this in order to allow interrupt handling to work even after a double fault. Signed-off-by: Juergen Gross

Re: [Xen-devel] [PATCH-for-4.11] xpti: fix bug in double fault handling

>>> On 23.04.18 at 14:22, wrote: > On 23/04/18 14:11, Jan Beulich wrote: > On 23.04.18 at 13:37, wrote: >>> --- a/tools/firmware/xen-dir/shim.config >>> +++ b/tools/firmware/xen-dir/shim.config >>> @@ -1,6 +1,6 @@ >>> # >>> # Automatically generated file;

Re: [Xen-devel] [PATCH v2 07/10] xen/arm: Release maintenance interrupt when CPU is hot-unplugged

Hi Mirela, On 20/04/18 13:25, Mirela Simonovic wrote: When a CPU is hot-unplugged the maintenance interrupt has to be released in order to free the memory that was allocated when the CPU was hotplugged and interrupt requested. The interrupt was requested using request_irq() which is called from

Re: [Xen-devel] [PATCH V2] x86/p2m: fixed p2m_change_type_range() start / end check

On 04/23/2018 02:47 PM, George Dunlap wrote: > On 04/18/2018 02:12 PM, Razvan Cojocaru wrote: >> p2m_change_type_range() handles end > max_mapped_pfn, but not >> start > max_mapped_pfn. Check the latter just after grabbing the >> lock and bail if true. >> >> Signed-off-by: Razvan Cojocaru

Re: [Xen-devel] [PATCH-for-4.11 v2] xpti: fix bug in double fault handling

>>> On 23.04.18 at 14:38, wrote: > When entering the hypervisor via the double fault handler resetting > xen_cr3 was missing. This led to switching to pv_cr3 when returning > from the next following interrupt. So repair this in order to allow > interrupt handling to work even

[Xen-devel] [PATCH v3] xpti: fix bug in double fault handling

When entering the hypervisor via the double fault handler resetting xen_cr3 was missing. This led to switching to pv_cr3 when returning from the next following exception, so repair this in order to allow exception handling to work even after a double fault. Signed-off-by: Juergen Gross

[Xen-devel] [xen-unstable-smoke test] 122366: tolerable all pass - PUSHED

flight 122366 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/122366/ 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

Re: [Xen-devel] [PATCH V2] x86/p2m: fixed p2m_change_type_range() start / end check

On 04/23/2018 12:56 PM, Razvan Cojocaru wrote: > On 04/23/2018 02:47 PM, George Dunlap wrote: >> On 04/18/2018 02:12 PM, Razvan Cojocaru wrote: >>> p2m_change_type_range() handles end > max_mapped_pfn, but not >>> start > max_mapped_pfn. Check the latter just after grabbing the >>> lock and bail

Re: [Xen-devel] [PATCH 05/16] xen: defer call to xen_restrict until just before os_setup_post

On Thu, Apr 19, 2018 at 05:45:08PM +0100, Ian Jackson wrote: > We need to restrict *all* the control fds that qemu opens. Looking in > /proc/PID/fd shows there are many; their allocation seems scattered > throughout Xen support code in qemu. > > We must postpone the restrict call until roughly

Re: [Xen-devel] [RFC v2 4/9] libxl_qmp: Move the buffer realloc to the same scope level as read

On Mon, Apr 23, 2018 at 10:03:39AM +0100, Wei Liu wrote: > On Mon, Apr 16, 2018 at 06:32:22PM +0100, Anthony PERARD wrote: > > In qmp_next(), the inner loop should only try to parse messages from > > QMP, if there is more than one. > > > > The handling of the receive buffer ('incomplete'), should

Re: [Xen-devel] [RFC v2 4/9] libxl_qmp: Move the buffer realloc to the same scope level as read

On Mon, Apr 23, 2018 at 03:50:27PM +0100, Anthony PERARD wrote: > On Mon, Apr 23, 2018 at 10:03:39AM +0100, Wei Liu wrote: > > On Mon, Apr 16, 2018 at 06:32:22PM +0100, Anthony PERARD wrote: > > > In qmp_next(), the inner loop should only try to parse messages from > > > QMP, if there is more than

Re: [Xen-devel] [PATCH 03/16] xen: link against xentoolcore

On Thu, Apr 19, 2018 at 05:45:06PM +0100, Ian Jackson wrote: > From: Anthony PERARD > > Xen libraries in 4.10 include a new xentoolcore library. This > contains the xentoolcore_restrict_all function which we are about to > want to use. > > Signed-off-by: Ian Jackson

Re: [Xen-devel] [PATCH v3] xpti: fix bug in double fault handling

>>> On 23.04.18 at 15:59, wrote: > When entering the hypervisor via the double fault handler resetting > xen_cr3 was missing. This led to switching to pv_cr3 when returning > from the next following exception, so repair this in order to allow > exception handling to work even

Re: [Xen-devel] [PATCH v3] xpti: fix bug in double fault handling

On 23/04/18 14:59, Juergen Gross wrote: > When entering the hypervisor via the double fault handler resetting > xen_cr3 was missing. This led to switching to pv_cr3 when returning > from the next following exception, so repair this in order to allow > exception handling to work even after a double

Re: [Xen-devel] Setting up a call to discuss PCI Emulation - Future Direction

On Mon, Apr 23, 2018 at 08:26:59AM +, Lars Kurth wrote: >Hi all, >so it seems we have no perfect slot proposals, but 2 semi-perfect. >May 2nd: 16:00 - 17:00 Christopher can't attend >May 2nd: 17:00 - 18:00 Chao can't attend >Maybe a compromise would be 16:30 to 17:30 Hi Lars, Your suggestion

Re: [Xen-devel] [PATCH] tools/kdd: silence gcc 8 warning a different way

On Mon, Apr 16, 2018 at 02:43:32PM +0200, Marek Marczykowski wrote: > On Mon, Apr 16, 2018 at 06:00:37AM -0600, Jan Beulich wrote: > > >>> On 16.04.18 at 12:33, wrote: > > > On Thu, Apr 12, 2018 at 06:04:49AM -0600, Jan Beulich wrote: > > >> Older gcc doesn't like "#pragma

Re: [Xen-devel] Setting up a call to discuss PCI Emulation - Future Direction

On Mon, Apr 23, 2018 at 10:12:22PM +0800, Chao Gao wrote: >On Mon, Apr 23, 2018 at 08:26:59AM +, Lars Kurth wrote: >>Hi all, >>so it seems we have no perfect slot proposals, but 2 semi-perfect. >>May 2nd: 16:00 - 17:00 Christopher can't attend >>May 2nd: 17:00 - 18:00 Chao can't attend >>Maybe

[Xen-devel] [OSSTEST PATCH 1/3] ms-queuedaemon: Support infra-priority

This will allow a flight to order the queueing its own test jobs more sensibly without interfering with inter-flight priority. Signed-off-by: Ian Jackson --- README.planner | 1 + ms-queuedaemon | 6 -- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git

[Xen-devel] [OSSTEST PATCH 2/3] ms-planner: include PreviousShare information in Unshare events

We can't put this in $evt->{Share} because existing clients will see it there and assume it means the resource is shared. Signed-off-by: Ian Jackson --- ms-planner | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ms-planner b/ms-planner index af0c746..5d20cc2

[Xen-devel] [OSSTEST PATCH 3/3] ms-planner: Including Unshare event for previous sharing state

Arrange for the initial plan to contain an Unshare event for resources which are unallocated, but currently recorded as shared (ie, they might be ready for reuse). Specifically, we need to: * Include the Wear in the information for a host with no unallocatable shares (since the consumers

[Xen-devel] [OSSTEST PATCH 0/3] ms-*: Support for host reuse

These three patches help support within-flight test hose reuse. Currently there is nothing that uses these new features in any public branch. I have a private branch with the client side, which has seen some testing and which I hope will be ready soon. These daemon changes have been in

Re: [Xen-devel] [RFC 0/2] To introduce xenwatch multithreading (xen mtwatch)

On Sat, Apr 07, 2018 at 07:25:53PM +0800, Dongli Zhang wrote: > About per-domU xenwatch thread create/destroy, a new type of xenstore node is > introduced: '/local/domain/0/mtwatch/'. > > Suppose the new domid id 7. During the domU (domid=7) creation, the xen > toolstack writes

Re: [Xen-devel] Setting up a call to discuss PCI Emulation - Future Direction

Alright: 17:00-18:00 it is. I will send out a separate mail with call-in details Lars On 23/04/2018, 15:24, "Chao Gao" wrote: On Mon, Apr 23, 2018 at 10:12:22PM +0800, Chao Gao wrote: >On Mon, Apr 23, 2018 at 08:26:59AM +, Lars Kurth wrote: >>Hi all,

Re: [Xen-devel] [PATCH V2] x86/p2m: fixed p2m_change_type_range() start / end check

On 04/23/2018 05:28 PM, George Dunlap wrote: > On 04/23/2018 12:56 PM, Razvan Cojocaru wrote: >> On 04/23/2018 02:47 PM, George Dunlap wrote: >>> On 04/18/2018 02:12 PM, Razvan Cojocaru wrote: p2m_change_type_range() handles end > max_mapped_pfn, but not start > max_mapped_pfn. Check the

Re: [Xen-devel] [PATCH RFC 03/10] x86/passthrough: io.c is used for HVM only

>>> On 21.02.18 at 22:46, wrote: > Signed-off-by: Wei Liu > --- > This file has a few functions that are called in other places. We need > to provide stubs for them at some point. Currently the declarations > are in different places. What is the

Re: [Xen-devel] Xen and safety certification, Minutes of the meeting on Apr 4th (Notes on MISRA, ISO 26262 static code analysis requirements)

Hi all, On 06/04/2018, 15:13, "Lars Kurth" wrote: > 1) Requirements to the code, a subset of MISRA for ASIL B > Next step: get more information about requirements and publish it to > xen-devel. I see a few problems here: * The MISRA

Re: [Xen-devel] [PATCH 16/16] configure: do_compiler: Dump some extra info under bash

On Thu, Apr 19, 2018 at 05:45:19PM +0100, Ian Jackson wrote: > This makes it much easier to find a particular thing in config.log. > > The information may be lacking in other shells, resulting in harmless > empty output. (This is why we don't use the proper ${FUNCNAME[*]} > array syntax - other

Re: [Xen-devel] [Qemu-devel] [PATCH 16/16] configure: do_compiler: Dump some extra info under bash

On Mon, Apr 23, 2018 at 05:21:42PM +0100, Anthony PERARD wrote: > On Thu, Apr 19, 2018 at 05:45:19PM +0100, Ian Jackson wrote: > > This makes it much easier to find a particular thing in config.log. > > > > The information may be lacking in other shells, resulting in harmless > > empty output.

Re: [Xen-devel] [PATCH RFC 05/10] x86/passthrough: move hvm_dpci_isairq_eoi

>>> On 21.02.18 at 22:46, wrote: > This function is not Intel specific. Move it to io.c along side its > sole user. Remove declaration in iommu.h. > > Signed-off-by: Wei Liu Acked-by: Jan Beulich (with whatever path name adjustments

Re: [Xen-devel] [RFC v2 6/9] libxl: Have QEMU save its state to a file descriptor

On Mon, Apr 23, 2018 at 10:20:42AM +0100, Wei Liu wrote: > On Mon, Apr 16, 2018 at 06:32:24PM +0100, Anthony PERARD wrote: > > In case QEMU have restricted access to the system, open the file for it, > > and QEMU will save its state to this file descritor. > > > > Signed-off-by: Anthony PERARD

Re: [Xen-devel] [PATCH RFC 09/10] passthrough/intel: put some code under CONFIG_HVM

>>> On 21.02.18 at 22:47, wrote: > @@ -1873,6 +1876,7 @@ int iommu_pte_flush(struct domain *d, u64 gfn, u64 *pte, > return rc; > } > > +#ifdef CONFIG_HVM > static int __init vtd_ept_page_compatible(struct iommu *iommu) > { > u64 ept_cap, vtd_cap = iommu->cap; >

Re: [Xen-devel] [RFC PATCH 1/8] x86/domctl: introduce a pair of hypercall to set and get cpu topology

>>> On 08.01.18 at 05:01, wrote: > Define interface, structures and hypercalls for toolstack to build > cpu topology and for guest that will retrieve it [1]. > Two subop hypercalls introduced by this patch: > XEN_DOMCTL_set_cpu_topology to define cpu topology information per

Re: [Xen-devel] [RFC PATCH 2/8] x86/vlapic: use apic_id array to set initial (x2)APIC ID

>>> On 08.01.18 at 05:01, wrote: > --- a/xen/include/asm-x86/hvm/domain.h > +++ b/xen/include/asm-x86/hvm/domain.h > @@ -213,6 +213,9 @@ struct hvm_domain { > uint8_t thread_per_core; > }; > > +#define hvm_vcpu_x2apic_id(v) >

Re: [Xen-devel] [PATCH 16/16] configure: do_compiler: Dump some extra info under bash

Anthony PERARD writes ("Re: [PATCH 16/16] configure: do_compiler: Dump some extra info under bash"): > On Thu, Apr 19, 2018 at 05:45:19PM +0100, Ian Jackson wrote: > > +funcs: ${FUNCNAME} > > +lines: ${BASH_LINENO} > > +files: ${BASH_SOURCE}" > > echo $compiler "$@" >> config.log > >

[Xen-devel] [xen-unstable-smoke test] 122371: tolerable all pass - PUSHED

flight 122371 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/122371/ 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

Re: [Xen-devel] [PATCH RFC 01/10] passthrough: rearrange x86 code

>>> On 21.02.18 at 22:46, wrote: > Clean up the hierarchy of the directory: put vtd, amd and io.c under > x86. Adjust makefile and MAINTAINERS. Considering the history in particular of VT-d, I'm not convinced of this move: x86 and ia64 did share the bulk of the VT-d code

Re: [Xen-devel] [PATCH RFC 02/10] passthrough: split out x86 PCI code to x86/pci.c

>>> On 21.02.18 at 22:46, wrote: > Move the functions that reference x86 hvm data structures to its own > file. Rename pci_clean_dpci_irqs to arch_pci_clean_irqs. > > There is still one location in that file which references > arch.hvm_domain, but it is fine because ARM

Re: [Xen-devel] [PATCH 12/16] xen: Remove now-obsolete xen_xc_domain_add_to_physmap

On Thu, Apr 19, 2018 at 05:45:15PM +0100, Ian Jackson wrote: > The last user was just removed; remove this function, accordingly. > > Signed-off-by: Ian Jackson Acked-by: Anthony PERARD -- Anthony PERARD

Re: [Xen-devel] [PATCH RFC 07/10] passthrough/amd: split out hvm code from iommu_map.c

>>> On 21.02.18 at 22:46, wrote: > Move and rename update_paging_mode. Create a local header file for > this and other functions that need exporting. Functions you move into global name space need suitable prefixes - neither hvm_update_paging_mode() nor

Re: [Xen-devel] [PATCH 05/16] xen: defer call to xen_restrict until just before os_setup_post

On Thu, Apr 19, 2018 at 05:45:08PM +0100, Ian Jackson wrote: > diff --git a/stubs/xen-hvm.c b/stubs/xen-hvm.c > index 0067bcc..7787ea2 100644 > --- a/stubs/xen-hvm.c > +++ b/stubs/xen-hvm.c > @@ -13,6 +13,7 @@ > #include "hw/xen/xen.h" > #include "exec/memory.h" > #include

Re: [Xen-devel] [PATCH RFC for-next] x86/mm: introduce and use virt_to_xen_l4e

>>> On 31.10.17 at 19:51, wrote: > Avoid open-coding in a lot of places. > > No functional change. > > Signed-off-by: Wei Liu > --- > Is this patch useful or is open-coding preferred? I think we want to revisit this when 5-level paging code arrives.

Re: [Xen-devel] [PATCH 0/6] arm: more kconfig configurability and small default configs

Hello Stefano, I'm really glad to see this series. In the list of platform-specific bits you are trying to make selectable, you missed platform support code itself. Moreover, as it is said in your follow-up emails, set of UART, IOMMU, GIC is defined by SoC family. So wouldn't it be more

Re: [Xen-devel] [PATCH 3/6] arm: make it possible to disable the SMMU driver

Hello Stefano, On 20.04.18 01:43, Stefano Stabellini wrote: Let's take this example: SMMUv2. The driver is decently quality, and definitely some boards will require it. It makes sense to security support it. However, some boards don't come with an SMMU at all, such as Pine64 I guess arm

Re: [Xen-devel] [RFC v2 8/9] HACK libxl_exec: Check QEMU status via QMP instead of xenstore

On Fri, Apr 20, 2018 at 07:37:17PM +0100, Ian Jackson wrote: > Anthony PERARD writes ("[RFC v2 8/9] HACK libxl_exec: Check QEMU status via > QMP instead of xenstore"): > > When QEMU is restricted, the qemu on the receiving side cann't write > > anything to xenstore once the migration is started.

Re: [Xen-devel] [PATCH v2 03/10] xen/arm: Implement CPU_OFF PSCI call (physical interface)

Hi Julien, On Mon, Apr 23, 2018 at 1:21 PM, Julien Grall wrote: > Hi Mirela, > > On 20/04/18 13:25, Mirela Simonovic wrote: >> >> During the system suspend to RAM non-boot CPUs will be hotplugged. >> This will be triggered via disable_nonboot_cpus() call. When >> hotplugged

Re: [Xen-devel] [Qemu-devel] [PATCH 16/16] configure: do_compiler: Dump some extra info under bash

Daniel P. Berrangé writes ("Re: [Qemu-devel] [PATCH 16/16] configure: do_compiler: Dump some extra info under bash"): > Personally I'd suggest we add informative messages throughout the > configure script for each check being run. If people really hate the > idea of a verbose output from

Re: [Xen-devel] [PATCH v2 03/10] xen/arm: Implement CPU_OFF PSCI call (physical interface)

On 23/04/18 18:12, Mirela Simonovic wrote: On Mon, Apr 23, 2018 at 1:21 PM, Julien Grall wrote: On 20/04/18 13:25, Mirela Simonovic wrote: +if ( errno ) +panic("PSCI cpu off failed for CPU%d err=%d\n", get_processor_id(), + errno); +} + void

Re: [Xen-devel] [RFC v2 8/9] HACK libxl_exec: Check QEMU status via QMP instead of xenstore

Anthony PERARD writes ("Re: [RFC v2 8/9] HACK libxl_exec: Check QEMU status via QMP instead of xenstore"): > But, with the to be release QEMU 2.12, there is a new interface that > allow to pre-open a socket: > -chardev socket,fd=? > See >

Re: [Xen-devel] [PATCH 2/8] x86/HVM/SVM: Add AVIC initialization code

> +++ b/xen/arch/x86/hvm/svm/avic.c > @@ -0,0 +1,191 @@ > +/* > + * avic.c: implements AMD Advanced Virtual Interrupt Controller (AVIC) > support > + * Copyright (c) 2016, Advanced Micro Devices, Inc. Not 2018? ___ Xen-devel mailing list

Re: [Xen-devel] [PATCH] Input: xen-kbdfront - allow better run-time configuration

On 04/23/2018 09:53 PM, Dmitry Torokhov wrote: On Thu, Apr 19, 2018 at 02:44:19PM +0300, Oleksandr Andrushchenko wrote: On 04/19/2018 02:25 PM, Juergen Gross wrote: On 18/04/18 17:04, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko It is now

Re: [Xen-devel] [PATCH 2/8] x86/HVM/SVM: Add AVIC initialization code

On 4/23/2018 2:33 PM, Konrad Rzeszutek Wilk wrote: +++ b/xen/arch/x86/hvm/svm/avic.c @@ -0,0 +1,191 @@ +/* + * avic.c: implements AMD Advanced Virtual Interrupt Controller (AVIC) support + * Copyright (c) 2016, Advanced Micro Devices, Inc. Not 2018? Ah good catch. Yeah it should be 2018.

Re: [Xen-devel] [PATCH for-4.11] x86/spec_ctrl: Updates to retpoline-safety decision making

> diff --git a/xen/arch/x86/spec_ctrl.c b/xen/arch/x86/spec_ctrl.c > index 5b5ec90..aff06f0 100644 > --- a/xen/arch/x86/spec_ctrl.c > +++ b/xen/arch/x86/spec_ctrl.c > @@ -113,12 +113,13 @@ static void __init print_details(enum ind_thunk thunk) > printk(XENLOG_DEBUG "Speculative mitigation

[Xen-devel] [linux-4.14 baseline test] 122368: tolerable FAIL

"Old" tested version had not actually been tested; therefore in this flight we test it, rather than a new candidate. The baseline, if any, is the most recent actually tested revision. flight 122368 linux-4.14 real [real] http://logs.test-lab.xenproject.org/osstest/logs/122368/ Failures :-/ but

[Xen-devel] [xen-4.7-testing test] 122353: regressions - FAIL

flight 122353 xen-4.7-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/122353/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-xtf-amd64-amd64-3 50 xtf/test-hvm64-lbr-tsx-vmentry fail REGR. vs. 122131

Re: [Xen-devel] [RFC 0/2] To introduce xenwatch multithreading (xen mtwatch)

Hi Wei, On 04/23/2018 10:09 PM, Wei Liu wrote: > On Sat, Apr 07, 2018 at 07:25:53PM +0800, Dongli Zhang wrote: >> About per-domU xenwatch thread create/destroy, a new type of xenstore node is >> introduced: '/local/domain/0/mtwatch/'. >> >> Suppose the new domid id 7. During the domU (domid=7)

Re: [Xen-devel] [PATCH 0/1] drm/xen-zcopy: Add Xen zero-copy helper DRM driver

On 04/23/2018 08:10 AM, Oleksandr Andrushchenko wrote: > On 04/23/2018 02:52 PM, Wei Liu wrote: >> On Fri, Apr 20, 2018 at 02:25:20PM +0300, Oleksandr Andrushchenko wrote: > the gntdev. > > I think this is generic enough that it could be implemented by a > device not tied to

Re: [Xen-devel] [PATCH for-4.11] x86/spec_ctrl: Updates to retpoline-safety decision making

On 23/04/2018 22:16, Konrad Rzeszutek Wilk wrote: >> diff --git a/xen/arch/x86/spec_ctrl.c b/xen/arch/x86/spec_ctrl.c >> index 5b5ec90..aff06f0 100644 >> --- a/xen/arch/x86/spec_ctrl.c >> +++ b/xen/arch/x86/spec_ctrl.c >> @@ -113,12 +113,13 @@ static void __init print_details(enum ind_thunk thunk)

[Xen-devel] [xen-4.9-testing test] 122355: regressions - FAIL

flight 122355 xen-4.9-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/122355/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemut-win7-amd64 16 guest-localmigrate/x10 fail REGR. vs. 121761

Re: [Xen-devel] [RFC 0/2] To introduce xenwatch multithreading (xen mtwatch)

On 24/04/18 01:55, Dongli Zhang wrote: > Hi Wei, > > On 04/23/2018 10:09 PM, Wei Liu wrote: >> On Sat, Apr 07, 2018 at 07:25:53PM +0800, Dongli Zhang wrote: >>> About per-domU xenwatch thread create/destroy, a new type of xenstore node >>> is >>> introduced: '/local/domain/0/mtwatch/'. >>> >>>

[Xen-devel] [xen-4.8-testing test] 122354: regressions - trouble: broken/fail/pass

flight 122354 xen-4.8-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/122354/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl broken test-armhf-armhf-xl 4

Re: [Xen-devel] [RFC 0/2] To introduce xenwatch multithreading (xen mtwatch)

Hi Juergen, On 04/24/2018 01:22 PM, Juergen Gross wrote: > On 24/04/18 01:55, Dongli Zhang wrote: >> Hi Wei, >> >> On 04/23/2018 10:09 PM, Wei Liu wrote: >>> On Sat, Apr 07, 2018 at 07:25:53PM +0800, Dongli Zhang wrote: About per-domU xenwatch thread create/destroy, a new type of xenstore

Re: [Xen-devel] [PATCH 0/1] drm/xen-zcopy: Add Xen zero-copy helper DRM driver

On 04/24/2018 01:41 AM, Boris Ostrovsky wrote: On 04/23/2018 08:10 AM, Oleksandr Andrushchenko wrote: On 04/23/2018 02:52 PM, Wei Liu wrote: On Fri, Apr 20, 2018 at 02:25:20PM +0300, Oleksandr Andrushchenko wrote: the gntdev. I think this is generic enough that it could be implemented

  1   2   >