>>> On 10.07.15 at 08:21, wrote:
>
>> -Original Message-
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Thursday, July 09, 2015 3:26 PM
>> To: Wu, Feng; Tian, Kevin
>> Cc: Andrew Cooper; george.dun...@eu.citrix.com; Zhang, Yang Z;
>> xen-devel@lists.xen.org; k...@xen.org
>> Su
>>> On 10.07.15 at 07:59, wrote:
> If you agree with doing all this in a central place, maybe we can create
> an arch hook for 'struct scheduler' to do this and call it in all the places
> vcpu_runstate_change() gets called. What is your opinion about this?
Doing this in a central place is certai
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, July 09, 2015 3:26 PM
> To: Wu, Feng; Tian, Kevin
> Cc: Andrew Cooper; george.dun...@eu.citrix.com; Zhang, Yang Z;
> xen-devel@lists.xen.org; k...@xen.org
> Subject: RE: [Xen-devel] [v3 12/15] vmx: poste
On Thu, Jul 9, 2015 at 7:27 PM, Julien Grall wrote:
>
>
> On 09/07/2015 12:30, Manish Jaggi wrote:
>>
>> On Thursday 09 July 2015 01:38 PM, Julien Grall wrote:
>>>
>>> On 09/07/2015 08:13, Manish Jaggi wrote:
>
>
> If this was a domctl there might be scope for accepting an
> implem
The first issue (which would really be relevant to the documentation
patch) is that the documentation is in a separate commit. There are
sometimes valid reasons for doing this. I'm not sure if they apply,
Wei suggested we should organize/spit all patches according to libxl,
libxc, xc and xl.
> -Original Message-
> From: George Dunlap [mailto:george.dun...@eu.citrix.com]
> Sent: Thursday, July 09, 2015 10:28 PM
> To: Dario Faggioli; Jan Beulich
> Cc: Tian, Kevin; Wu, Feng; andrew.coop...@citrix.com; xen-devel; Zhang, Yang
> Z; k...@xen.org
> Subject: Re: [Xen-devel] Fwd: [v3 1
tools/libxl/libxl_dom.c | 5 +++
tools/libxl/libxl_internal.h | 24 +
tools/libxl/libxl_x86.c | 83
...
diff --git a/tools/libxl/libxl_dom.c b/tools/libxl/libxl_dom.c
index 62ef120..41da479 100644
--- a/tools/libxl/libxl_dom.
flight 59267 linux-3.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59267/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-win7-amd64 6 xen-boot fail REGR. vs. 30511
Tests which are failing
I have found a few things in this patch which I would like to see
improved. See below.
Given how late I am with this review, I do not feel that I should be
nacking it at this time. You have a tools ack from Wei, so my
comments are not a blocker for this series.
But if you need to respin, pleas
On 07/10/2015 02:26 AM, Andrew Cooper wrote:
This series adds support for the libxl migration v2 stream, and untangles the
existing layering violations of the toolstack and qemu records.
It can be found on the branch "libxl-migv2-v2"
git://xenbits.xen.org/people/andrewcoop/xen.git
http://x
Hi, all:
I am trying to improve the performance of netfront/netback, and I found
that there were some discussion about PV network performance improvement in
devel mailing list ([1]). The proposals mentioned in [1] are helpful, such as
multipage ring, multiqueue, etc, and some of them have
flight 59275 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59275/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail pass in 59143
Regressions which are regarded as all
> @@ -546,6 +652,23 @@ int main(int argc, char *argv[])
> }
>
> break;
> +case VM_EVENT_REASON_SINGLESTEP:
> +printf("Singlestep: rip=%016"PRIx64", vcpu %d\n",
> + req.regs.x86.rip,
> + req.vcp
On 07/10/2015 02:26 AM, Andrew Cooper wrote:
as a wrapper to kill(2), and use it in preference to sendig in
s/sendig/sendsig/
libxl_save_callout.c.
Signed-off-by: Andrew Cooper
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
Logically new in v2 - split out from a v1 change which was it
> diff --git a/xen/include/public/vm_event.h b/xen/include/public/vm_event.h
> index 577e971..6dfa9db 100644
> --- a/xen/include/public/vm_event.h
> +++ b/xen/include/public/vm_event.h
> @@ -47,6 +47,16 @@
> #define VM_EVENT_FLAG_VCPU_PAUSED (1 << 0)
> /* Flags to aid debugging mem_event */
>
From: Tamas K Lengyel
Working altp2m test-case. Extended the test tool to support singlestepping
to better highlight the core feature of altp2m view switching.
Signed-off-by: Tamas K Lengyel
Signed-off-by: Ed White
---
tools/tests/xen-access/xen-access.c | 173 ++--
From: Tamas K Lengyel
Wrappers to issue altp2m hvmops.
Signed-off-by: Tamas K Lengyel
Signed-off-by: Ravi Sahita
---
tools/libxc/Makefile | 1 +
tools/libxc/include/xenctrl.h | 21
tools/libxc/xc_altp2m.c | 237 ++
3 files changed
From: Ravi Sahita
Signed-off-by: Ravi Sahita
Acked-by: Daniel De Graaf
---
tools/flask/policy/policy/modules/xen/xen.if | 4 ++--
xen/arch/x86/hvm/hvm.c | 6 ++
xen/include/xsm/dummy.h | 12
xen/include/xsm/xsm.h
The altp2mhvm and nestedhvm parameters are mutually
exclusive and cannot be set together.
Signed-off-by: Ed White
Reviewed-by: Andrew Cooper for the hypervisor bits.
---
docs/man/xl.cfg.pod.5 | 12
tools/libxl/libxl.h | 6 ++
tools/libxl/libxl_create.c
Signed-off-by: Ed White
---
xen/arch/x86/hvm/hvm.c | 138
xen/include/public/hvm/hvm_op.h | 82
2 files changed, 220 insertions(+)
diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
index bda6c1e..23cd507 10064
Add the remaining routines required to support enabling the alternate
p2m functionality.
Signed-off-by: Ed White
Reviewed-by: Andrew Cooper
---
xen/arch/x86/hvm/hvm.c | 58 +-
xen/arch/x86/mm/hap/Makefile | 1 +
xen/arch/x86/mm/hap/altp2m_hap.c | 98 ++
xen/arch/x
Add a flag to indicate that a memory event occurred in an alternate p2m
and a field containing the p2m index. Allow any event response to switch
to a different alternate p2m using the same flag and field.
Modify p2m_mem_access_check() to handle alternate p2m's.
Signed-off-by: Ed White
Acked-by:
From: George Dunlap
The existing ept_set_entry() and ept_get_entry() routines are extended
to optionally set/get suppress_ve. Passing -1 will set suppress_ve on
new p2m entries, or retain suppress_ve flag on existing entries.
Signed-off-by: George Dunlap
---
xen/arch/x86/mm/mem_sharing.c | 5
From: Ravi Sahita
Signed-off-by: Ravi Sahita
---
xen/arch/x86/hvm/emulate.c | 19 +--
xen/arch/x86/hvm/vmx/vmx.c | 29 +
xen/arch/x86/x86_emulate/x86_emulate.c | 20 +++-
xen/arch/x86/x86_emulate/x86_emulate.h |
Add the basic data structures needed to support alternate p2m's and
the functions to initialise them and tear them down.
Although Intel hardware can handle 512 EPTP's per hardware thread
concurrently, only 10 per domain are supported in this patch for
performance reasons.
The iterator in hap_enab
Implement and hook up the code to enable VMX support of VMFUNC and #VE.
VMFUNC leaf 0 (EPTP switching) emulation is added in a later patch.
Signed-off-by: Ed White
Reviewed-by: Andrew Cooper
Acked-by: Jun Nakajima
---
xen/arch/x86/hvm/vmx/vmx.c | 138 +
As implemented here, only supported on platforms with VMX HAP.
By default this functionality is force-disabled, it can be enabled
by specifying altp2m=1 on the Xen command line.
Signed-off-by: Ed White
Reviewed-by: Andrew Cooper
---
docs/misc/xen-command-line.markdown | 7 +++
xen/arch/x8
Currently, neither is enabled globally but may be enabled on a per-VCPU
basis by the altp2m code.
Remove the check for EPTE bit 63 == zero in ept_split_super_page(), as
that bit is now hardware-defined.
Signed-off-by: Ed White
Reviewed-by: Andrew Cooper
Acked-by: George Dunlap
Acked-by: Jun N
This set of patches adds support to hvm domains for EPTP switching by creating
multiple copies of the host p2m (currently limited to 10 copies).
The primary use of this capability is expected to be in scenarios where access
to memory needs to be monitored and/or restricted below the level at which
In preparation for selectively enabling #VE in a later patch, set
suppress #VE on all EPTE's.
Suppress #VE should always be the default condition for two reasons:
it is generally not safe to deliver #VE into a guest unless that guest
has been modified to receive it; and even then for most EPT viol
From: Andrew Cooper
For use on codepaths which would need to use domain_pause() but might be in
the target domain's context. In the case that the target domain is in
context, all other vcpus are paused.
Signed-off-by: Andrew Cooper
---
xen/common/domain.c | 28
int libxl__device_pci_setdefault(libxl__gc *gc, libxl_device_pci *pci)
{
+/* We'd like to force reserve rdm specific to a device by default.*/
+if ( pci->rdm_policy == LIBXL_RDM_RESERVE_POLICY_INVALID)
^
I have just spotted that spurious whitespace. However I won't block
> -Original Message-
> From: George Dunlap [mailto:george.dun...@eu.citrix.com]
> Sent: Thursday, July 09, 2015 8:53 PM
> To: Wu, Feng
> Cc: Dario Faggioli; Tian, Kevin; k...@xen.org; andrew.coop...@citrix.com;
> xen-devel; jbeul...@suse.com; Zhang, Yang Z
> Subject: Re: [Xen-devel] Fwd:
> -Original Message-
> From: Dario Faggioli [mailto:dario.faggi...@citrix.com]
> Sent: Thursday, July 09, 2015 8:42 PM
> To: Wu, Feng
> Cc: George Dunlap; Tian, Kevin; k...@xen.org; andrew.coop...@citrix.com;
> xen-devel; jbeul...@suse.com; Zhang, Yang Z
> Subject: Re: [Xen-devel] Fwd: [v
On 07/09/2015 04:34 AM, Ian Campbell wrote:
On Wed, 2015-07-01 at 15:03 -0600, Jim Fehlig wrote:
Perhaps. But thanks for providing a way (b_info->device_model_user) for apps to
override the libxl policy.
You mentioned in v5 that libvirt supports setting both the user and the
group and that the
flight 59254 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59254/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-libvirt 11 guest-start fail like 59086
test-amd64-amd64-libvirt 1
Currently, blkif_queue_request has 2 distinct execution path:
- Send a discard request
- Send a read/write request
The function is also allocating grants to use for generating the
request. Although, this is only used for read/write request.
Rather than having a function with 2 distinct ex
The Xen interface is using 4KB page granularity. This means that each
grant is 4KB.
The current implementation allocates a Linux page per grant. On Linux
using 64KB page granularity, only the first 4KB of the page will be
used.
We could decrease the memory wasted by sharing the page with multiple
All the ring (xenstore, and PV rings) are always based on the page
granularity of Xen.
Signed-off-by: Julien Grall
Cc: Konrad Rzeszutek Wilk
Cc: Boris Ostrovsky
Cc: David Vrabel
---
Changes in v2:
- Also update the ring mapping function
---
drivers/xen/xenbus/xenbus_client.c | 6 +
From: Julien Grall
The PV block protocol is using 4KB page granularity. The goal of this
patch is to allow a Linux using 64KB page granularity using block
device on a non-modified Xen.
The block API is using segment which should at least be the size of a
Linux page. Therefore, the driver will ha
Only use the first 4KB of the page to store the events channel info. It
means that we will wast 60KB every time we allocate page for:
* control block: a page is allocating per CPU
* event array: a page is allocating everytime we need to expand it
I think we can reduce the memory waste fo
The PV network protocol is using 4KB page granularity. The goal of this
patch is to allow a Linux using 64KB page granularity working as a
network backend on a non-modified Xen.
It's only necessary to adapt the ring size and break skb data in small
chunk of 4KB. The rest of the code is relying on
For ARM64 guests, Linux is able to support either 64K or 4K page
granularity. Although, the hypercall interface is always based on 4K
page granularity.
With 64K page granuliarty, a single page will be spread over multiple
Xen frame.
When a driver request/free a balloon page, the balloon driver wi
The PV block protocol is using 4KB page granularity. The goal of this
patch is to allow a Linux using 64KB page granularity behaving as a
block backend on a non-modified Xen.
It's only necessary to adapt the ring size and the number of request per
indirect frames. The rest of the code is relying o
The hypercall interface (as well as the toolstack) is always using 4KB
page granularity. When the toolstack is asking for mapping a series of
guest PFN in a batch, it expects to have the page map contiguously in
its virtual memory.
When Linux is using 64KB page granularity, the privcmd driver will
The console ring is always based on the page granularity of Xen.
Signed-off-by: Julien Grall
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
Cc: David Vrabel
Cc: Stefano Stabellini
Cc: Boris Ostrovsky
Cc: linuxppc-...@lists.ozlabs.org
---
drivers/tty/hvc/hvc_xen.c | 6 +++---
1 file changed, 3 insert
The hypercall interface is always using 4KB page granularity. This is
requiring to use xen page definition macro when we deal with hypercall.
Note that pfn_to_mfn is working with a Xen pfn (i.e 4KB). We may want to
rename pfn_mfn to make this explicit.
We also allocate a 64KB page for the shared
The PV network protocol is using 4KB page granularity. The goal of this
patch is to allow a Linux using 64KB page granularity using network
device on a non-modified Xen.
It's only necessary to adapt the ring size and break skb data in small
chunk of 4KB. The rest of the code is relying on the gran
Hi all,
ARM64 Linux is supporting both 4KB and 64KB page granularity. Although, Xen
hypercall interface and PV protocol are always based on 4KB page granularity.
Any attempt to boot a Linux guest with 64KB pages enabled will result to a
guest crash.
This series is a first attempt to allow those
The Xen interface is always using 4KB page. This means that a Linux page
may be split across multiple Xen page when the page granularity is not
the same.
This helper will break down a Linux page into 4KB chunk and call the
helper on each of them.
Signed-off-by: Julien Grall
Cc: Konrad Rzeszutek
Many PV drivers contain the idiom:
pfn = page_to_mfn(...) /* Or similar */
gnttab_grant_foreign_access_ref
Replace it by a new helper. Note that when Linux is using a different
page granularity than Xen, the helper only gives access to the first 4KB
grant.
This is useful where drivers are alloca
Prepare the code to support 64KB page granularity. The first
implementation will use a full Linux page per indirect and persistent
grant. When non-persistent grant is used, each page of a bio request
may be split in multiple grant.
Furthermore, the field page of the grant structure is only used to
When Linux is using 64K page granularity, every page will be slipt in
multiple non-contiguous 4K MFN (page granularity of Xen).
I'm not sure how to handle efficiently the check to know whether we can
merge 2 biovec with a such case. So for now, always says that biovec are
not mergeable.
Signed-of
All the usage of the field pfn are done using the same idiom:
pfn_to_page(grant->pfn)
This will return always the same page. Store directly the page in the
grant to clean up the code.
Signed-off-by: Julien Grall
Cc: Konrad Rzeszutek Wilk
Cc: Roger Pau Monné
Cc: Boris Ostrovsky
Cc: David Vra
The Xen hypercall interface is always using 4K page granularity on ARM
and x86 architecture.
With the incoming support of 64K page granularity for ARM64 guest, it
won't be possible to re-use the Linux page definition in Xen drivers.
Introduce Xen page definition helpers based on the Linux page
de
Currently, a grant is always based on the Xen page granularity (i.e
4KB). When Linux is using a different page granularity, a single page
will be split between multiple grants.
The new helpers will be in charge to split the Linux page into grant and
call a function given by the caller on each gran
The skb doesn't change within the function. Therefore it's only
necessary to check if we need GSO once at the beginning.
Signed-off-by: Julien Grall
Cc: Ian Campbell
Cc: Wei Liu
Cc: net...@vger.kernel.org
---
Changes in v2:
- Patch added
---
drivers/net/xen-netback/netback.c | 14 +
flight 59256 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59256/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-xsm 11 guest-start fail REGR. vs. 58842
Regressions which are reg
flight 59222 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/59222/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 58581
Tests which are failin
On Thu, Jul 09, 2015 at 04:00:41PM +0800, Jiang Liu wrote:
> Use accessor for_pci_msi_entry() to access MSI device list, so we could easily
> move msi_list from struct pci_dev into struct device later.
>
> Signed-off-by: Jiang Liu
> ---
> drivers/pci/msi.c | 39 ---
On Thu, Jul 09, 2015 at 04:00:40PM +0800, Jiang Liu wrote:
> Use accessor for_pci_msi_entry() to access MSI device list, so we could
> easily move msi_list from struct pci_dev into struct device later.
>
> Signed-off-by: Jiang Liu
Looks pretty simple. Acked- by: Konrad Rzeszutek Wilk
> ---
> a
On Wed, Jul 08, 2015 at 09:50:26PM -0400, elena.ufimts...@oracle.com wrote:
> From: Elena Ufimtseva
>
> On some platforms RMRR regions may be not specified
> in ACPI and thus will not be mapped 1:1 in dom0. This
> causes IO Page Faults and prevents dom0 from booting
> in PVH mode.
> New Xen comma
On Wed, Jul 08, 2015 at 09:50:24PM -0400, elena.ufimts...@oracle.com wrote:
> From: Elena Ufimtseva
>
> In preparation for auxiliary RMRR data provided on Xen
> command line, make RMRR adding a separate function.
> Also free memery for rmrr device scope in error path.
s/memery/memory/
>
> Sign
When a legacy stream is found, it needs to be converted to a v2 stream for the
reading logic. This is done by exec()ing the python conversion utility.
One complication is that the caller of this interface needs to assume
ownership of the output fd, to prevent it being closed while still in use in
Contains:
* Reverse-engineered notes of the legacy format from xg_save_restore.h
* Python implementation of the legacy format
* Public HVM Params used in the legacy stream
* XL header format
Signed-off-by: Andrew Cooper
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
New in v2 - removes
Libxl has now been fully adjusted not to need them.
Signed-off-by: Andrew Cooper
Acked-by: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
tools/libxl/libxl_dom.c|1 -
tools/libxl/libxl_internal.h |2 --
tools/libxl/libxl_save_callout.c | 39 +---
This is a complicated set of changes which must be done together for
bisectability.
* libxl-save-helper is updated to unconditionally use libxc migration v2.
* libxl compatibility workarounds in libxc are disabled for save operations.
* libxl__stream_write_start() is logically spliced into the
And call it when a checkpoint record is found in the libxc stream.
Some parts of this patch have been based on patches from the COLO series.
Signed-off-by: Wen Congyang
Signed-off-by: Yang Hongyang
Signed-off-by: Andrew Cooper
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
v2: Borrow suf
Libxl has now been fully adjusted not to need it.
Signed-off-by: Andrew Cooper
Acked-by: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
tools/libxc/xc_sr_common.h |5 --
tools/libxc/xc_sr_restore.c | 18 -
tools/libxc/xc_sr_restore_x86_hvm.c | 124 ---
when signalled to do so by libxl__remus_domain_checkpoint_callback()
Signed-off-by: Andrew Cooper
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
This patch has changed substantially in v2 as a result of changes earlier in
the series. No behavioural difference from v1.
---
tools/libxl/libx
This utility will take a legacy stream as in input, and produce a v2 stream as
an output. It is exec()'d by libxl to provide backwards compatibility.
Signed-off-by: Andrew Cooper
Acked-by: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
tools/python/Makefile |4 +
tools
From: Ross Lagerwall
This contains the event machinary and state machines to write non-checkpointed
migration v2 stream (with the exception of the xc_domain_save() handling which
is spliced later in a bisectable way).
Signed-off-by: Ross Lagerwall
Signed-off-by: Andrew Cooper
CC: Ian Campbell
Contains:
* Python implementation of the libxc migration v2 records
* Verification code for spec compliance
* Unit tests
Signed-off-by: Andrew Cooper
Acked-by: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
tools/python/setup.py|1 +
tools/python/xen/migration/libxc.py |
For backwards compatibility, a legacy stream needs converting before it can be
read by the v2 stream logic.
This causes the v2 stream logic to need to juggle two parallel tasks.
check_stream_finished() is introduced for the purpose of joining the tasks in
both success and error cases.
Signed-off-
From: Ross Lagerwall
C structures describing the Libxl migration v2 stream format
Signed-off-by: Ross Lagerwall
Signed-off-by: Andrew Cooper
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
v2: Move into libxl__ namespace
---
tools/libxl/libxl_sr_stream_format.h | 57 +++
Signed-off-by: Andrew Cooper
Acked-by: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
This is exceedingly useful for development, but not of practical use being
installed into a production dom0.
---
tools/python/scripts/verify-stream-v2 | 174 +
1 file changed,
This is the final bit of untangling for Remus.
Signed-off-by: Andrew Cooper
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
As before, Remus functionality is untested, but the new logic here should
handle failovers correctly. The patch has changed greatly from v1, both in a
functional sence
From: Ross Lagerwall
This contains the event machinary and state machines to read an act on a
non-checkpointed migration v2 stream (with the exception of the
xc_domain_restore() handling which is spliced later in a bisectable way).
It also contains some boilerplate to help support checkpointed s
In a remus senario, libxc will write a CHECKPOINT record, then hand ownership
of the fd to libxl. Libxl then writes any records required and finishes with
a CHECKPOINT_END record, then hands ownership of the fd back to libxc.
Signed-off-by: Andrew Cooper
CC: Ian Campbell
CC: Ian Jackson
CC: We
This is a complicated set of changes which must be done together for
bisectability.
* libxl-save-helper is updated to unconditionally use libxc migration v2.
* libxl compatibility workarounds in libxc are disabled for restore operations.
* libxl__stream_read_start() is logically spliced into th
Contains:
* Python implementation of the libxl migration v2 records
* Verification code for spec compliance
* Unit tests
Signed-off-by: Andrew Cooper
Acked-by: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
tools/python/xen/migration/libxl.py | 188 +++
tools
This is safe (as the variables will simply be unused), and is required for
correct compilation when midway through untangling the libxc/libxl
interaction.
The #define is left in place to highlight that the variables can be removed
once the untangling is complete.
Signed-off-by: Andrew Cooper
Ack
This series adds support for the libxl migration v2 stream, and untangles the
existing layering violations of the toolstack and qemu records.
It can be found on the branch "libxl-migv2-v2"
git://xenbits.xen.org/people/andrewcoop/xen.git
http://xenbits.xen.org/git-http/people/andrewcoop/xen.git
From: Ian Jackson
For some reason BSD's queue.h uses `__offsetof'. It expects it to
work just like offsetof. So use offsetof.
Reported-by: Andrew Cooper
Signed-off-by: Ian Jackson
---
tools/include/xen-external/bsd-sys-queue-h-seddery |2 ++
1 file changed, 2 insertions(+)
diff --git a
as a wrapper to kill(2), and use it in preference to sendig in
libxl_save_callout.c.
Signed-off-by: Andrew Cooper
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
Logically new in v2 - split out from a v1 change which was itself a
cherrypick-and-modify from the AO Abort series
---
tools/libx
Shortly more parameters will appear, and this saves unboxing each one.
libxl_domain_restore_params is mandatory for restore streams, and ignored for
plain creation. The old 'checkpointed_stream' was incorrectly identified as a
private parameter when it was infact public.
No functional change.
Si
This is the same as is used by libxc.
Signed-off-by: Andrew Cooper
Acked-by: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
tools/libxl/libxl_internal.h |3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h
index 5235d25..19fc425 1
Introduced at this point so the python stream conversion code has a concrete
ABI to use. Later when libxl itself starts supporting a v2 stream, it will be
added to XL_MANDATORY_FLAG_ALL.
Signed-off-by: Andrew Cooper
Acked-by: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
v2: Expand commit mes
In a future patch, we shall support automatically converting a legacy stream
to a v2 stream, in which case libxc needs to read from a different fd.
Simply overwriting restore_fd does not work; the two fd's have different
circumstances. The restore_fd needs to be returned to its origial state
befo
With migration v2, there are several moving parts needing to be juggled at
once. This requires the error handling logic to be able to query the state of
each moving part, possibly before they have been started, and be able to
cancel them.
Signed-off-by: Andrew Cooper
CC: Ian Campbell
CC: Ian Ja
Signed-off-by: Andrew Cooper
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
docs/specs/libxl-migration-stream.pandoc | 205 ++
1 file changed, 205 insertions(+)
create mode 100644 docs/specs/libxl-migration-stream.pandoc
diff --git a/docs/specs/libxl-migration-
Tiejun Chen writes ("[v7][PATCH 16/16] tools: parse to enable new rdm policy
parameters"):
> This patch parses to enable user configurable parameters to specify
> RDM resource and according policies,
>
> Global RDM parameter:
> rdm = "strategy=host,policy=strict/relaxed"
> Per-device RDM para
Tiejun Chen writes ("[v7][PATCH 13/16] libxl: construct e820 map with RDM
information for HVM guest"):
> Here we'll construct a basic guest e820 table via
> XENMEM_set_memory_map. This table includes lowmem, highmem
> and RDMs if they exist, and hvmloader would need this info
> later.
>
> Note th
Tiejun Chen writes ("[v7][PATCH 12/16] tools: introduce a new parameter to set
a predefined rdm boundary"):
> Previously we always fix that predefined boundary as 2G to handle
> conflict between memory and rdm, but now this predefined boundar
> can be changes with the parameter "rdm_mem_boundary"
Tiejun Chen writes ("[v7][PATCH 11/16] tools/libxl: detect and avoid conflicts
with RDM"):
> While building a VM, HVM domain builder provides struct hvm_info_table{}
> to help hvmloader. Currently it includes two fields to construct guest
> e820 table by hvmloader, low_mem_pgend and high_mem_pgend
- wei.l...@citrix.com wrote:
> On Thu, Jul 09, 2015 at 05:00:45PM +0100, Jan Beulich wrote:
> > >>> On 09.07.15 at 17:53, wrote:
> > > - jbeul...@suse.com wrote:
> > >> >>> On 09.07.15 at 14:07, wrote:
> > >> > You are right, it needs to be rebased. I can post later rebased
> on
> > >>
Tiejun Chen writes ("[v7][PATCH 10/16] tools: introduce some new parameters to
set rdm policy"):
> This patch introduces user configurable parameters to specify RDM
> resource and according policies,
...
> int libxl__device_pci_setdefault(libxl__gc *gc, libxl_device_pci *pci)
> {
> +/* We'd
Including the explanation of how to run these tests.
Signed-off-by: Ian Jackson
---
tools/libxl/Makefile |8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/tools/libxl/Makefile b/tools/libxl/Makefile
index cc9c152..44a4da7 100644
--- a/tools/libxl/Makefile
+++ b/tools/
We are going to use this shortly. But, it is nicely self-contained.
Signed-off-by: Ian Jackson
---
tools/libxl/Makefile |2 +-
tools/libxl/libxl_test_fdevent.c | 79 ++
tools/libxl/libxl_test_fdevent.h | 12 ++
3 files changed, 92 inse
In 31c836f4 "libxl: events: Permit timeouts to signal ao abort",
timeout callbacks take an extra rc argument.
In that patch the wrong assertion is made about the rc in
test_timedereg's `occurs' callback. Fix this to make the test pass
again.
Signed-off-by: Ian Jackson
---
tools/libxl/libxl_tes
1 - 100 of 320 matches
Mail list logo
