On Thu, 2019-08-01 at 19:19 -0700, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> For pages that were retained via get_user_pages*(), release those pages
> via the new put_user_page*() routines, instead of via put_page() or
> release_pages().
>
> This is part a tree-wide conversion, as
On 02/08/2019 3:20 am, john.hubb...@gmail.com wrote:
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit
flight 139636 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139636/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-vhd 17 guest-start/debian.repeat fail REGR. vs. 139584
Tests which did
On 8/2/19 6:27 PM, Calum Mackay wrote:
> On 02/08/2019 3:20 am, john.hubb...@gmail.com wrote:
...
> Since it's static, and only called twice, might it be better to change its
> two callers [nfs_direct_{read,write}_schedule_iovec()] to call
> put_user_pages() directly, and remove
On Fri, 2019-08-02 at 14:49 +0100, Julien Grall wrote:
> /!\/!\/!\
>
> I am not a scheduler expert so my view maybe be wrong. Dario feel
> free to
> correct me :).
>
> /!\/!\/!\
>
:-)
> On 02/08/2019 14:07, Andrii Anisov wrote:
> > On 02.08.19 12:15, Julien Grall wrote:
> > > >
> > But the
On Fri, 2019-08-02 at 16:07 +0300, Andrii Anisov wrote:
> On 02.08.19 12:15, Julien Grall wrote:
> > From the list below it is not clear what is the split between
> > hypervisor time and guest time. See some of the examples below.
>
> I guess your question is *why* do I split hyp/guest time in
flight 139633 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139633/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-freebsd10-i386 7 xen-boot fail in 139594 pass in 139633
The pull request you sent on Fri, 2 Aug 2019 16:47:46 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-5.3a-rc3-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/dcb8cfbd8fe9e62c7d64e82288d3ffe2502b7371
Thank you!
--
Deet-doot-dot,
flight 139629 linux-4.19 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139629/
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
flight 139632 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139632/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 46e34cc9561360a63549308b9b5464df6651de05
baseline version:
ovmf
> On Jul 31, 2019, at 04:11, Jan Beulich wrote:
>
>> On 31.07.2019 02:22, Dario Faggioli wrote:
>> Jan's example above, seem to compile **without any warnings** for me as
>> well. If I add a main(), I can even get the code above to print the
>> content of the array.
>>
>> And yet, building the
On 8/2/19 1:05 AM, Peter Zijlstra wrote:
On Thu, Aug 01, 2019 at 07:16:19PM -0700, john.hubb...@gmail.com wrote:
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder versions"). That commit
has an extensive description of the
On 8/2/19 9:09 AM, Weiny, Ira wrote:
On 02.08.19 07:48, John Hubbard wrote:
On 8/1/19 9:36 PM, Juergen Gross wrote:
On 02.08.19 04:19, john.hubb...@gmail.com wrote:
From: John Hubbard
...
If that's not the case (both here, and in 3 or 4 other patches in this
series, then as you said, I
On 8/2/19 7:52 AM, Jan Kara wrote:
On Fri 02-08-19 07:24:43, Matthew Wilcox wrote:
On Fri, Aug 02, 2019 at 02:41:46PM +0200, Jan Kara wrote:
On Fri 02-08-19 11:12:44, Michal Hocko wrote:
On Thu 01-08-19 19:19:31, john.hubb...@gmail.com wrote:
[...]
2) Convert all of the call sites for
flight 139647 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139647/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-armhf-armhf-xl
> IOW, in response to GP, I was going to counter-suggest what you suggest
> in this email. :-)
>
> Are you up for taking a stab at something like `gengotypes.py`?
Yes, I think I can handle that.
-NR
___
Xen-devel mailing list
On 8/1/19 11:29 PM, Jens Wiklander wrote:
On Fri, Aug 2, 2019 at 4:20 AM wrote:
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide
On 8/2/19 2:19 AM, Joonas Lahtinen wrote:
Quoting john.hubb...@gmail.com (2019-08-02 05:19:37)
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a
On 03/07/2019 11:47, Jan Beulich wrote:
On 24.05.19 at 17:15, wrote:
>> --- a/tools/tests/x86_emulator/Makefile
>> +++ b/tools/tests/x86_emulator/Makefile
>> @@ -149,7 +149,7 @@ $(addsuffix .h,$(TESTCASES)): %.h: %.c testcase.mk
>> Makefile
>> (echo 'static const unsigned int
flight 139637 freebsd-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139637/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
freebsd f66d5bcdd266eb22421e6f81a8f4530d1627b4a8
baseline version:
freebsd
Hello Juergen
I would like to see this in Xen 4.13:
https://lists.xenproject.org/archives/html/xen-devel/2019-08/msg00253.html
So, please add:
=== ARM ===
* Renesas IPMMU-VMSA support + Linux's iommu_fwspec (V2)
- Oleksandr Tyshchenko
--
Regards,
Oleksandr Tyshchenko
On 02/08/2019 17:16, George Dunlap wrote:
> Commits ec83f825627 "mm.h: add helper function to test-and-clear
> _PGC_allocated" (and subsequent fix-up 44a887d021d "mm.h: fix BUG_ON()
> condition in put_page_alloc_ref()") introduced a BUG_ON() to detect
> unsafe behavior of callers.
>
>
From: Oleksandr Tyshchenko
We need to have some abstract way to add new device to the IOMMU
based on the generic IOMMU DT binding [1] which can be used for
both DT (right now) and ACPI (in future).
For that reason we can borrow the idea used in Linux these days
called "iommu_fwspec". Having
From: Oleksandr Tyshchenko
Next patch in this series will make use of it.
Original patch was initially posted by Sameer Goel:
https://lists.xen.org/archives/html/xen-devel/2017-06/msg00858.html
This could be considered as another attempt to add it:
From: Oleksandr Tyshchenko
The purpose of this patch series is to add IPMMU-VMSA support to Xen on ARM.
Besides new IOMMU driver, this series contains "iommu_fwspec" support
and new API iommu_add_dt_device() for adding DT device to IOMMU.
The IPMMU-VMSA is VMSA-compatible I/O Memory Management
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 and interconnect networks.
Please note, current driver is supposed to work only with newest
Gen3 SoCs
From: Oleksandr Tyshchenko
This patch adds new iommu_add_dt_device API for adding DT device
to the IOMMU using generic IOMMU DT binding [1] and previously
added "iommu_fwspec" support.
New function parses the DT binding, prepares "dev->iommu_fwspec"
with correct information and calls the IOMMU
From: Oleksandr Tyshchenko
Introduce a separate file to keep various helpers which could be used
by more than one IOMMU driver in order not to duplicate code.
The first condidates to be moved to the new file are SMMU driver's
"map_page/unmap_page" callbacks. There callbacks neither contain any
From: Oleksandr Tyshchenko
This patch adds minimal required support to General IOMMU framework
to be able to handle a case when IOMMU driver requesting deferred
probing for a device.
In order not to pull Linux's error code (-EPROBE_DEFER) to Xen
we have chosen -EAGAIN to be used for indicating
flight 139621 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139621/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemuu-rhel6hvm-intel 12 guest-start/redhat.repeat fail REGR.
vs. 139563
Tests
Commits ec83f825627 "mm.h: add helper function to test-and-clear
_PGC_allocated" (and subsequent fix-up 44a887d021d "mm.h: fix BUG_ON()
condition in put_page_alloc_ref()") introduced a BUG_ON() to detect
unsafe behavior of callers.
Unfortunately this condition still turns out to be too strict.
>
> On 02.08.19 07:48, John Hubbard wrote:
> > On 8/1/19 9:36 PM, Juergen Gross wrote:
> >> On 02.08.19 04:19, john.hubb...@gmail.com wrote:
> >>> From: John Hubbard
> > ...
> >>> diff --git a/drivers/xen/privcmd.c b/drivers/xen/privcmd.c index
> >>> 2f5ce7230a43..29e461dbee2d 100644
> >>> ---
The x86 version of get_user_pages_fast() relies on disabled interrupts to
synchronize gup_pte_range() between gup_get_pte(ptep); and get_page() against
a parallel munmap. The munmap side nulls the pte, then flushes TLBs, then
releases the page. As TLB flush is done synchronously via IPI disabling
Signed-off-by: Anthony PERARD
---
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 a/tools/libxl/libxl_domain.c
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
---
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 92eeeb27f0..6b3e388a18 100644
--- a/tools/libxl/libxl_usb.c
+++
The QMP command "query-cpus" is called from different places, extract
the algorithm that parse the answer into a separate function.
Signed-off-by: Anthony PERARD
---
tools/libxl/libxl_domain.c | 69 ++
1 file changed, 40 insertions(+), 29 deletions(-)
diff
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
---
tools/libxl/libxl_usb.c | 79 +++--
1 file changed, 61 insertions(+), 18
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
---
Notes:
In do_pci_remove, instead of using a poll loop { ev_timer ; query-pci },
it could be possible to listen to events sent
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
Signed-off-by: Anthony PERARD
---
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
index
`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
---
tools/libxl/libxl_device.c | 2 ++
tools/libxl/libxl_internal.h | 1 +
2
Signed-off-by: Anthony PERARD
---
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 80797c5ed2..d78ffa6b60 100644
--- a/tools/libxl/libxl_domain.c
+++
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
---
tools/libxl/libxl_internal.h | 1 -
tools/libxl/libxl_pci.c | 288 ---
tools/libxl/libxl_qmp.c
Signed-off-by: Anthony PERARD
---
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 246c570121..c00356a2f1 100644
---
Signed-off-by: Anthony PERARD
---
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 8e3a419805..2c11896f9e 100644
--- a/tools/libxl/libxl_usb.c
+++
Signed-off-by: Anthony PERARD
---
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 cc176f6d01..5975c1d192 100644
--- a/tools/libxl/libxl_usb.c
+++
Signed-off-by: Anthony PERARD
---
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 5975c1d192..92eeeb27f0 100644
--- a/tools/libxl/libxl_usb.c
+++
Signed-off-by: Anthony PERARD
---
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 52a8bd7895..f3c39fa86f 100644
--- a/tools/libxl/libxl_domain.c
+++
Signed-off-by: Anthony PERARD
---
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 9639d491d9..9aabad74fa 100644
--- a/tools/libxl/libxl_qmp.c
+++
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
---
tools/libxl/libxl_usb.c |
This is in preparation of using asynchronous operation to communicate
with QEMU via QMP (libxl__ev_qmp).
Signed-off-by: Anthony PERARD
---
tools/libxl/libxl_domain.c | 49 ++--
tools/libxl/libxl_internal.h | 6 +-
tools/libxl/libxl_pci.c | 221 ++-
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
---
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:
Removed libxl__qmp_cpu_add since it's not used anymore.
`cpumap' arg of libxl__set_vcpuonline_xenstore is constified.
Signed-off-by: Anthony PERARD
---
tools/libxl/libxl_domain.c | 205 ++-
tools/libxl/libxl_internal.h | 2 -
tools/libxl/libxl_qmp.c |
There are no more users.
Signed-off-by: Anthony PERARD
---
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 8dea44b221..5c15a73a08 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
---
tools/libxl/libxl_domain.c | 163 ---
tools/libxl/libxl_internal.h | 3 -
tools/libxl/libxl_qmp.c | 38
3 files changed, 131
libxl__domain_unpause is a reimplementation of
libxl__domain_unpause_deprecated with asynchronous operation.
Signed-off-by: Anthony PERARD
---
tools/libxl/libxl_domain.c | 52
tools/libxl/libxl_internal.h | 5 +++-
2 files changed, 56 insertions(+), 1
On 7/31/19 10:22 PM, Nicholas Rosbrook wrote:
>> I looked at the thing about naked returns, and didn't really understand
>> it; but anyway I'm happy to have things modified to be more Go-like. I
>> definitely "speak" Go with a funny accent.
>
> TL;DR: Naked returns exist; don't use them (with
On Thu, Aug 01, 2019 at 06:00:48PM +0200, Juergen Gross wrote:
> This email only tracks big items for xen.git tree. Please reply for items you
> would like to see in 4.13 so that people have an idea what is going on and
> prioritise accordingly.
If I can be bold, I'd like to see some more QEMU
On 01.08.2019 12:22, Chao Gao wrote:
> --- a/xen/arch/x86/microcode.c
> +++ b/xen/arch/x86/microcode.c
> @@ -189,12 +189,20 @@ static DEFINE_SPINLOCK(microcode_mutex);
>
> DEFINE_PER_CPU(struct cpu_signature, cpu_sig);
>
> -struct microcode_info {
> -unsigned int cpu;
> -uint32_t
On 8/1/19 7:59 PM, Nicholas Rosbrook wrote:
>> With that said, what are your expectations for the generated Go code at this
>> point?
>> Do you think we should try to generate the pieces that call into libxl? Or,
>> do you think
>> the code generation should be limited to the structs and
Hi,
On the quest to have QEMU depriviledge, we need to make quite a few changes to
libxl. This patch series rework quite a few libxl feature to use libxl__ev_qmp,
which is the new asynchronous way of communicating with QEMU in libxl.
Unfortunately, some libxl functions (in the public API) are
.. because it makes QMP calls which are going to be async.
Signed-off-by: Anthony PERARD
---
tools/libxl/libxl.h| 12 +++-
tools/libxl/libxl_domain.c | 12
tools/xl/xl_misc.c | 4 ++--
tools/xl/xl_vmcontrol.c| 4 ++--
4 files changed, 23 insertions(+),
.. because it makes QMP calls which are going to be async.
Signed-off-by: Anthony PERARD
---
tools/libxl/libxl.h| 14 +-
tools/libxl/libxl_domain.c | 12
tools/xl/xl_cpupool.c | 2 +-
tools/xl/xl_vcpu.c | 2 +-
4 files changed, 23 insertions(+), 7
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
---
tools/libxl/libxl.h | 13 -
tools/libxl/libxl_qmp.c | 9 +
tools/xl/xl_misc.c | 2 +-
3 files changed, 18 insertions(+), 6 deletions(-)
diff --git a/tools/libxl/libxl.h
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
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
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
---
.. because it makes QMP calls which are going to be async.
Signed-off-by: Anthony PERARD
---
tools/libxl/libxl.h| 12 +++-
tools/libxl/libxl_domain.c | 14 +++---
tools/xl/xl_info.c | 3 ++-
tools/xl/xl_saverestore.c | 3 ++-
tools/xl/xl_vmcontrol.c| 3
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
On 8/2/19 3:44 PM, Jan Beulich wrote:
> On 30.07.2019 18:44, Paul Durrant wrote:
>> --- a/xen/common/grant_table.c
>> +++ b/xen/common/grant_table.c
>> @@ -1682,6 +1682,14 @@ gnttab_unpopulate_status_frames(struct domain *d,
>> struct grant_table *gt)
>> struct page_info *pg =
On 01.08.2019 12:22, Chao Gao wrote:
> apply_microcode()'s always loading the cached ucode patch forces
> a patch to be stored before being loading. Make apply_microcode()
> accept a patch pointer to remove the limitation so that a patch
> can be stored after a successful loading.
>
>
On 01.08.2019 12:22, Chao Gao wrote:
> --- a/xen/arch/x86/microcode.c
> +++ b/xen/arch/x86/microcode.c
> @@ -277,6 +277,9 @@ static long do_microcode_update(void *_info)
> if ( error )
> info->error = error;
>
> +if ( microcode_ops->end_update )
> +
On 01.08.2019 12:22, Chao Gao wrote:
> --- a/xen/arch/x86/microcode_amd.c
> +++ b/xen/arch/x86/microcode_amd.c
> @@ -78,23 +78,23 @@ struct mpbhdr {
> static DEFINE_SPINLOCK(microcode_update_lock);
>
> /* See comment in start_update() for cases when this routine fails */
> -static int
On 01.08.2019 12:22, Chao Gao wrote:
> Remove the per-cpu cache field in struct ucode_cpu_info since it has
> been replaced by a global cache. It would leads to only one field
> remaining in ucode_cpu_info. Then, this struct is removed and the
> remaining field (cpu signature) is stored in per-cpu
On 01.08.2019 12:22, Chao Gao wrote:
> Previously, a per-cpu ucode cache is maintained. Then each CPU had one
> per-cpu update cache and there might be multiple versions of microcode.
> Thus microcode_resume_cpu tried best to update microcode by loading
> every update cache until a successful
On Fri 02-08-19 07:24:43, Matthew Wilcox wrote:
> On Fri, Aug 02, 2019 at 02:41:46PM +0200, Jan Kara wrote:
> > On Fri 02-08-19 11:12:44, Michal Hocko wrote:
> > > On Thu 01-08-19 19:19:31, john.hubb...@gmail.com wrote:
> > > [...]
> > > > 2) Convert all of the call sites for get_user_pages*(), to
On 01.08.2019 12:22, Chao Gao wrote:
> +bool microcode_update_cache(struct microcode_patch *patch)
> +{
> +
> +ASSERT(spin_is_locked(_mutex));
> +
> +if ( !microcode_cache )
> +microcode_cache = patch;
> +else if ( microcode_ops->compare_patch(patch, microcode_cache) ==
> +
On 30.07.2019 18:44, Paul Durrant wrote:
> --- a/xen/common/grant_table.c
> +++ b/xen/common/grant_table.c
> @@ -1682,6 +1682,14 @@ gnttab_unpopulate_status_frames(struct domain *d,
> struct grant_table *gt)
> struct page_info *pg = virt_to_page(gt->status[i]);
> gfn_t gfn =
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-5.3a-rc3-tag
xen: fixes for 5.3-rc3
It contains:
- a small cleanup
- a fix for a build error on ARM with some configs
- a fix of a patch for the Xen gntdev driver
- 3 patches for
On Thu, Aug 01, 2019 at 07:19:57PM -0700, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> For pages that were retained via get_user_pages*(), release those pages
> via the new put_user_page*() routines, instead of via put_page() or
> release_pages().
>
> This is part a tree-wide
On Fri, 2019-08-02 at 13:11 +0100, Andrew Cooper wrote:
> On 02/08/2019 13:00, Dario Faggioli wrote:
> > On Mon, 2019-07-29 at 12:18 -0500, Doug Goldstein wrote:
> > >
> > > Will you be pushing the rebuilt container or do you need me to do
> > > that?
> >
> > So, I guess someone else, with enough
On Fri, Aug 02, 2019 at 02:41:46PM +0200, Jan Kara wrote:
> On Fri 02-08-19 11:12:44, Michal Hocko wrote:
> > On Thu 01-08-19 19:19:31, john.hubb...@gmail.com wrote:
> > [...]
> > > 2) Convert all of the call sites for get_user_pages*(), to
> > > invoke put_user_page*(), instead of put_page().
flight 139627 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/139627/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 139585
test-armhf-armhf-libvirt-raw 13
On 01.08.19 13:17, Julien Grall wrote:
All the commit message is based on "performance improvement" Now you are selling it as this is confusing.
Sorry Julien, I have no more arguments for you.
I'll drop these two patches for the next iteration.
--
Sincerely,
Andrii Anisov.
Hi,
/!\/!\/!\
I am not a scheduler expert so my view maybe be wrong. Dario feel free to
correct me :).
/!\/!\/!\
On 02/08/2019 14:07, Andrii Anisov wrote:
On 02.08.19 12:15, Julien Grall wrote:
I can make such a list, how it is done in this series:
From the list below it is not clear
On 01.08.2019 12:22, Chao Gao wrote:
> Sometimes, an ucode with a level lower than or equal to current CPU's
> patch level is useful. For example, to work around a broken bios which
> only loads ucode for BSP, when BSP parses an ucode blob during bootup,
> it is better to save an ucode with lower
On 01.08.2019 12:22, Chao Gao wrote:
> --- a/xen/arch/x86/microcode_amd.c
> +++ b/xen/arch/x86/microcode_amd.c
> @@ -433,6 +433,9 @@ static int cpu_request_microcode(unsigned int cpu, const
> void *buf,
> goto out;
> }
>
> +mc_amd->equiv_cpu_table_size = 0;
> +
On 02/08/2019, 14:03, "Julien Grall" wrote:
On 02/08/2019 14:02, Julien Grall wrote:
> Hi Jan,
>
> On 02/08/2019 13:52, Jan Beulich wrote:
>> On 02.08.2019 13:14, Lars Kurth wrote:
1.5.4 Sending Patches Manually
>>> This should be removed or state
On 01.08.2019 12:22, Chao Gao wrote:
> --- a/xen/arch/x86/microcode_intel.c
> +++ b/xen/arch/x86/microcode_intel.c
> @@ -134,14 +134,35 @@ static int collect_cpu_info(unsigned int cpu_num,
> struct cpu_signature *csig)
> return 0;
> }
>
> -static inline int microcode_update_match(
> -
On 01.08.2019 12:22, Chao Gao wrote:
> --- a/xen/arch/x86/microcode.c
> +++ b/xen/arch/x86/microcode.c
> @@ -383,10 +383,15 @@ static struct notifier_block microcode_percpu_nfb = {
>
> int __init early_microcode_update_cpu(bool start_update)
> {
> +unsigned int cpu = smp_processor_id();
Hi Andrii,
On 02/08/2019 13:24, Andrii Anisov wrote:
On 02.08.19 12:03, Julien Grall wrote:
A fair amount of leave_hypervisor_tail() deal with the guest itself (i.e vGIC,
P2M...)
All that stuff is what hypervisor does for the guest. And does behind the
guest's back.
Please define
On 02.08.2019 11:22, Roger Pau Monne wrote:
> Switch rmrr_identity_mapping to use iommu_{un}map in order to
> establish RMRR mappings for PV domains, like it's done in
> arch_iommu_hwdom_init. This solves the issue of a PV hardware domain
> not getting RMRR mappings because
With core or socket scheduling we need to know the number of siblings
per scheduling unit before we can setup the scheduler properly. In
order to prepare that do cpupool0 population only after all cpus are
up.
With that in place there is no need to create cpupool0 earlier, so
do that just before
Today a cpu which is removed from the system is taken directly from
Pool0 to the offline state. This will conflict with the new idle
scheduler, so remove it from Pool0 first. Additionally accept removing
a free cpu instead of requiring it to be in Pool0.
For the resume failed case we need to call
On 02.08.19 12:15, Julien Grall wrote:
I can make such a list, how it is done in this series:
From the list below it is not clear what is the split between hypervisor time
and guest time. See some of the examples below.
I guess your question is *why* do I split hyp/guest time in such a
Instead of having a full blown scheduler running for the free cpus
add a very minimalistic scheduler for that purpose only ever scheduling
the related idle vcpu. This has the big advantage of not needing any
per-cpu, per-domain or per-scheduling unit data for free cpus and in
turn simplifying
1 - 100 of 140 matches
Mail list logo
