Re: [Xen-devel] [v4][PATCH 15/19] tools: introduce a new parameter to set a predefined rdm boundary

diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5 index 638b350..079465f 100644 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -767,6 +767,27 @@ to a given device, and "strict" is default here. Note this would override global B option. +=item B + +Number of megabytes to se

Re: [Xen-devel] [PATCH 8/8] xen/x86: Additional SMAP modes to work around buggy 32bit PV guests

>>> On 24.06.15 at 18:31, wrote: > @@ -784,6 +791,11 @@ unsigned long pv_guest_cr4_to_real_cr4(const struct vcpu > *v) > if ( v->domain->arch.vtsc ) > cr4 |= X86_CR4_TSD; > > +/* Disable SMAP behind unaware 32bit PV guests. */ > +if ( (smap_mode == smap_mode_compat) && is_

Re: [Xen-devel] vif-bridge: ip link set failed, "name" too long

On 06/25/2015 05:53 AM, Ian Campbell wrote: On Thu, 2015-06-25 at 12:36 +0100, Anthony PERARD wrote: Error: argument "tap695cf459-b0-emu" is wrong: "name" too long Under Linux IFNAMSIZ is 16, whereas this is 18 characters. Since our suffix is "-emu" we are adding 4 to the original 14, so we co

Re: [Xen-devel] [PATCH 7/8] xen/x86: Rework CR4 handling for PV guests

>>> On 25.06.15 at 18:22, wrote: > On 25/06/15 15:41, Jan Beulich wrote: > On 24.06.15 at 18:31, wrote: >>> The major change here is that v->arch.pv_vcpu.ctrlreg[4] now contains only >>> CR4 >>> bits which Xen wishes to shadow, rather than containing a mix of host and >>> guest bits. This i

[Xen-devel] [qemu-upstream-unstable test] 58880: tolerable FAIL - PUSHED

flight 58880 qemu-upstream-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/58880/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-amd64-libvirt 11 guest-start fail like 58415 Tests which did not

Re: [Xen-devel] [PATCH QEMU-XEN] xen/pt: Start with emulated PCI_COMMAND set to zero.

>>> On 25.06.15 at 19:23, wrote: > On Thu, Jun 25, 2015 at 08:34:45AM +0100, Jan Beulich wrote: >> >>> On 24.06.15 at 17:59, wrote: >> > While digging in this I realized that some shortcuts and assumptions >> > had been taken (I think I am restating what you two have already >> > realized). >> >

Re: [Xen-devel] [PATCH v2 07/12] x86/altp2m: add control of suppress_ve.

>>> On 25.06.15 at 18:36, wrote: > On 06/25/2015 01:12 AM, Jan Beulich wrote: > On 24.06.15 at 19:53, wrote: >>> On 06/24/2015 07:38 AM, Jan Beulich wrote: >>> On 22.06.15 at 20:56, wrote: > --- a/xen/include/asm-x86/p2m.h > +++ b/xen/include/asm-x86/p2m.h > @@ -237,6 +237,19

Re: [Xen-devel] [PATCH V5 2/7] libxl_read_file_contents: add new entry to read sysfs file

>>> On 6/25/2015 at 07:09 PM, in message <21899.57676.368102.982...@mariner.uk.xensource.com>, Ian Jackson wrote: > Chunyan Liu writes ("[PATCH V5 2/7] libxl_read_file_contents: add new entry > to read sysfs file"): > > Sysfs file has size=4096 but actual file content is less than that. > >

Re: [Xen-devel] [PATCH V5 2/7] libxl_read_file_contents: add new entry to read sysfs file

>>> On 6/25/2015 at 07:09 PM, in message <21899.57676.368102.982...@mariner.uk.xensource.com>, Ian Jackson wrote: > Chunyan Liu writes ("[PATCH V5 2/7] libxl_read_file_contents: add new entry > to read sysfs file"): > > Sysfs file has size=4096 but actual file content is less than that. > >

Re: [Xen-devel] [v4][PATCH 14/19] tools/libxl: detect and avoid conflicts with RDM

On 2015/6/25 19:23, Wei Liu wrote: On Tue, Jun 23, 2015 at 05:57:25PM +0800, Tiejun Chen wrote: 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_pgen

[Xen-devel] [linux-3.4 test] 58878: regressions - FAIL

flight 58878 linux-3.4 real [real] http://logs.test-lab.xenproject.org/osstest/logs/58878/ 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

Re: [Xen-devel] vTPM issues

It worked straight away on Ubuntu 15.04. Thanks a lot for your advice. On 25 Jun 2015, at 11:52, Emil Condrea mailto:emilcond...@gmail.com>> wrote: Timeouts have the standard values. Good luck with installing 15.04. On Thu, Jun 25, 2015 at 12:34 PM, Marcos Simó Picó mailto:marco...@kth.se>> wr

Re: [Xen-devel] [PATCH v2 09/12] x86/altp2m: add remaining support routines.

On 06/25/2015 06:40 AM, Razvan Cojocaru wrote: > On 06/25/2015 03:44 PM, Lengyel, Tamas wrote: >> On Wed, Jun 24, 2015 at 2:06 PM, Ed White > > wrote: >> On 06/24/2015 09:15 AM, Lengyel, Tamas wrote: >> >> +bool_t p2m_set_altp2m_mem_access(struct domain *d,

Re: [Xen-devel] [PATCH] xen: new maintainer for the RTDS scheduler

2015-06-25 5:44 GMT-07:00 Dario Faggioli : > Signed-off-by: Dario Faggioli > --- > Cc: George Dunlap > Cc: Meng Xu > --- > MAINTAINERS |5 + > 1 file changed, 5 insertions(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index 6b1068e..e6616d2 100644 > --- a/MAINTAINERS > +++ b/MAINTAINE

Re: [Xen-devel] [PATCH] Stepping up for being the maintainer of sched_rt.c

2015-06-25 5:44 GMT-07:00 Dario Faggioli : > I've been involved with this scheduler from the very beginning of the > upstreaming process (from the RT-Xen project to here). Right! Thank Dario for your help and advice! :-) > > I've been working with Meng and his group closely since then, and I now

Re: [Xen-devel] [PATCH v7 5/9] PCI: Add pci_iomap_wc() variants

On Thu, 2015-06-25 at 21:40 +, Casey Leedom wrote: > > Ah, thanks. I see now that the __raw_*() APIs don't do any of the > Endian Swizzling. Unfortunately the *_relaxed() APIs on PowerPC > are just defined as the normal *() routines. From > arch/powerpc/include/asm/io.h: > > /* >

Re: [Xen-devel] [PATCH v8 0/9] pci: add pci_iomap_wc() and pci_ioremap_wc_bar()

On Wed, 2015-06-24 at 18:22 -0700, Luis R. Rodriguez wrote: > Although I had test compiled this before just to be safe I went ahead and > successfully test-compiled this set with allmodconfig, specially since I've > now > removed the exports for the devres routines. Please let me know if these >

Re: [Xen-devel] PCI Passthrough ARM Design : Draft1

On Thursday 25 June 2015 10:56 PM, Konrad Rzeszutek Wilk wrote: On Thu, Jun 25, 2015 at 01:21:28PM +0100, Ian Campbell wrote: On Thu, 2015-06-25 at 17:29 +0530, Manish Jaggi wrote: On Thursday 25 June 2015 02:41 PM, Ian Campbell wrote: On Thu, 2015-06-25 at 13:14 +0530, Manish Jaggi wrote:

Re: [Xen-devel] race condition in xen-gntdev

On Mon, Jun 22, 2015 at 03:14:16PM -0400, Daniel De Graaf wrote: > The reason that gntdev_release didn't have a lock is because there are not > supposed to be any references to the areas pointed to by priv->maps when it > is called. However, since the MMU notifier has not yet been unregistered, >

Re: [Xen-devel] [v4][PATCH 13/19] tools/libxc: check to set args.mmio_size before call xc_hvm_build

On 2015/6/25 19:08, Wei Liu wrote: On Tue, Jun 23, 2015 at 05:57:24PM +0800, Tiejun Chen wrote: After commit 5dff8e9eedc7, "libxc/libxl: fill xc_hvm_build_args in libxl" is introduced, we won't check to set args.mmio_size inside xc_hvm_build as before. So instead, we need to do this before call

[Xen-devel] [linux-next test] 58877: tolerable FAIL

flight 58877 linux-next real [real] http://logs.test-lab.xenproject.org/osstest/logs/58877/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-i386-libvirt 11 guest-start fail like 58841 test-amd64-amd64-libvirt 11

Re: [Xen-devel] [PATCH v2 09/12] x86/altp2m: add remaining support routines.

On 06/25/2015 03:45 PM, Lengyel, Tamas wrote: > On Thu, Jun 25, 2015 at 4:46 PM, Ed White wrote: > >> On 06/25/2015 11:23 AM, Lengyel, Tamas wrote: >>> On Thu, Jun 25, 2015 at 12:48 PM, Ed White >> wrote: >>> On 06/25/2015 06:40 AM, Razvan Cojocaru wrote: > On 06/25/2015 03:44 PM, Lengy

Re: [Xen-devel] [PATCH v7 5/9] PCI: Add pci_iomap_wc() variants

On Thu, 2015-06-25 at 21:40 +, Casey Leedom wrote: > Hhmmm, so what do PowerPC Drivers do when they want to take > advantage of Write Combining? Do their own Endian Swizzling > with the __raw_*() APIs? Yeah either, we need to fix our relaxed implementation (patch welcome :-) Cheers, Ben.

Re: [Xen-devel] [PATCH v2 09/12] x86/altp2m: add remaining support routines.

On Thu, Jun 25, 2015 at 4:46 PM, Ed White wrote: > On 06/25/2015 11:23 AM, Lengyel, Tamas wrote: > > On Thu, Jun 25, 2015 at 12:48 PM, Ed White > wrote: > > > >> On 06/25/2015 06:40 AM, Razvan Cojocaru wrote: > >>> On 06/25/2015 03:44 PM, Lengyel, Tamas wrote: > On Wed, Jun 24, 2015 at 2:06

[Xen-devel] [qemu-mainline test] 58876: tolerable FAIL - PUSHED

flight 58876 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/58876/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-i386-libvirt 11 guest-start fail like 58844 test-amd64-i386-libvirt-xsm

Re: [Xen-devel] [PATCHv1 8/8] xen/balloon: use hotplugged pages for foreign mappings etc.

On Thu, Jun 25, 2015 at 06:11:03PM +0100, David Vrabel wrote: > alloc_xenballooned_pages() is used to get ballooned pages to back > foreign mappings etc. Instead of having to balloon out real pages, > use (if supported) hotplugged memory. > > This makes more memory available to the guest and reduc

Re: [Xen-devel] [PATCH v7 5/9] PCI: Add pci_iomap_wc() variants

| From: Arnd Bergmann [a...@arndb.de] | Sent: Thursday, June 25, 2015 1:44 PM | | On Thursday 25 June 2015 15:01:56 Casey Leedom wrote: | > | > Is there a reference I can read on this so I can understand | > when and where we can use the __raw_*() APIs? Can these | > Raw Read/Write operations b

Re: [Xen-devel] [PATCHv1 7/8] xen/balloon: make alloc_xenballoon_pages() always allocate low pages

On Thu, Jun 25, 2015 at 06:11:02PM +0100, David Vrabel wrote: > All users of alloc_xenballoon_pages() wanted low memory pages, so > remove the option for high memory. > > Signed-off-by: David Vrabel Reviewed-by: Daniel Kiper Daniel ___ Xen-devel mail

Re: [Xen-devel] [PATCH v2 09/12] x86/altp2m: add remaining support routines.

On Thu, Jun 25, 2015 at 4:27 PM, Ed White wrote: > On 06/25/2015 10:42 AM, Lengyel, Tamas wrote: > > On Thu, Jun 25, 2015 at 12:31 PM, Ed White > wrote: > > > >> On 06/24/2015 07:44 PM, Lengyel, Tamas wrote: > +if ( altp2m_active ) > +{ > +if ( altp2mhvm_hap_nested

Re: [Xen-devel] [PATCHv1 5/8] xen/balloon: rationalize memory hotplug stats

On Thu, Jun 25, 2015 at 08:54:45PM +0200, Daniel Kiper wrote: > On Thu, Jun 25, 2015 at 08:38:36PM +0200, Daniel Kiper wrote: > > On Thu, Jun 25, 2015 at 06:11:00PM +0100, David Vrabel wrote: > > > The stats used for memory hotplug make no sense and are fiddled with > > > in odd ways. Remove them

Re: [Xen-devel] [PATCHv1 6/8] xen/balloon: only hotplug additional memory if required

On Thu, Jun 25, 2015 at 06:11:01PM +0100, David Vrabel wrote: > Now that we track the total number of pages (included hotplugged > regions), it is easy to determine if more memory needs to be > hotplugged. > > Signed-off-by: David Vrabel > --- > drivers/xen/balloon.c | 16 +--- > 1

Re: [Xen-devel] [PATCH v7 5/9] PCI: Add pci_iomap_wc() variants

On Thursday 25 June 2015 15:01:56 Casey Leedom wrote: > > Is there a reference I can read on this so I can understand > when and where we can use the __raw_*() APIs? Can these > Raw Read/Write operations be reordered with respect to > each other or are the use of the various flavors of SYNC > i

Re: [Xen-devel] [PATCH v8 0/9] pci: add pci_iomap_wc() and pci_ioremap_wc_bar()

On Wed, Jun 24, 2015 at 06:22:13PM -0700, Luis R. Rodriguez wrote: > Luis R. Rodriguez (9): > pci: add pci_ioremap_wc_bar() > video: fbdev: i740fb: use arch_phys_wc_add() and pci_ioremap_wc_bar() > video: fbdev: kyrofb: use arch_phys_wc_add() and pci_ioremap_wc_bar() > video: fbdev: gxt4500

Re: [Xen-devel] [PATCH v2 09/12] x86/altp2m: add remaining support routines.

On 06/25/2015 11:23 AM, Lengyel, Tamas wrote: > On Thu, Jun 25, 2015 at 12:48 PM, Ed White wrote: > >> On 06/25/2015 06:40 AM, Razvan Cojocaru wrote: >>> On 06/25/2015 03:44 PM, Lengyel, Tamas wrote: On Wed, Jun 24, 2015 at 2:06 PM, Ed White >>> > wrote:

Re: [Xen-devel] [PATCH v2 00/12] Alternate p2m: support multiple copies of host p2m

On 06/25/2015 10:29 AM, Lengyel, Tamas wrote: >> >> I plan to fix the bug, such that unshare will always occur before a copy. >> I don't plan to make the altp2m's able to have shared pages. >> >> Ed >> > > For now that is of course fine, memsharing is experimental and that's what > I meant above.

Re: [Xen-devel] [PATCH v2 09/12] x86/altp2m: add remaining support routines.

On 06/25/2015 10:42 AM, Lengyel, Tamas wrote: > On Thu, Jun 25, 2015 at 12:31 PM, Ed White wrote: > >> On 06/24/2015 07:44 PM, Lengyel, Tamas wrote: +if ( altp2m_active ) +{ +if ( altp2mhvm_hap_nested_page_fault(v, gpa, gla, npfec, &p2m) >> == 1 ) +

[Xen-devel] [linux-linus test] 58873: regressions - FAIL

flight 58873 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/58873/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-rumpuserxen-amd64 15 rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 5

Re: [Xen-devel] [PATCHv1 5/8] xen/balloon: rationalize memory hotplug stats

On Thu, Jun 25, 2015 at 08:38:36PM +0200, Daniel Kiper wrote: > On Thu, Jun 25, 2015 at 06:11:00PM +0100, David Vrabel wrote: > > The stats used for memory hotplug make no sense and are fiddled with > > in odd ways. Remove them and introduce total_pages to track the total > > number of pages (both

Re: [Xen-devel] [PATCHv1 5/8] xen/balloon: rationalize memory hotplug stats

On Thu, Jun 25, 2015 at 06:11:00PM +0100, David Vrabel wrote: > The stats used for memory hotplug make no sense and are fiddled with > in odd ways. Remove them and introduce total_pages to track the total > number of pages (both populated and unpopulated) including those within > hotplugged region

Re: [Xen-devel] [PATCH v2 09/12] x86/altp2m: add remaining support routines.

On Thu, Jun 25, 2015 at 12:48 PM, Ed White wrote: > On 06/25/2015 06:40 AM, Razvan Cojocaru wrote: > > On 06/25/2015 03:44 PM, Lengyel, Tamas wrote: > >> On Wed, Jun 24, 2015 at 2:06 PM, Ed White >> > wrote: > >> On 06/24/2015 09:15 AM, Lengyel, Tamas wrote:

Re: [Xen-devel] [PATCH v2 09/12] x86/altp2m: add remaining support routines.

On 06/25/2015 07:48 PM, Ed White wrote: > On 06/25/2015 06:40 AM, Razvan Cojocaru wrote: >> On 06/25/2015 03:44 PM, Lengyel, Tamas wrote: >>> On Wed, Jun 24, 2015 at 2:06 PM, Ed White >> > wrote: >>> On 06/24/2015 09:15 AM, Lengyel, Tamas wrote: >>> >> +bool

Re: [Xen-devel] [PATCHv1 4/8] xen/balloon: find non-conflicting regions to place hotplugged memory

On Thu, Jun 25, 2015 at 06:10:59PM +0100, David Vrabel wrote: > Instead of placing hotplugged memory at the end of RAM (which may > conflict with PCI devices or reserved regions) use allocate_resource() > to get a new, suitably aligned resource that does not conflict. > > Signed-off-by: David Vrabe

[Xen-devel] [PATCH 21/35] libxl: ao abort: Provide explicit internal abort check API

Some places in libxl which can't handle abort via a libxl__ao_abortable callback might nevertheless benefit from being able to explicitly check whether abort has been requested. Provide the (fairly trivial) internal API function to do this. Signed-off-by: Ian Jackson Acked-by: Ian Campbell ---

[Xen-devel] [PATCH 02/35] libxl: suspend: switch_logdirty_done takes rc

switch_logdirty_done used to take the value to pass to libxl__xc_domain_saverestore_async_callback_done (ie, the return value from the callback). (This was mistakenly described as "ok" in the prototype, but in the definition it is "broke" and all the call sites passed 0 for success or -1 for error

Re: [Xen-devel] [PATCHv1 3/8] x86/xen: discard RAM regions above the maximum reservation

On Thu, Jun 25, 2015 at 06:10:58PM +0100, David Vrabel wrote: > During setup, discard RAM regions that are above the maximum > reservation (instead of marking them as E820_UNUSABLE). This allows > hotplug memory to be placed at these addresses. > > Signed-off-by: David Vrabel Reviewed-by: Daniel

[Xen-devel] [PATCH 08/35] libxl: Rename AO_ABORT to AO_CREATE_FAIL

We are going to introduce a new meaning for aborting an ao, so rename this to avoid confusion. Signed-off-by: Ian Jackson --- tools/libxl/libxl.c | 10 +- tools/libxl/libxl_event.c|4 ++-- tools/libxl/libxl_internal.h | 12 ++-- 3 files changed, 13 insertions

[Xen-devel] [PATCH v4 00/35] libxl ao abort request (cancellation)

This is v4 of my series to provide support for abandoning a long-running libxl operation. This abandonment is now called `abort' rather than `cancel'; this conveys the potential destructiveness, and also provides the space for us to provide a safer (more checked) cancellation, later. I have in ge

[Xen-devel] [PATCH 14/35] libxl: events: Permit timeouts to signal ao abort

The callback functions provided by users must take an rc value. This rc value can be ERROR_TIMEDOUT or ERROR_ABORTED. Users of xswait are now expected to deal correctly with ERROR_ABORTED. If they experience this, it hasn't been logged. And the caller won't log it either since it's not TIMEDOUT.

[Xen-devel] [PATCH 06/35] libxl: xswait/devstate: Move xswait to before devstate

Pure code motion. We are going to make devstate use xswait. Signed-off-by: Ian Jackson Acked-by: Ian Campbell --- tools/libxl/libxl_internal.h | 109 +- 1 file changed, 55 insertions(+), 54 deletions(-) diff --git a/tools/libxl/libxl_internal.h b/tools

Re: [Xen-devel] [PATCHv1 2/8] xen/balloon: remove scratch page left overs

On Thu, Jun 25, 2015 at 06:10:57PM +0100, David Vrabel wrote: > Commit 0bb599fd30108883b00c7d4a226eeb49111e6932 (xen: remove scratch > frames for ballooned pages and m2p override) removed the use of the > scratch page for ballooned out pages. > > Remove some left over function definitions. > > Sign

[Xen-devel] [PATCH 03/35] libxl: suspend: common suspend callbacks take rc

Change the following functions to take a libxl error code rather than a boolean "ok" value, and translate that value to the boolean expected by libxc at the last moment: domain_suspend_callback_common_done} dss->callback_common_done remus_domain_suspend_callback_common_done } domain_

[Xen-devel] [PATCH 09/35] libxl: Change some log messages to say `abandoning' rather than `aborting'

We are going to introduce application-requested aborts of (ao) operations, but these suspend failures are something different. Reword to avoid confusion. Signed-off-by: Ian Jackson --- tools/libxl/libxl_dom.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tools/libx

[Xen-devel] [PATCH 19/35] libxl: ao: Provide manip_refcnt

Previously we used in_initiator to stop the ao being freed while we were still in the initiator function (which would result in the initiator's call to lixl__ao_inprogress accessing the ao after it had been freed). We are going to introduce a new libxl entrypoint which finds, and operates on, ongo

[Xen-devel] [PATCH 16/35] libxl: domain create: Do not destroy on ao abort

If we aborted the domain creation, do not try to tear it down again Document this. This is a backwards-compatible API change since old libxl users will never abort any operations. In the current code, there is no functional change, because ERROR_ABORTED is never generated anywhere yet. Signed-of

[Xen-devel] [PATCH 17/35] libxl: ao: Record ultimate parent of a nested ao

This will be used by the abort request machinery. Signed-off-by: Ian Jackson Acked-by: Ian Campbell --- tools/libxl/libxl_event.c| 25 +++-- tools/libxl/libxl_internal.h |3 ++- 2 files changed, 17 insertions(+), 11 deletions(-) diff --git a/tools/libxl/libxl_even

[Xen-devel] [PATCH 11/35] libxl: New error codes ABORTED etc.

We introduce ERROR_ABORTED now, so that we can write code to handle it, and decreee that functions might return it, even though currently there is nowhere where this error is generated. While we're here, provide ERROR_NOTFOUND which will also be used later, but only as part of the public API. Sig

[Xen-devel] [PATCH 18/35] libxl: ao: Count the nested progeny of an ao

This will detect any "escaped" nested aos. Signed-off-by: Ian Jackson Acked-by: Ian Campbell --- tools/libxl/libxl_event.c|8 +++- tools/libxl/libxl_internal.h |1 + 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/tools/libxl/libxl_event.c b/tools/libxl/libxl_event

[Xen-devel] [PATCH 15/35] libxl: spawn: Preserve rc in error path

Make spawn provide an rc to its caller, and either pass it through from the timeout callback, or invent ERROR_FAIL, as applicable. Signed-off-by: Ian Jackson --- v4: New patch in this version of the series. --- tools/libxl/libxl_dm.c |8 +--- tools/libxl/libxl_exec.c | 36 +++

[Xen-devel] [PATCH 20/35] libxl: ao abort: Provide public ao abort request API

Provide libxl_ao_abort. There is machinery to allow an ao to register an interest in abort requests, using a libxl__ao_abortable. This API is not currently very functional: requesting abort will never have any effect. Signed-off-by: Ian Jackson --- v4: Rename from cancel to abort. Actually

[Xen-devel] [PATCH 01/35] libxl: ao internal API docs: Mention synchronous ao completion

This doc comment about ao lifecycle failed to mention the option of completing the ao during the initiator function. (Indeed, the most obvious reading would forbid it.) Restructure the comment, describe this situation, and generally improve the wording. Also, fix a grammar problem (missing word

[Xen-devel] [PATCH 04/35] libxl: suspend: Return correct error from callbacks

If a suspend callback fails, it has a libxl error code in its hand. However we must return to libxc the values that libxc expects. So we stash the libxl error code in dss->rc and fish it out again after libxc returns from the suspend call. While we're here, abolish the now-redundant `ok' variable

[Xen-devel] [PATCH 10/35] libxl: Change an internal comment to say `bail' rather than `abort'

Signed-off-by: Ian Jackson --- tools/libxl/libxl_internal.h |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h index cd1dfc3..b445a51 100644 --- a/tools/libxl/libxl_internal.h +++ b/tools/libxl/libxl_internal.h @@ -23

[Xen-devel] [PATCH 05/35] libxl: Use libxl__xswait* in libxl__ao_device

Replace the separate timeout and xenstore watch with use of libxl__xswait*. Different control flow, but no ultimate functional change apart from slight changes to the text of error messages. Signed-off-by: Ian Jackson Acked-by: Ian Campbell --- tools/libxl/libxl_device.c | 64 -

[Xen-devel] [PATCH 35/35] libxl: When save/restore helper dies, do not overwrite rc

If we already have an rc (eg from ao abort), keep it. Signed-off-by: Ian Jackson --- v4: New patch in this version of the series. --- tools/libxl/libxl_save_callout.c | 13 - 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/tools/libxl/libxl_save_callout.c b/tools/libx

[Xen-devel] [PATCH 07/35] libxl: devstate: Use libxl__xswait*

Signed-off-by: Ian Jackson Acked-by: Ian Campbell --- v3: Initialise ds->w.ao --- tools/libxl/libxl_device.c |4 +-- tools/libxl/libxl_event.c| 79 +++--- tools/libxl/libxl_internal.h | 11 +++--- 3 files changed, 41 insertions(+), 53 deletions(-

Re: [Xen-devel] [PATCHv1 1/8] mm: memory hotplug with an existing resource

On Thu, Jun 25, 2015 at 06:10:56PM +0100, David Vrabel wrote: > Add add_memory_resource() to add memory using an existing "System RAM" > resource. This is useful if the memory region is being located by > finding a free resource slot with allocate_resource(). > > Xen guests will make use of this i

[Xen-devel] [PATCH 13/35] libxl: events: Make libxl__async_exec_* pass caller an rc

The internal user of libxl__async_exec_start et al now gets an rc as well as the process's exit status. For now this is always either 0 or ERROR_FAIL, but with ao abort requests this will possibly be ABORTED or TIMEDOUT too. Signed-off-by: Ian Jackson Acked-by: Ian Campbell --- v4: Improve doc

[Xen-devel] [PATCH 24/35] libxl: Introduce DOMAIN_DESTROYED error code

This is currently reported only by the bootloader code, if the domain is destroyed while the bootloader is running. In the future it would be nice to return it for other circumstances where the domain existed when the operation started but subsequently vanished. Signed-off-by: Ian Jackson Acked-

[Xen-devel] [PATCH 12/35] libxl: events: Make timeout and async exec setup take an ao, not a gc

Change the timeout setup functions to take a libxl__ao, not a libxl__gc. This is going to be needed for ao abort, because timeouts are going to be a main hook for ao abort requests - so the timeouts need to be associated with an ao. This means that timeouts can only occur as part of a long-runnin

[Xen-devel] [PATCH 26/35] libxl: Introduce FILLZERO

FILLZERO is a macro for memset(&foo,0,sizeof(foo)). It eliminates the possiblity to make the error memset(&foo,0,sizeof(&foo)). No callers yet, but document it in CODING_STYLE. (In accordance with existing libxl policy, I haven't gone through all existing possible call sites.) Signed-off-by: Ia

[Xen-devel] [PATCH 23/35] libxl: ao abort: Note that driver domain task cannot be usefully aborted

In practice, aborting this task will cause all subsequent actual backend operations to fail, but will not actually cause the libxl_device_events_handler operation to complete. Signed-off-by: Ian Jackson CC: Roger Pau Monné Acked-by: Roger Pau Monné Acked-by: Ian Campbell --- v2: New in this ve

[Xen-devel] [PATCH 30/35] libxl: ao: datacopier callback gets an rc

libxl__datacopier_* now provides its caller's callback function with an rc value. This relieves the caller of the need to figure out an appropriate rc value. Arrange that the `other internal failure' cases now get a valid positive errno value (EIO). In a few places, assert that errno is nonzero

[Xen-devel] [PATCH 33/35] libxl: spawn: Always debug log middle child process death

Otherwise the debug log is strangely devoid of an explanation for the spawn completing. We decorate `what', as otherwise the logged message is rather alarming (especially if the death is due to us sending SIGKILL, which even happens on the success path). Signed-off-by: Ian Jackson --- v4: New pa

[Xen-devel] [PATCH 27/35] libxl: ao abort: Preparations for save/restore abort

Two unrelated non-functional changes, broken out into a pre-patch for easier review: Break out a function sendsig() in libxl_save_callout.c. Move io_fd to be a global variable in libxl_save_helper.c. Signed-off-by: Ian Jackson Acked-by: Ian Campbell --- v2: New in this version of the series. -

[Xen-devel] [PATCH 31/35] libxl: ao abort: Make datacopiers abortable

libxl__datacopier_* can now actually generate a callback with rc==ABORTED. This provides abort support during some corner cases, including (at least) copying the device model data during the end of domain save. Signed-off-by: Ian Jackson Acked-by: Ian Campbell --- v2: New in this version of the

[Xen-devel] [PATCH 29/35] libxl: ao abort: Abort libxc save/restore

Register the the save/restore helper interface with the abort machinery. When we are informed that save/restore should be aborted, we make a note of the that in our rc variable, and send the helper a SIGTERM. It will die in due course. Signed-off-by: Ian Jackson Acked-by: Ian Campbell --- v2:

[Xen-devel] [PATCH 28/35] libxl: ao abort: Handle SIGTERM in save/restore helper

During startup of the save/restore helper, set the disposition of SIGTERM appropriately. For restore, we can simply die immediately - there is no point trying to do any kind of cleanup on what is now going to be a trashed domain. For save, we want to arrange that libxc's cleanup code (eg turning

[Xen-devel] [PATCH 25/35] libxl: ao abort: Support aborting where we spot domain death

Make an active libxl__domaindeathcheck contain an active libxl__ao_abortable. Consequential changes are: * domaindeath callbacks now take an rc value. * libxl__domaindeathcheck_start takes an ao, not a gc. * bootloader_domaindeath plumbs the rc through to its caller. * libxl__domaindeathcheck_

[Xen-devel] [PATCH 34/35] libxl: libxl__ev_child pass actual pid to callback

The callbacks actually ignore this except for logging, but we should log the correct pid. Signed-off-by: Ian Jackson --- v4: New patch in this version of the series. --- tools/libxl/libxl_fork.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tools/libxl/libxl_fork.c b/t

[Xen-devel] [PATCH 32/35] libxl: Fix libxl__get_domid error reporting

Make it log something if the xenstore path does not exist. Signed-off-by: Ian Jackson --- v4: New patch in this version of the series. --- tools/libxl/libxl.c |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/tools/libxl/libxl.c b/tools/libxl/libxl.c index 54b398b..c5a

[Xen-devel] [PATCH 22/35] libxl: ao abort: Make timeouts abortable

Make libxl__ev_time* register with the abort machinery, so that libxl_ao_abort can stop any operation which has a timeout. Signed-off-by: Ian Jackson Acked-by: Ian Campbell --- v4: Do not immediately deregister the abortable (!) --- tools/libxl/libxl_event.c| 28 ++

Re: [Xen-devel] [PATCH v2 09/12] x86/altp2m: add remaining support routines.

On Thu, Jun 25, 2015 at 12:31 PM, Ed White wrote: > On 06/24/2015 07:44 PM, Lengyel, Tamas wrote: > >> +if ( altp2m_active ) > >> +{ > >> +if ( altp2mhvm_hap_nested_page_fault(v, gpa, gla, npfec, &p2m) > == > >> 1 ) > >> +{ > >> +/* entry was lazily copied from

Re: [Xen-devel] [PATCH v2 00/12] Alternate p2m: support multiple copies of host p2m

On Thu, Jun 25, 2015 at 12:38 PM, Ed White wrote: > On 06/25/2015 02:00 AM, Andrew Cooper wrote: > > On 24/06/15 23:55, Ed White wrote: > >> On 06/24/2015 03:45 PM, Lengyel, Tamas wrote: > >>> On Wed, Jun 24, 2015 at 6:02 PM, Ed White > wrote: > >>> > On 06/24/2015 02:34 PM, Lengyel, Tamas

Re: [Xen-devel] [PATCH OSSTEST v3 21/22] Debian: Arrange to be able to chainload a xen.efi from grub2

On Thu, Jun 25, 2015 at 01:36:29PM +0100, Ian Jackson wrote: > Ian Campbell writes ("Re: [PATCH OSSTEST v3 21/22] Debian: Arrange to be able > to chainload a xen.efi from grub2"): > > On Thu, 2015-06-25 at 11:33 +0100, Ian Jackson wrote: > > > Is there some upstream-friendly way of achieving the s

Re: [Xen-devel] PCI Passthrough ARM Design : Draft1

On Thu, Jun 25, 2015 at 01:21:28PM +0100, Ian Campbell wrote: > On Thu, 2015-06-25 at 17:29 +0530, Manish Jaggi wrote: > > > > On Thursday 25 June 2015 02:41 PM, Ian Campbell wrote: > > > On Thu, 2015-06-25 at 13:14 +0530, Manish Jaggi wrote: > > >> On Wednesday 17 June 2015 07:59 PM, Ian Campbell

Re: [Xen-devel] [PATCH QEMU-XEN] xen/pt: Start with emulated PCI_COMMAND set to zero.

On Thu, Jun 25, 2015 at 08:34:45AM +0100, Jan Beulich wrote: > >>> On 24.06.15 at 17:59, wrote: > > While digging in this I realized that some shortcuts and assumptions > > had been taken (I think I am restating what you two have already > > realized). > > > > 1) The dev.config is (by Xen code) u

Re: [Xen-devel] [PATCH] libxl: locally attach disks with hotplug scripts for bootloader execution

On 06/25/2015 03:17 PM, Roger Pau Monne wrote: > Or else bootloader execution fails. Tested using an iSCSI disk. > > Signed-off-by: Roger Pau Monné > Reported-by: Hildebrand, Nils > Cc: Ian Jackson > Cc: Ian Campbell > Cc: Wei Liu > Cc: George Dunlap > --- > tools/libxl/libxl.c | 17

[Xen-devel] [PATCHv1 4/8] xen/balloon: find non-conflicting regions to place hotplugged memory

Instead of placing hotplugged memory at the end of RAM (which may conflict with PCI devices or reserved regions) use allocate_resource() to get a new, suitably aligned resource that does not conflict. Signed-off-by: David Vrabel --- drivers/xen/balloon.c | 63 ++

[Xen-devel] [PATCHv1 5/8] xen/balloon: rationalize memory hotplug stats

The stats used for memory hotplug make no sense and are fiddled with in odd ways. Remove them and introduce total_pages to track the total number of pages (both populated and unpopulated) including those within hotplugged regions (note that this includes not yet onlined pages). This will be usefu

[Xen-devel] [PATCHv1 1/8] mm: memory hotplug with an existing resource

Add add_memory_resource() to add memory using an existing "System RAM" resource. This is useful if the memory region is being located by finding a free resource slot with allocate_resource(). Xen guests will make use of this in their balloon driver to hotplug arbitrary amounts of memory in respon

[Xen-devel] [PATCHv1 8/8] xen/balloon: use hotplugged pages for foreign mappings etc.

alloc_xenballooned_pages() is used to get ballooned pages to back foreign mappings etc. Instead of having to balloon out real pages, use (if supported) hotplugged memory. This makes more memory available to the guest and reduces fragmentation in the p2m. If userspace is lacking a udev rule (or s

[Xen-devel] [PATCHv1 2/8] xen/balloon: remove scratch page left overs

Commit 0bb599fd30108883b00c7d4a226eeb49111e6932 (xen: remove scratch frames for ballooned pages and m2p override) removed the use of the scratch page for ballooned out pages. Remove some left over function definitions. Signed-off-by: David Vrabel --- include/xen/balloon.h |3 --- 1 file cha

[Xen-devel] [PATCHv1 3/8] x86/xen: discard RAM regions above the maximum reservation

During setup, discard RAM regions that are above the maximum reservation (instead of marking them as E820_UNUSABLE). This allows hotplug memory to be placed at these addresses. Signed-off-by: David Vrabel --- arch/x86/xen/setup.c |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) d

[Xen-devel] [PATCHv1 0/8] mm, xen/balloon: memory hotplug improvements

The series improves the use of hotplug memory in the Xen balloon driver. - Reliably find a non-conflicting location for the hotplugged memory (this fixes memory hotplug in a number of cases, particularly in dom0). - Use hotplugged memory for alloc_xenballooned_pages() (keeping more memory a

[Xen-devel] [PATCHv1 7/8] xen/balloon: make alloc_xenballoon_pages() always allocate low pages

All users of alloc_xenballoon_pages() wanted low memory pages, so remove the option for high memory. Signed-off-by: David Vrabel --- arch/x86/xen/grant-table.c |2 +- drivers/xen/balloon.c | 21 - drivers/xen/grant-table.c |2 +- driver

[Xen-devel] [PATCHv1 6/8] xen/balloon: only hotplug additional memory if required

Now that we track the total number of pages (included hotplugged regions), it is easy to determine if more memory needs to be hotplugged. Signed-off-by: David Vrabel --- drivers/xen/balloon.c | 16 +--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/drivers/xen/ball

[Xen-devel] [rumpuserxen test] 58890: regressions - FAIL

flight 58890 rumpuserxen real [real] http://logs.test-lab.xenproject.org/osstest/logs/58890/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-rumpuserxen 5 rumpuserxen-build fail REGR. vs. 33866 build-i386-rumpuserxe

Re: [Xen-devel] [PATCH v2 09/12] x86/altp2m: add remaining support routines.

On 06/25/2015 06:40 AM, Razvan Cojocaru wrote: > On 06/25/2015 03:44 PM, Lengyel, Tamas wrote: >> On Wed, Jun 24, 2015 at 2:06 PM, Ed White > > wrote: >> On 06/24/2015 09:15 AM, Lengyel, Tamas wrote: >> >> +bool_t p2m_set_altp2m_mem_access(struct domain *d,

Re: [Xen-devel] [PATCH 2/4] xen: x86 / cpupool: clear the proper cpu_valid bit on pCPU teardown

On 25/06/15 17:13, Dario Faggioli wrote: > On Thu, 2015-06-25 at 16:52 +0100, Andrew Cooper wrote: >> On 25/06/15 16:04, Dario Faggioli wrote: >>> On Thu, 2015-06-25 at 15:20 +0100, Andrew Cooper wrote: On 25/06/15 13:15, Dario Faggioli wrote: > # xl cpupool-cpu-remove Pool-0 8-15 > #

Re: [Xen-devel] [PATCH v2 00/12] Alternate p2m: support multiple copies of host p2m

On 06/25/2015 02:00 AM, Andrew Cooper wrote: > On 24/06/15 23:55, Ed White wrote: >> On 06/24/2015 03:45 PM, Lengyel, Tamas wrote: >>> On Wed, Jun 24, 2015 at 6:02 PM, Ed White wrote: >>> On 06/24/2015 02:34 PM, Lengyel, Tamas wrote: > Hi Ed, > I tried the system using memsharing and

  1   2   3   4   >