On 20. 09. 19 1:17, Michael Ellerman wrote:
>
>
> On 20 September 2019 6:33:50 am AEST, Linus Torvalds
> wrote:
>> On Wed, Sep 18, 2019 at 8:27 AM Christoph Hellwig
>> wrote:
>>>
>>> please pull the dma-mapping updates for 5.4.
>>
>> Pulled.
>>
>>> In addition to the usual Kconfig conflics
flight 141459 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141459/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-examine 11 examine-serial/bootloaderfail like 141376
flight 141489 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141489/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 7 xen-boot fail REGR. vs. 141253
Tests which
flight 141453 linux-4.19 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141453/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-pvops 6 kernel-build fail REGR. vs. 129313
Tests which are
On Tue, 20 Aug 2019, Oleksandr wrote:
>
> On 20.08.19 15:22, Julien Grall wrote:
>
> Hi, Julien
>
> > -iommu_setup();
> > +rc = iommu_setup();
> > +if ( !iommu_enabled && rc != -ENODEV )
> > +panic("Couldn't configure correctly all the IOMMUs.");
> >
>
> Please add
Hi Oleksandr-san,
> From: Oleksandr Tyshchenko, Sent: Saturday, September 14, 2019 12:35 AM
>
> From: Oleksandr Tyshchenko
>
> The IPMMU-VMSA is VMSA-compatible I/O Memory Management Unit (IOMMU)
> which provides address translation and access protection functionalities
> to processing units
flight 141485 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141485/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 7 xen-boot fail REGR. vs. 141253
Tests which
On Tue, 17 Sep 2019, Julien Grall wrote:
> The current implementations of xen_{map, unmap}_table() expect
> {map, unmap}_domain_page() to be usable. Those helpers are used to
> map/unmap page tables while update Xen page-tables.
>
> Since commit 022387ee1a "xen/arm: mm: Don't open-code Xen PT
flight 141456 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141456/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-libvirt-qcow2 15 guest-start/debian.repeat fail REGR. vs.
141415
Tests which did
On 20 September 2019 6:33:50 am AEST, Linus Torvalds
wrote:
>On Wed, Sep 18, 2019 at 8:27 AM Christoph Hellwig
>wrote:
>>
>> please pull the dma-mapping updates for 5.4.
>
>Pulled.
>
>> In addition to the usual Kconfig conflics where you just want to keep
>> both edits there are a few more
On Tue, 17 Sep 2019, Julien Grall wrote:
> After commit 6e3e771203 "xen/arm: setup: Relocate the Device-Tree later on
> in the boot", the boot allocator will not receive any xenheap page (i.e.
> mapped page) on Arm32.
>
> However, the boot allocator implicitely rely on having the first page
>
On 9/19/19 3:24 AM, Jan Beulich wrote:
> On 18.09.2019 23:16, Joe Jin wrote:
>> On 9/16/19 11:48 PM, Jan Beulich wrote:
>>> On 17.09.2019 00:20, Joe Jin wrote:
On 9/16/19 1:01 AM, Jan Beulich wrote:
> On 13.09.2019 18:38, Joe Jin wrote:
>> On 9/13/19 12:14 AM, Jan Beulich wrote:
The pull request you sent on Wed, 18 Sep 2019 08:27:48 -0700:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/671df189537883f36cf9c7d4f9495bfac0f86627
Thank you!
--
Deet-doot-dot, I am a bot.
flight 141480 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141480/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 7 xen-boot fail REGR. vs. 141253
Tests which
flight 141446 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141446/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-i386 7 xen-boot fail REGR. vs. 133580
On 9/19/19 11:07 PM, Boris Ostrovsky wrote:
> On 9/19/19 6:37 AM, Jan Beulich wrote:
>> hvm_monitor_cpuid() expects the input registers, not two of the outputs.
>>
>> However, once having made the necessary adjustment, the SVM and VMX
>> functions are so similar that they should be folded (thus
On Wed, Sep 18, 2019 at 8:27 AM Christoph Hellwig wrote:
>
> please pull the dma-mapping updates for 5.4.
Pulled.
> In addition to the usual Kconfig conflics where you just want to keep
> both edits there are a few more interesting merge issues this time:
>
> - most importanly powerpc and
flight 141448 linux-4.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141448/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvshim 20 guest-start/debian.repeat fail REGR. vs. 139698
Tests which are
On 9/19/19 6:37 AM, Jan Beulich wrote:
> hvm_monitor_cpuid() expects the input registers, not two of the outputs.
>
> However, once having made the necessary adjustment, the SVM and VMX
> functions are so similar that they should be folded (thus avoiding
> further similar asymmetries to get
Anthony PERARD writes ("[PATCH v2 00/35] libxl refactoring to use ev_qmp (with
API changes)"):
> Patches with missing ackes:
> libxl: Use ev_qmp for switch_qemu_xen_logdirty
> libxl: Use ev_qmp in libxl_set_vcpuonline
> libxl_pci: Extract common part of *qemu_trad_watch_state_cb
>
>
Anthony PERARD writes ("[PATCH v2 35/35] libxl_pci: Extract common part of
*qemu_trad_watch_state_cb"):
> Functions pci_add_qemu_trad_watch_state_cb and
> pci_remove_qemu_trad_watch_state_cb are similar so the common part is
> extracted in a different function.
OK (though not quite how I would
Anthony PERARD writes ("[PATCH v2 00/35] libxl refactoring to use ev_qmp (with
API changes)"):
> Patches with missing ackes:
...
> libxl: Use ev_qmp in libxl_set_vcpuonline
From my point of view I seem to have sent a ack for this,
Message-ID:
Anthony PERARD writes ("[PATCH v2 06/35] libxl: Use ev_qmp for
switch_qemu_xen_logdirty"):
> Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
(in line with my previous comments)
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
flight 141451 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141451/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf b0c15fb128c518b9acd8611a2deea213e9e55193
baseline version:
ovmf
On Mon, 2019-08-19 at 18:58 +0100, Vlastimil Babka wrote:
[...]
> Hi, I'm sending this stable-only patch for consideration because it's probably
> unrealistic to backport the 4.13 switch to generic GUP. I can look at 4.4 and
> 3.16 if accepted. The RCU page table freeing could be also considered.
This patch also replaces the use of
libxl__wait_for_device_model_deprecated() by its equivalent
without the need for a thread.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_internal.h | 1 -
tools/libxl/libxl_pci.c | 288 ---
There are no more users.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_internal.h | 3 ---
tools/libxl/libxl_qmp.c | 16
2 files changed, 19 deletions(-)
diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h
index
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_dm.c | 22 +-
tools/libxl/libxl_internal.h | 1 +
2 files changed, 22 insertions(+), 1 deletion(-)
diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c
index 246c570121d3..c00356a2f16a
Having the function do_usbdev_add makes it harder to add asynchronous
calls into it. Move its body back into libxl__device_usbdev_add and
adjust the latter as there are no reason to have a separated function.
No functional changes.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
`aodev->qmp' is initialised in libxl__prepare_ao_device(), but since
there isn't a single exit path for a `libxl__ao_device', users of this
new `qmp' field will have to disposed of it.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
Notes:
v2:
- Added a comment to
Having the function do_usbdev_remove makes it harder to add asynchronous
calls into it. Move its body back into libxl__device_usbdev_remove and
adjust the latter as there are no reason to have a separated function.
No functional changes.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_domain.c | 49 ++--
tools/libxl/libxl_internal.h | 2 --
tools/libxl/libxl_qmp.c | 5
3 files changed, 42 insertions(+), 14 deletions(-)
diff --git
libxl__domain_resume is a rework libxl__domain_resume_deprecated. It
makes uses of ev_xswatch and ev_qmp, to replace synchronous QMP calls
and libxl__wait_for_device_model_deprecated call.
This patch also introduce libxl__dm_resume which is a sub-operation of
both libxl__domain_resume and
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_usb.c | 78 +++--
1 file changed, 68 insertions(+), 10 deletions(-)
diff --git a/tools/libxl/libxl_usb.c b/tools/libxl/libxl_usb.c
index 3b432231ea85..1fc7ccf41f86 100644
---
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_usb.c | 99 +
1 file changed, 81 insertions(+), 18 deletions(-)
diff --git a/tools/libxl/libxl_usb.c b/tools/libxl/libxl_usb.c
index 373b37d7159a..b9a31f96ebe3 100644
---
This is in preparation of using asynchronous operation to communicate
with QEMU via QMP (libxl__ev_qmp).
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_domain.c | 49 ++--
tools/libxl/libxl_internal.h | 6 +-
tools/libxl/libxl_pci.c | 221
Functions pci_add_qemu_trad_watch_state_cb and
pci_remove_qemu_trad_watch_state_cb are similar so the common part is
extracted in a different function.
Signed-off-by: Anthony PERARD
---
Notes:
v2:
- new patch which attempt to combine the "basically-identical" functions
libxl__domain_unpause is a reimplementation of
libxl__domain_unpause_deprecated with asynchronous operation.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_domain.c | 52
tools/libxl/libxl_internal.h | 5 +++-
2 files changed,
This also mean libxl__initiate_device_usbctrl_remove, which uses
libxl__device_usbdev_remove synchronously, needs to be updated to use
it with multidev.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_usb.c | 79 +++--
1 file
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_usb.c | 97 +
1 file changed, 79 insertions(+), 18 deletions(-)
diff --git a/tools/libxl/libxl_usb.c b/tools/libxl/libxl_usb.c
index 506dbdcf5ee4..373b37d7159a 100644
---
do_pci_add is going to be asynchronous, so we start by having a single
path out of the function. All `return`s instead set rc and goto out.
While here, some use of `rc' was used to store the return value of
libxc calls, change them to store into `r'. Also, add the value of `r'
in the error
This patch also replaces the use of
libxl__wait_for_device_model_deprecated() by its equivalent
without the need for a thread.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_internal.h | 2 -
tools/libxl/libxl_pci.c | 222 +--
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_domain.c | 21 +++--
1 file changed, 19 insertions(+), 2 deletions(-)
diff --git a/tools/libxl/libxl_domain.c b/tools/libxl/libxl_domain.c
index 80797c5ed21c..d78ffa6b6019 100644
---
Removed libxl__qmp_cpu_add since it's not used anymore.
`cpumap' arg of libxl__set_vcpuonline_xenstore is constified.
The QMP command "query-cpus" is going to be called from different
places, so the algorithm that parse the answer is in a separate
function, qmp_parse_query_cpus.
Signed-off-by:
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_domain.c | 25 ++---
1 file changed, 18 insertions(+), 7 deletions(-)
diff --git a/tools/libxl/libxl_domain.c b/tools/libxl/libxl_domain.c
index 52a8bd7895cb..f3c39fa86fc9 100644
---
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_internal.h | 7 +-
tools/libxl/libxl_pci.c | 170 ++-
2 files changed, 150 insertions(+), 27 deletions(-)
diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_qmp.c | 52 +++--
1 file changed, 50 insertions(+), 2 deletions(-)
diff --git a/tools/libxl/libxl_qmp.c b/tools/libxl/libxl_qmp.c
index 9639d491d991..9aabad74fabd 100644
---
These two fields help to give more information about the device been
hotplug/hotunplug to callbacks.
There is already `dev' of type `libxl__device', but it is mostly
useful when the backend/frontend is xenstore. Some device (like
`usbdev') don't have devid, so `dev' can't be used.
Signed-off-by:
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl_usb.c | 93 ++---
1 file changed, 77 insertions(+), 16 deletions(-)
diff --git a/tools/libxl/libxl_usb.c b/tools/libxl/libxl_usb.c
index de8122dc57e9..506dbdcf5ee4 100644
---
QEMU upstream (or qemu-xen) may not have set "running" state in
xenstore. "running" with QEMU doesn't mean that the binary is
running, it means that the emulation have started. When adding a
pci-passthrough device to QEMU, we do so via QMP, we have a direct
answer to whether QEMU is running or
This was the last user of libxl__qmp_query_cpus which can now be
removed.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
Notes:
v3:
- following rename of ev_lock to ev_devlock, renamed field rdcs.ev_lock
to rdcs.devlock
tools/libxl/libxl_domain.c | 163
libxl_domain_unpause needs to make QMP calls, which are asynchronous,
change the API to reflect that.
Do the same with libxl_domain_pause async, even if it will keep
completing synchronously.
Also fix some coding style issue in those functions.
Signed-off-by: Anthony PERARD
Acked-by: Ian
libxl__qmp_initializations is part of the device domain startup, it
queries information about the newly spawned QEMU and do some
post-startup configuration. So the function call doesn't belong to the
general domain creation, but only to the device model part of the
process, thus the call belong to
.. because it makes QMP calls which are going to be async.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl.h| 15 ++-
tools/libxl/libxl_domain.c | 12
tools/xl/xl_cpupool.c | 2 +-
tools/xl/xl_vcpu.c | 2 +-
4 files
.. because it makes QMP calls which are going to be async.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl.h| 13 -
tools/libxl/libxl_domain.c | 14 +++---
tools/xl/xl_info.c | 3 ++-
tools/xl/xl_saverestore.c | 3 ++-
.. because it makes QMP calls which are going to be async.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl.h | 14 +-
tools/libxl/libxl_qmp.c | 9 +
tools/xl/xl_misc.c | 2 +-
3 files changed, 19 insertions(+), 6 deletions(-)
diff --git
Setup a timeout of 10s for all the commands. It used to be about 5s
per commands.
The order of command is changed, we call 'query-vnc' before
'change-vnc-password', but that should not matter. That makes it
easier to call 'change-vnc-password' conditionally.
Also 'change' command is replaced by
.. because it makes QMP calls which are going to be async.
Signed-off-by: Anthony PERARD
Acked-by: Ian Jackson
---
tools/libxl/libxl.h| 13 -
tools/libxl/libxl_domain.c | 12
tools/xl/xl_misc.c | 4 ++--
tools/xl/xl_vmcontrol.c| 4 ++--
4 files
These two functions are used from many places in libxl and need to
change to be able to accomodate libxl__ev_qmp calls and thus needs to
be asynchronous.
(There is also libxl__domain_resume_device_model in the mix.)
A later patch will introduce a new libxl__domain_resume and
Patches with missing ackes:
libxl: Use ev_qmp for switch_qemu_xen_logdirty
libxl: Use ev_qmp in libxl_set_vcpuonline
libxl_pci: Extract common part of *qemu_trad_watch_state_cb
The series depends on "Some cleanup of libxl" series.
Patch series available in this git branch (which is on
Signed-off-by: Anthony PERARD
---
tools/libxl/libxl_dom_save.c | 41
tools/libxl/libxl_internal.h | 3 +--
tools/libxl/libxl_qmp.c | 10 -
3 files changed, 38 insertions(+), 16 deletions(-)
diff --git a/tools/libxl/libxl_dom_save.c
flight 141474 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141474/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 7 xen-boot fail REGR. vs. 141253
Tests which
On Fri, Jun 14, 2019 at 12:24:29PM +0100, Anthony PERARD wrote:
> Hi,
>
> This series contains cleanup patches, ahead of a series that's going to make
> more changes to libxl.
v2 with patch 11 acked and the whole branch rebased pushed to:
On 9/16/19 11:59 AM, Pawel Wieczorkiewicz wrote:
Having detailed hotpatch metadata helps to properly identify module's
origin and version. It also allows to keep track of the history of
hotpatch loads in the system (at least within dmesg buffer size
limits).
The hotpatch metadata are embedded
Anthony PERARD writes ("Re: [PATCH 33/35] libxl: Extract qmp_parse_query_cpus"):
> On Tue, Sep 17, 2019 at 06:42:10PM +0100, Ian Jackson wrote:
> > Anthony PERARD writes ("[PATCH 33/35] libxl: Extract qmp_parse_query_cpus"):
> > > The QMP command "query-cpus" is called from different places,
Anthony PERARD writes ("Re: [PATCH 17/35] libxl: Add libxl__ev_qmp to
libxl__ao_device"):
> On Tue, Sep 17, 2019 at 06:07:31PM +0100, Ian Jackson wrote:
> > It might be nice to add a comment about the field(s) of
> > libxl__ao_device which callers of libxl__prepare_ao_device are
> > expected to
On 9/16/19 11:59 AM, Pawel Wieczorkiewicz wrote:
This is the initial implementation of the expectations enhancement
to improve inline asm hotpatching.
Expectations are designed as optional feature, since the main use of
them is planned for inline asm hotpatching. The flag enabled allows
to
Andrew,
On 15.07.2019 16:58, Jan Beulich wrote:
> 1: guard top-of-stack reads
> 2: widen condition for logging top-of-stack
>
> The issue patch 2 fixes (a curious lack of an intermediate call stack
> entry) was observed in practice; patch 1 is a result of me just looking
> at the code.
I
On 14.09.2019 10:52, Juergen Gross wrote:
> @@ -1673,8 +1676,10 @@ static void schedule(void)
> * switch, else lost_records resume will not work properly.
> */
>
> -ASSERT(!next->is_running);
> +ASSERT(!next->sched_unit->is_running);
> next->is_running = 1;
> +
On 14.09.2019 10:52, Juergen Gross wrote:
> Add the following helpers using a sched_unit as input instead of a
> vcpu:
>
> - is_idle_unit() similar to is_idle_vcpu()
> - is_unit_online() similar to is_vcpu_online() (returns true when any
> of its vcpus is online)
> - unit_runnable() like
On Tue, Sep 17, 2019 at 06:07:31PM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("[PATCH 17/35] libxl: Add libxl__ev_qmp to
> libxl__ao_device"):
> > `aodev->qmp' is initialised in libxl__prepare_ao_device(), but since
> > there isn't a single exit path for a `libxl__ao_device', users of
On 14.09.2019 10:52, Juergen Gross wrote:
> Affinities are scheduler specific attributes, they should be per
> scheduling unit. So move all affinity related fields in struct vcpu
> to struct sched_unit. While at it switch affinity related functions in
> sched-if.h to use a pointer to sched_unit
flight 141444 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141444/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvshim 20 guest-start/debian.repeat fail in 141392 REGR.
vs. 141254
Tests
On 14.09.2019 10:52, Juergen Gross wrote:
> This prepares support of larger scheduling granularities, e.g. core
> scheduling.
>
> While at it move sched_has_urgent_vcpu() from include/asm-x86/cpuidle.h
> into sched.h removing the need for including sched-if.h in cpuidle.h.
> For that purpose
On 9/16/19 11:59 AM, Pawel Wieczorkiewicz wrote:
Livepatch only tracks an entire payload applied/reverted state. But,
with an option to supply the apply_payload() and/or revert_payload()
functions as optional hooks, it becomes possible to intermix the
execution of the original
On Tue, Sep 17, 2019 at 06:42:10PM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("[PATCH 33/35] libxl: Extract qmp_parse_query_cpus"):
> > The QMP command "query-cpus" is called from different places, extract
> > the algorithm that parse the answer into a separate function.
>
> I hope you
On 9/16/19 11:59 AM, Pawel Wieczorkiewicz wrote:
With default implementation the ELF_LIVEPATCH_FUNC section containing
all functions to be replaced or added must be part of the hotpatch
payload, otherwise the payload is rejected (with -EINVAL).
However, with the extended hooks implementation, a
On 9/16/19 11:59 AM, Pawel Wieczorkiewicz wrote:
By default, in the quiescing zone, a hotpatch payload is applied with
s/hotpatch/livepatch/ (for all the patches)
apply_payload() and reverted with revert_payload() functions. Both of
the functions receive the payload struct pointer as a
> -Original Message-
> diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
> index fdb1e17f59..4cc077bb3f 100644
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -3236,6 +3236,19 @@ static enum hvm_translation_result __hvm_copy(
> return
On 17.09.2019 15:21, Julien Grall wrote:
> After commit 6e3e771203 "xen/arm: setup: Relocate the Device-Tree later on
> in the boot", the boot allocator will not receive any xenheap page (i.e.
> mapped page) on Arm32.
>
> However, the boot allocator implicitely rely on having the first page
>
On 19.09.2019 15:03, Alexandru Stefan ISAILA wrote:
> @@ -601,6 +602,7 @@ static void *hvmemul_map_linear_addr(
>
> case HVMTRANS_gfn_paged_out:
> case HVMTRANS_gfn_shared:
> +case HVMTRANS_bad_gfn_access:
> err = ERR_PTR(~X86EMUL_RETRY);
>
flight 141470 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141470/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 7 xen-boot fail REGR. vs. 141253
Tests which
On 19.09.19 15:29, Julien Grall wrote:
Hi,
Hi, Julien
+
+int __init iommu_add_dt_device(struct dt_device_node *np)
Sorry to only realise it now. Would it make sense to have this
function implemented in xen/passthrough/device_tree.c?
Not entirely sure. device_tree.c is a common
Make sure we don't leave any DTEs unexpected requests through which
would be passed through untranslated. Set V and IV right away (with
all other fields left as zero), relying on the V and/or IV bits
getting cleared only by amd_iommu_set_root_page_table() and
amd_iommu_set_intremap_table() under
Having a single device table for all segments can't possibly be right.
(Even worse, the symbol wasn't static despite being used in just one
source file.) Attach the device tables to their respective IVRS mapping
ones.
Signed-off-by: Jan Beulich
---
v6: New.
---
Move the device flags field up into an unused hole, thus shrinking
overall structure size by 8 bytes. Use bool and uint_t as
appropriate. Drop pointless (redundant) initializations.
Signed-off-by: Jan Beulich
---
v6: New.
---
xen/drivers/passthrough/amd/iommu_acpi.c |6 +++---
There's no point setting up tables with more space than a PCI device can
use. For both MSI and MSI-X we can determine how many interrupts could
be set up at most. Tables allocated during ACPI table parsing, however,
will (for now at least) continue to be set up to have maximum size.
Note that
Prepare for the number of entries to not be the maximum possible, by
separating checks against maximum size from ones against actual size.
For caller side simplicity have alloc_intremap_entry() return the
maximum possible value upon allocation failure, rather than the first
just out-of-bounds one.
Rather than doing this every time we set up interrupts for a device
anew (and then in several places) fill this invariant field right after
allocating struct pci_dev.
Signed-off-by: Jan Beulich
---
v6: New.
---
xen/arch/x86/msi.c| 13 +
xen/drivers/passthrough/pci.c |
Rather than duplicating entries in amd_iommu_msi_msg_update_ire(), share
the tables. This mainly requires some care while freeing them, to avoid
freeing memory blocks twice.
Signed-off-by: Jan Beulich
Acked-by: Andrew Cooper
---
v5: New.
---
xen/drivers/passthrough/amd/iommu_init.c |
ACPI tables are free to list far more device coordinates than there are
actual devices. By delaying the table allocations for most cases, and
doing them only when an actual device is known to be present at a given
position, overall memory used for the tables goes down from over 500k
pages to just
On Thu, Sep 19, 2019 at 02:03:10PM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("Re: [PATCH 06/35] libxl: Use ev_qmp for
> switch_qemu_xen_logdirty"):
> > On Tue, Sep 17, 2019 at 05:52:24PM +0100, Ian Jackson wrote:
> > I guess we could try to optimise the simpler case when there is only
The main goal continues to be to reduce the huge memory overhead
that we've noticed. On the way there a number of other things were
once again noticed. All patches have now been tested on a Fam15
and a Fam17 system.
01: don't blindly allocate interrupt remapping tables
02: make phantom functions
A/D bit writes (on page walks) can be considered benign by an introspection
agent, so receiving vm_events for them is a pessimization. We try here to
optimize by filtering these events out.
Currently, we are fully emulating the instruction at RIP when the hardware sees
an EPT fault with npfec.kind
Anthony PERARD writes ("Re: [PATCH 06/35] libxl: Use ev_qmp for
switch_qemu_xen_logdirty"):
> On Tue, Sep 17, 2019 at 05:52:24PM +0100, Ian Jackson wrote:
> > I hate to suggest this at this stage, but: maybe the timeout could be
> > incorporated into libxl__ev_qmp ?
> >
> > I think every
Wei Liu writes ("Re: [PATCH for-4.13] configure: fix print syntax for python
3"):
> On Thu, 19 Sep 2019 at 12:28, Ian Jackson wrote:
> > My previous reply bounced due to header mangling in your first mail.
> > Let me try again:
> >
> > This is good in principle but:
> >
> > Can you provide as a
On Tue, Sep 17, 2019 at 05:52:24PM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("[PATCH 06/35] libxl: Use ev_qmp for
> switch_qemu_xen_logdirty"):
> > Signed-off-by: Anthony PERARD
> ...
> > +rc = libxl__ev_time_register_rel(ao, >timeout,
> > +
Hi,
On 19/09/2019 13:25, Oleksandr wrote:
On 19.09.19 14:35, Julien Grall wrote:
Hi Oleksandr,
On 13/09/2019 16:35, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
The main puprose of this patch is to add a way to register DT device
(which is behind the IOMMU) using the generic
On 19.09.19 14:35, Julien Grall wrote:
Hi Oleksandr,
Hi, Julien.
On 13/09/2019 16:35, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
The main puprose of this patch is to add a way to register DT device
(which is behind the IOMMU) using the generic IOMMU DT bindings [1]
before
flight 141442 linux-4.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141442/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvshim 20 guest-start/debian.repeat fail in 141400 REGR.
vs. 139910
Tests
1 - 100 of 144 matches
Mail list logo