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
>
> ---
> Changes since V1:
>>> 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 vlapic *vlapic, uint32_t
> icr_low,
>>> uint32_t ic
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.
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 XenStore entries),
but keyboard and po
>>> 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 Cojocaru
>> Suggested-by: G
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
>
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
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 Apr 2018 11:01:49 +0
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 app
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 - 0x
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
Acke
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 be done at the
> same scope level as read(). It doesn't need to be
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
_
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
I think this is going to break FreeBSD?
And what is /dev/fdset exac
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 +++
> tools/libxl/libxl_qmp.c | 39 ++
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
test-armhf-armhf-armhf-sid-n
Hi all,
forgot to mention: I am testing xen on Salvator-X board.
ᐧ
2018-04-20 12:05 GMT+01:00 Yessine Daoud :
> Hi,
>
> When I upgrade to Xen 4.11, I got the following when creating any guest:
>
> (XEN)_event_channel.c:319:d0v3_EVTCHNOP_failure:_domain_1,_error_-22
> (XEN)_event_channel.c:319:d
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 c
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 introspect
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 kexec loaded images. The
> > f
>>> 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 consideration for enhancing
>> > Xen to support signature verif
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.
_
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 h
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 zero
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 EL3
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). Therefore
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
cpu_up/start_secondary(
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
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
---
tools/firmware/xen-dir/shim.config |
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
--
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 bo
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
Sorry, I meant to reply to
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 r
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
>> Sugge
flight 122352 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122352/
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 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 j
>>> 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 interrupts
> in machine_restart().
Pointing at bad behavior to j
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 interrupts
>> in machin
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
---
xen/a
>>> 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; DO NOT EDIT.
>>> -# Xen/x86 4.11-un
>>> 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 after a double fault.
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 allow
>> interrupt
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
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
___
Xen-devel mailing list
Xen-devel@list
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
>> i
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
>
Release-acked-by: Juergen Gross
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/a
>>> 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 after a double fault.
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
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 '/local/domain/0/mt
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
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 GCC diagnostic" inside f
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
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 1
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 th
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 if
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
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
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 migh
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 productio
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 a/README.planner b/README.pl
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 100755
--- a/ms-planner
+++ b/
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,
>>so it seems we have no
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
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
> Acked-by: Stefano Stabell
>>> 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 back when ia64 was still
>>> 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 guest is HVM.
>
> Signed
>>> 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 preferred name / location for the
> stubs?
Perhaps
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
___
Xen-devel mailing list
Xen-devel@lists.x
>>> 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 are necessary depending on the
disposition of patches earlier
>>> 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 set_iommu_pde_present() clarify that this
i
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
>
>>> 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;
> @@ -1885,6 +1889,7 @@
>>> 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.
Jan
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 "qapi/qapi-commands-mi
>>> 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 domain
> and XENMEM_ge
>>> 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)
> (v->domain->arch.hvm_domain.apic_id[v->vcpu_id])
I can't seem
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 2012 spec has to be bought
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 s
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. (T
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
> > $co
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 1
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. S
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
> https://git.qemu.org/?p=qemu.git;a=commit;h=0935700f8544
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 configure
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 the CPU will end up in
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 call_psci_system_off(v
The attachment is also at
https://wiki.xenproject.org/images/c/cf/Windows_PV_Driver_-_Graduation_Proposal.pdf
Lars
> On 23 Apr 2018, at 18:14, Lars Kurth wrote:
>
> Dear Community members,
> please find attached (and in markdown, but without graphs) the case to
> graduate the Windows PV Driver
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 natur
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 natur
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 passth
Hello Stefano,
If we stick with platform specific configuration file:
On 19.04.18 01:15, Stefano Stabellini wrote:
This is a reference tiny kconfig for Renesas RCar. In terms of
schedulers, it selects credit and NULL only. It enables all the ARM64
errata.
Signed-off-by: Stefano Stabellini
Hi, Oleksandr.
On Thu, Apr 19, 2018 at 9:39 AM, Oleksandr Andrushchenko
wrote:
> @@ -241,60 +242,84 @@ static int xenkbd_probe(struct xenbus_device *dev,
> }
>
> /* keyboard */
> - kbd = input_allocate_device();
> - if (!kbd)
> - goto error_nomem;
> -
flight 122372 examine real [real]
http://logs.test-lab.xenproject.org/osstest/logs/122372/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
examine-laxton0 2 hosts-allocatebroken blocked in 121088
examine-rimava0 2 hosts-all
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 only possible to control if multi-touch virtual device
> > > is c
On Mon, Apr 23, 2018 at 11:29:45AM +0300, Oleksandr Andrushchenko wrote:
> 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, bu
> +++ 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
Xen-devel@list
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.
_
On 04/23/2018 11:38 AM, Ian Jackson wrote:
> You are right. Perhaps my testing was inadequate. I wrote this a
> long while ago, and if there was a syntax along these lines that DTRT
> in both bash and dash in my tests it is long gone. Starting de novo,
> the following code works for me:
>
>
"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 n
1 - 100 of 123 matches
Mail list logo
