[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Xen-devel] [PATCH v2 0/*] xen: xen-domid-restrict impr
|
From: |
Ian Jackson |
|
Subject: |
Re: [Qemu-devel] [Xen-devel] [PATCH v2 0/*] xen: xen-domid-restrict improvements |
|
Date: |
Tue, 10 Oct 2017 18:21:43 +0100 |
Ross Lagerwall writes ("Re: [Xen-devel] [PATCH v2 0/*] xen: xen-domid-restrict
improvements"):
> If no one objects, I propose adding the following calls to
> libxendevicemodel (with underlying Xen implementations, of course) that
> would be usable after the xendevicemodel handle has been restricted.
>
> xendevicemodel_add_to_physmap(xendevicemodel_handle *dmod,
...
> xendevicemodel_pin_memory_cacheattr(xendevicemodel_handle *dmod,
...
> This is equivalent to xc_domain_pin_memory_cacheattr().
These seem fine to me. If you want this in Xen 4.10 I think you will
want to make a case to Julien (not CC'd) for a release ack.
Ian.
- Re: [Qemu-devel] [PATCH 3/8] xen: defer call to xen_restrict until after os_setup_post, (continued)
[Qemu-devel] [PATCH 5/8] xen: move xc_interface compatibility fallback further up the file, Ian Jackson, 2017/10/04
[Qemu-devel] [PATCH 2/8] xen: restrict: use xentoolcore_restrict_all, Ian Jackson, 2017/10/04
[Qemu-devel] [PATCH 4/8] xen: destroy_hvm_domain: Move reason into a variable, Ian Jackson, 2017/10/04
[Qemu-devel] [PATCH 8/8] RFC configure: do_compiler: Dump some extra info under bash, Ian Jackson, 2017/10/04
[Qemu-devel] [PATCH 6/8] xen: destroy_hvm_domain: Try xendevicemodel_shutdown, Ian Jackson, 2017/10/04
Re: [Qemu-devel] [PATCH v2 0/*] xen: xen-domid-restrict improvements, Ross Lagerwall, 2017/10/06
Re: [Qemu-devel] [PATCH v2 0/*] xen: xen-domid-restrict improvements, Ian Jackson, 2017/10/06