[Xen-devel] [BUG] mistakenly wake in Xen's credit scheduler

Hi all, The BOOST mechanism in Xen credit scheduler is designed to prioritize VM which has I/O-intensive application to handle the I/O request in time. However, this does not always work as expected. (1) Problem description -- Suppose two VMs(named VM-I/O and VM-CPU)

[Xen-devel] [BUG] mistakenly wake in Xen's credit scheduler

Hi all, The BOOST mechanism in Xen credit scheduler is designed to prioritize VM which has I/O-intensive application to handle the I/O request in time. However, this does not always work as expected. (1) Problem description Suppose two VMs(named VM-I/O and

Re: [Xen-devel] [BUG] mistakenly wake in Xen's credit scheduler

Most mailing lists only accept text-only emails. I saw you had bold font in your last email, which may be in html rich format. > On Oct 26, 2015, at 4:30 PM, Kun Suo wrote: > > Hi all, > > The BOOST mechanism in Xen credit scheduler is designed to prioritize VM > which has

Re: [Xen-devel] ovmf fails to build in stagin-4.6

On Mon, Oct 26, Wei Liu wrote: > I think you have a stale repository. Try deleting ovmf-dir-remote ? Its always built in a new clean chroot from the same set of sources. I will see if forcing GCC49 will change anything. Olaf ___ Xen-devel mailing

[Xen-devel] [PATCH] drop get_xen_guest_handle()

Its use in the tools (and its apparent abuse in the hypervisor) are long gone. Signed-off-by: Jan Beulich --- a/xen/arch/x86/sysctl.c +++ b/xen/arch/x86/sysctl.c @@ -31,8 +31,6 @@ #include #include -#define get_xen_guest_handle(val, hnd) do { val = (hnd).p; } while (0)

Re: [Xen-devel] [V8 2/4] x86/xsaves: enable xsaves/xrstors/xsavec in xen

>>> On 27.10.15 at 02:06, wrote: > On Mon, Oct 26, 2015 at 08:03:55AM -0600, Jan Beulich wrote: >> >>> On 23.10.15 at 11:48, wrote: >> > -a &= boot_cpu_data.x86_capability[X86_FEATURE_XSAVEOPT / 32]; >> > -if (

[Xen-devel] [linux-next test] 63316: regressions - trouble: blocked/broken/fail/pass

flight 63316 linux-next real [real] http://logs.test-lab.xenproject.org/osstest/logs/63316/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 3 host-install(3) broken REGR. vs. 63240

Re: [Xen-devel] [PATCH for-4.6] xen/public: arm: Use __typeof__ rather than typeof

>>> On 26.10.15 at 19:08, wrote: > On 23/10/15 15:55, Ian Campbell wrote: >> On Fri, 2015-10-23 at 15:44 +0100, Julien Grall wrote: >>> Thank you for the explanation. I think we can do the same as x86 does >>> i.e: >>> >>> #define set_xen_guest_handle_raw(hnd, val)

Re: [Xen-devel] [PATCH v1 1/5] xsplice: Design document.

On 10/27/2015 08:08 AM, Martin Pohlack wrote: On 06.10.2015 14:57, Ross Lagerwall wrote: On 09/16/2015 10:01 PM, Konrad Rzeszutek Wilk wrote: +### xSplice interdependencies + +xSplice patches interdependencies are tricky. + +There are the ways this can be addressed: + * A single large patch

Re: [Xen-devel] ovmf fails to build in stagin-4.6

On Tue, Oct 27, Olaf Hering wrote: > I will see if forcing GCC49 will change anything. This change works for me. --- xen.spec(revision 6) +++ xen.spec(working copy) @@ -290,6 +290,7 @@ ln -sfvbn ../qemu-xen-dir-remote tools/qemu-xen-dir-remote ln -sfvbn

Re: [Xen-devel] [PATCH 06/13] x86/hvm: Scale host TSC when setting/getting guest TSC

>>> On 27.10.15 at 02:54, wrote: > On Thu, Oct 22, 2015 at 08:17:29AM -0600, Jan Beulich wrote: >> >>> On 28.09.15 at 09:13, wrote: >> > The existing hvm_set_guest_tsc_fixed() and hvm_get_guest_tsc_fixed() >> > calculate the guest TSC by adding

Re: [Xen-devel] [PATCH 06/13] x86/hvm: Scale host TSC when setting/getting guest TSC

On Thu, Oct 22, 2015 at 08:17:29AM -0600, Jan Beulich wrote: > >>> On 28.09.15 at 09:13, wrote: > > The existing hvm_set_guest_tsc_fixed() and hvm_get_guest_tsc_fixed() > > calculate the guest TSC by adding the TSC offset to the host TSC. When > > the TSC scaling is

Re: [Xen-devel] [PATCH for-4.6] xen/public: arm: Use __typeof__ rather than typeof

>>> On 26.10.15 at 19:08, wrote: > However, IIUC, the get_xen_guest_handle is only exposed to the tools and > therefore possible to modify it in order to pass the type. Am I wrong? > FWIW, I haven't seen any usage in the tools directory. Indeed. Rather than worrying

Re: [Xen-devel] [PATCH v1 1/5] xsplice: Design document.

On 06.10.2015 14:57, Ross Lagerwall wrote: > On 09/16/2015 10:01 PM, Konrad Rzeszutek Wilk wrote: >> +### xSplice interdependencies >> + >> +xSplice patches interdependencies are tricky. >> + >> +There are the ways this can be addressed: >> + * A single large patch that subsumes and replaces all

Re: [Xen-devel] [PATCH 06/13] x86/hvm: Scale host TSC when setting/getting guest TSC

On Tue, Oct 27, 2015 at 02:15:53AM -0600, Jan Beulich wrote: > >>> On 27.10.15 at 02:54, wrote: > > On Thu, Oct 22, 2015 at 08:17:29AM -0600, Jan Beulich wrote: > >> >>> On 28.09.15 at 09:13, wrote: > >> > The existing hvm_set_guest_tsc_fixed()

[Xen-devel] OSSTest nested patch PART2 -- L2 installation failure

Hi Ians, Now I get to L2 installation. Failures: 1. Use of uninitialized value $prefix in pattern match (m//) at Osstest/TestSupport.pm line 1596 sub ether_prefix($) { my ($ho) = @_; my $prefix = get_host_property($ho, 'gen-ether-prefix-base'); $prefix =~ m/^(\w+:\w+):(\w+):(\w+)$/

Re: [Xen-devel] [V8 2/4] x86/xsaves: enable xsaves/xrstors/xsavec in xen

On Tue, Oct 27, 2015 at 02:13:03AM -0600, Jan Beulich wrote: > >> > + > >> > +((struct xsave_struct *)dest)->xsave_hdr.xstate_bv = xstate_bv; > >> > +((struct xsave_struct *)dest)->xsave_hdr.xcomp_bv = 0; > >> > >> Wouldn't it be more logical to also memcpy() the header? Which > >> would

Re: [Xen-devel] [BUG] mistakenly wake in Xen's credit scheduler

On Tue, Oct 27, 2015 at 5:59 AM, suokun wrote: > Hi all, > > The BOOST mechanism in Xen credit scheduler is designed to prioritize > VM which has I/O-intensive application to handle the I/O request in > time. However, this does not always work as expected. Thanks for the

[Xen-devel] [PATCH v1] xen/serial: Return actual bytes stored in TX FIFO for OMAP

This is intended to decrease a time spending in transmitter while waiting for the free space in TX FIFO. And as result to reduce the impact of hvc on the entire system running on OMAP5/DRA7XX based platforms. Signed-off-by: Oleksandr Tyshchenko CC: Ian

Re: [Xen-devel] [BUG] mistakenly wake in Xen's credit scheduler

On Tue, 2015-10-27 at 09:44 +, George Dunlap wrote: > On Tue, Oct 27, 2015 at 5:59 AM, suokun wrote: > > Hi all, > > > > The BOOST mechanism in Xen credit scheduler is designed to > > prioritize > > VM which has I/O-intensive application to handle the I/O request in > >

[Xen-devel] [PATCH v3 4/5] xl: improve return and exit codes of cpupool related functions

Turning cpupools related functions exit codes towards using the EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary numbers or libxl return codes. Signed-off-by: Harmandeep Kaur --- v2->v3: Edited changelog. tools/libxl/xl_cmdimpl.c | 52

[Xen-devel] [PATCH v3 3/5] xl: improve return and exit codes of vcpu related functions

Turning vcpu manipulation functions exit codes toward using the EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary numbers or libxl return codes. Signed-off-by: Harmandeep Kaur --- v2->v3: Fixed return of main_vcpuset. tools/libxl/xl_cmdimpl.c | 21

Re: [Xen-devel] ovmf fails to build in stagin-4.6

On Tue, Oct 27, 2015 at 08:12:09AM +0100, Olaf Hering wrote: > On Mon, Oct 26, Wei Liu wrote: > > > I think you have a stale repository. Try deleting ovmf-dir-remote ? > > Its always built in a new clean chroot from the same set of sources. > I will see if forcing GCC49 will change anything. >

Re: [Xen-devel] [BUG] mistakenly wake in Xen's credit scheduler

On Mon, 2015-10-26 at 23:59 -0600, suokun wrote: > Hi all, > Hi, And first of all, thanks for resending in plain text, this is much appreciated. Thanks also for the report. I'm not sure I can figure out completely what you're saying that you are seeing happening, let's see if you can help me...

Re: [Xen-devel] [PATCH v1] xen/serial: Return actual bytes stored in TX FIFO for OMAP

>>> On 27.10.15 at 11:36, wrote: > --- a/xen/include/xen/8250-uart.h > +++ b/xen/include/xen/8250-uart.h > @@ -143,6 +143,15 @@ > /* Supplementary control register */ > #define UART_OMAP_SCR 0x10 I think this one is already misplaced here (as is the

Re: [Xen-devel] [PATCH for-4.6] xen/public: arm: Use __typeof__ rather than typeof

Hi Jan, On 27/10/2015 08:07, Jan Beulich wrote: On 26.10.15 at 19:08, wrote: On 23/10/15 15:55, Ian Campbell wrote: On Fri, 2015-10-23 at 15:44 +0100, Julien Grall wrote: Thank you for the explanation. I think we can do the same as x86 does i.e: #define

[Xen-devel] [PATCH] 'dom' error handled, by raising ENOMEM if failure occurs. 'xs_fd' leak handled in success path.

Signed-off-by: Lasya Venneti --- tools/xenstore/init-xenstore-domain.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/tools/xenstore/init-xenstore-domain.c b/tools/xenstore/init-xenstore-domain.c index 0d12169..b413b09 100644 ---

Re: [Xen-devel] [PATCH] drop get_xen_guest_handle()

On 27/10/15 08:04, Jan Beulich wrote: > Its use in the tools (and its apparent abuse in the hypervisor) are > long gone. > > Signed-off-by: Jan Beulich Reviewed-by: Andrew Cooper ___ Xen-devel mailing

Re: [Xen-devel] [Minios-devel] [PATCH MINI-OS v2] xenbus: notify the other end when necessary

Wei Liu, le Tue 27 Oct 2015 10:32:18 +, a écrit : > I haven't checked if cxenstored behaves the same, though. It doesn't: it checks for room in rings before sleeping. Samuel ___ Xen-devel mailing list Xen-devel@lists.xen.org

Re: [Xen-devel] [Intel-gfx] [Announcement] 2015-Q3 release of XenGT - a Mediated Graphics Passthrough Solution from Intel

Hi all, We are pleased to announce another update of Intel GVT-g for Xen. Intel GVT-g is a full GPU virtualization solution with mediated pass-through, starting from 4th generation Intel Core(TM) processors with Intel Graphics processors. A virtual GPU instance is maintained for each VM, with

Re: [Xen-devel] [PATCH v8 15/17] vmx: VT-d posted-interrupt core logic handling

>>> On 27.10.15 at 06:19, wrote: >> From: Dario Faggioli [mailto:dario.faggi...@citrix.com] >> Sent: Monday, October 26, 2015 10:40 PM >> In any case, it would have been nice, given the situation, if you'd have put >> a few >> words about, e.g., which solution you ended up

Re: [Xen-devel] [PATCH] 'dom' error handled, by raising ENOMEM if failure occurs. 'xs_fd' leak handled in success path.

On Wed, 2015-10-28 at 03:49 +0530, Lasya wrote: The description of the patch, that you previously put in a separate email, should live here. Also, this is the second version of a patch. That should be evident from the subject line (something like "[PATCH v2]"). And still about the subject line,

[Xen-devel] [PATCH v3 1/5] xl: convert main() exit codes to EXIT_[SUCCESS|FAILURE]

Turning main() function exit codes towards using the EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary numbers or libxl return codes. Also includes a document comment in xl.h stating xl process should always return EXIT_FOO and main_* can be treated as main() as if they are

[Xen-devel] [PATCH v3 2/5] xl: improve return and exit codes of scheduling related functions

Turning scheduling related functions exit codes towards using the EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary numbers or libxl return codes. - for main_*: arbitrary -> EXIT_SUCCESS|EXIT_FAILURE. - for internal fucntion: arbitrary -> 0/1. Signed-off-by:

[Xen-devel] [PATCH v3 0/5] xl: convert exit codes to EXIT_[SUCCESS|FAILURE]

*Its my "bite size contribution" that is required for applying to the Outreachy program. *main_foo() is treated somewhat as a regular main(), it is changed to return EXIT_SUCCESS or EXIT_FAILURE. *Functions that are not main_foo(), are changed to do 'return 0' or 'return 1', and then 0/1 is

[Xen-devel] [PATCH v3 5/5] xl: improve return and exit codes of parse related functions

Turning parsing related functions exit codes towards using the EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary numbers or libxl return codes. - for main_*: arbitrary -> EXIT_SUCCESS|EXIT_FAILURE. - for internal fucntion: arbitrary -> 0/1. Don't touch

[Xen-devel] [qemu-mainline test] 63317: regressions - trouble: broken/fail/pass

flight 63317 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/63317/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-pair4 host-install/dst_host(4) broken REGR. vs. 63304

Re: [Xen-devel] [Minios-devel] [PATCH MINI-OS v2] xenbus: notify the other end when necessary

On Mon, Oct 26, 2015 at 06:34:59PM +, Wei Liu wrote: > On Mon, Oct 26, 2015 at 06:11:04PM +0100, Samuel Thibault wrote: > > Wei Liu, le Mon 26 Oct 2015 16:41:15 +, a écrit : > > > The oxenstored in staging. > > > > Ok. For a first, one fishy thing at quick sight is that the only > >

Re: [Xen-devel] [PATCH v1] xen/serial: Return actual bytes stored in TX FIFO for OMAP

On 27/10/15 10:50, Jan Beulich wrote: On 27.10.15 at 11:36, wrote: >> --- a/xen/include/xen/8250-uart.h >> +++ b/xen/include/xen/8250-uart.h >> @@ -143,6 +143,15 @@ >> /* Supplementary control register */ >> #define UART_OMAP_SCR 0x10 > > I think

Re: [Xen-devel] [PATCH] xen/mm: Unmap page for direct mapped domain on decrease reservation

>>> On 27.10.15 at 12:33, wrote: > Direct mapped domain needs to retrieve the exact same underlying > physical page when the region is re-populated. > > Currently, when the memory reservation for this domain is decreased, the > request is just ignored and the page stayed

Re: [Xen-devel] [PATCH] xen/mm: Improve message in populate physmap when the domain is direct mapped

>>> On 27.10.15 at 12:49, wrote: > On 27/10/15 11:45, Andrew Cooper wrote: >> On 27/10/15 11:33, Julien Grall wrote: >>> --- a/xen/common/memory.c >>> +++ b/xen/common/memory.c >>> @@ -141,7 +141,7 @@ static void populate_physmap(struct memop_args *a) >>>

Re: [Xen-devel] [PATCHv1 2/2] passthrough: improve locking when iterating over interrupts bound to VMs

On 27/10/15 12:44, Jan Beulich wrote: On 23.10.15 at 13:05, wrote: >> radix_tree_gang_lookup() only requires a RCU read lock, not the >> per-domain event_lock. > > ... when not caring about a consistent snapshot. > >> @@ -678,9 +684,7 @@ void

Re: [Xen-devel] [PATCH] libxl: No emulated disk driver for xvdX disk

George Dunlap writes ("Re: [Xen-devel] [PATCH] libxl: No emulated disk driver for xvdX disk"): > On Tue, Oct 27, 2015 at 11:11 AM, Stefano Stabellini > wrote: > > The guest can access xvdX disks via the PV block protocol, or via > > UEFI firmare using EFI

Re: [Xen-devel] [PATCH 10/13] vmx: Detect and initialize VMX RDTSC(P) scaling

>>> On 28.09.15 at 09:13, wrote: > @@ -1805,6 +1810,8 @@ void vmcs_dump_vcpu(struct vcpu *v) > printk("IDTVectoring: info=%08x errcode=%08x\n", > vmr32(IDT_VECTORING_INFO), vmr32(IDT_VECTORING_ERROR_CODE)); > printk("TSC Offset = 0x%016lx\n",

Re: [Xen-devel] [PATCH] x86/PV: don't zero-map LDT

On 26/10/15 16:14, Jan Beulich wrote: > This effectvely reverts the LDT related part of commit cf6d39f819 > ("x86/PV: properly populate descriptor tables"), which broke demand > paged LDT handling in guests. > > Reported-by: David Vrabel > Diagnosed-by: Andrew Cooper

Re: [Xen-devel] [PATCH 11/13] vmx: Use scaled host TSC to calculate TSC offset

>>> On 28.09.15 at 09:13, wrote: > --- a/xen/arch/x86/hvm/vmx/vmx.c > +++ b/xen/arch/x86/hvm/vmx/vmx.c > @@ -1102,11 +1102,26 @@ static void vmx_handle_cd(struct vcpu *v, unsigned > long value) > > static void vmx_set_tsc_offset(struct vcpu *v, u64 offset, u64

[Xen-devel] [seabios test] 63319: trouble: broken/fail/pass

flight 63319 seabios real [real] http://logs.test-lab.xenproject.org/osstest/logs/63319/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 3 host-install(3) broken REGR. vs.

Re: [Xen-devel] [PATCH 12/13] vmx: Add a call-back to apply TSC scaling ratio to hardware

>>> On 28.09.15 at 09:13, wrote: > This patch adds a new call-back setup_tsc_scaling in struct > hvm_function_table to apply the TSC scaling ratio to hardware. For VMX, > it writes the TSC scaling ratio to VMCS field TSC_MULTIPLIER. > > Signed-off-by: Haozhong Zhang

Re: [Xen-devel] [PATCH 06/13] x86/hvm: Scale host TSC when setting/getting guest TSC

On 10/27/2015 04:44 AM, Haozhong Zhang wrote: On Thu, Oct 22, 2015 at 08:17:29AM -0600, Jan Beulich wrote: On 28.09.15 at 09:13, wrote: The existing hvm_set_guest_tsc_fixed() and hvm_get_guest_tsc_fixed() calculate the guest TSC by adding the TSC offset to the host

Re: [Xen-devel] [PATCH] libxl: No emulated disk driver for xvdX disk

On 10/27/2015 09:19 AM, Ian Jackson wrote: George Dunlap writes ("Re: [Xen-devel] [PATCH] libxl: No emulated disk driver for xvdX disk"): On Tue, Oct 27, 2015 at 11:11 AM, Stefano Stabellini wrote: The guest can access xvdX disks via the PV block protocol,

Re: [Xen-devel] [PATCH] 'dom' error handled, by raising ENOMEM if failure occurs. 'xs_fd' leak handled in success path.

On 27/10/15 11:04, Lasya Venneti wrote: > On 27 October 2015 at 16:25, Dario Faggioli > wrote: > >> On Wed, 2015-10-28 at 03:49 +0530, Lasya wrote: >> >> The description of the patch, that you previously put in a separate >> email, should live here. >> > Oh, I had

Re: [Xen-devel] [PATCH] libxl: No emulated disk driver for xvdX disk

On Tue, Oct 27, 2015 at 11:11 AM, Stefano Stabellini wrote: > On Mon, 26 Oct 2015, Boris Ostrovsky wrote: >> On 10/16/2015 10:01 AM, Ian Jackson wrote: >> > Anthony PERARD writes ("[PATCH] libxl: No emulated disk driver for xvdX >> > disk"): >> > > When a guest

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

On 10/21/2015 11:08 AM, Chunyan Liu wrote: Sysfs file has size=4096 but actual file content is less than that. Current libxl_read_file_contents will treat it as error when file size and actual file content differs, so reading sysfs file content with this function always fails. Add a new entry

Re: [Xen-devel] [PATCH V8 3/7] libxl: add pvusb API

On 10/21/2015 11:08 AM, Chunyan Liu wrote: Add pvusb APIs, including: - attach/detach (create/destroy) virtual usb controller. - attach/detach usb device - list usb controller and usb devices - some other helper functions Signed-off-by: Chunyan Liu Signed-off-by: Simon

[Xen-devel] [PATCH] xen/mm: Improve message in populate physmap when the domain is direct mapped

The current domain and the domain pointed by the variable "d" are not the same. However, when it's not possible to get a reference on the page, the target domain ID is not printed. This makes the message difficult to understand. Improve the message by printing the target domain ID.

Re: [Xen-devel] [PATCH] xen/mm: Improve message in populate physmap when the domain is direct mapped

On 27/10/15 11:33, Julien Grall wrote: > The current domain and the domain pointed by the variable "d" are not > the same. > > However, when it's not possible to get a reference on the page, the > target domain ID is not printed. This makes the message difficult to > understand. > > Improve the

Re: [Xen-devel] [PATCH v8 15/17] vmx: VT-d posted-interrupt core logic handling

On Tue, 2015-10-27 at 05:19 +, Wu, Feng wrote: > > -Original Message- > > From: Dario Faggioli [mailto:dario.faggi...@citrix.com] > > > This is something similar with patch v7 and before, doing vcpu block > during context switch, and seems during the discussion, you guys > prefer

[Xen-devel] [xen-unstable-smoke test] 63331: tolerable all pass - PUSHED

flight 63331 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/63331/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass test-armhf-armhf-xl 12

Re: [Xen-devel] [PATCH] 'dom' error handled, by raising ENOMEM if failure occurs. 'xs_fd' leak handled in success path.

On 27 October 2015 at 16:25, Dario Faggioli wrote: > On Wed, 2015-10-28 at 03:49 +0530, Lasya wrote: > > The description of the patch, that you previously put in a separate > email, should live here. > Oh, I had thought no cover letter was needed. Hence, I didn't put

Re: [Xen-devel] [PATCH v1] xen/serial: Return actual bytes stored in TX FIFO for OMAP

>>> On 27.10.15 at 11:54, wrote: > On 27/10/15 10:50, Jan Beulich wrote: > On 27.10.15 at 11:36, wrote: >>> --- a/xen/include/xen/8250-uart.h >>> +++ b/xen/include/xen/8250-uart.h >>> @@ -143,6 +143,15 @@ >>> /* Supplementary

Re: [Xen-devel] [PATCH v3 1/5] xl: convert main() exit codes to EXIT_[SUCCESS|FAILURE]

On Tue, Oct 27, 2015 at 03:20:48PM +0530, Harmandeep Kaur wrote: [...] > }; > > +/* > + *The xl process should always return either EXIT_SUCCESS or > + *EXIT_FAILURE. main_* functions, implementing the various xl > + *commands, can be treated as main() as if they are returning > + *a process

Re: [Xen-devel] [PATCH] 'dom' error handled, by raising ENOMEM if failure occurs. 'xs_fd' leak handled in success path.

On 27 October 2015 at 16:37, George Dunlap wrote: > On 27/10/15 11:04, Lasya Venneti wrote: > > On 27 October 2015 at 16:25, Dario Faggioli > > wrote: > > > >> On Wed, 2015-10-28 at 03:49 +0530, Lasya wrote: > >> > >> The description of the

Re: [Xen-devel] [PATCH v3 2/5] xl: improve return and exit codes of scheduling related functions

On Tue, 2015-10-27 at 15:20 +0530, Harmandeep Kaur wrote: > Turning scheduling related functions exit codes towards using the > EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary > numbers > or libxl return codes. > - for main_*: arbitrary -> EXIT_SUCCESS|EXIT_FAILURE. >

Re: [Xen-devel] [PATCH] libxl: No emulated disk driver for xvdX disk

On Mon, 26 Oct 2015, Boris Ostrovsky wrote: > On 10/16/2015 10:01 AM, Ian Jackson wrote: > > Anthony PERARD writes ("[PATCH] libxl: No emulated disk driver for xvdX > > disk"): > > > When a guest configuration list xvdX for its disks, there is no need to > > > provide an emulated driver for the

[Xen-devel] [PATCH] xen/mm: Unmap page for direct mapped domain on decrease reservation

Direct mapped domain needs to retrieve the exact same underlying physical page when the region is re-populated. Currently, when the memory reservation for this domain is decreased, the request is just ignored and the page stayed mapped in the P2M. However, this make more difficult to spot issue

Re: [Xen-devel] [PATCH V8 7/7] domcreate: support pvusb in configuration file

On 10/21/2015 11:08 AM, Chunyan Liu wrote: Add code to support pvusb in domain config file. One could specify usbctrl and usb in domain's configuration file and create domain, then usb controllers will be created and usb device would be attached to guest automatically. One could specify usb

Re: [Xen-devel] [PATCH v3 5/5] xl: improve return and exit codes of parse related functions

On Tue, 2015-10-27 at 15:20 +0530, Harmandeep Kaur wrote: > Turning parsing related functions exit codes towards using the > EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary > numbers > or libxl return codes. > - for main_*: arbitrary -> EXIT_SUCCESS|EXIT_FAILURE. > -

Re: [Xen-devel] [RFC v2] xSplice design

On 06/12/2015 12:39 PM, Martin Pohlack wrote: On 15.05.2015 21:44, Konrad Rzeszutek Wilk wrote: [...] ## Hypercalls We will employ the sub operations of the system management hypercall (sysctl). There are to be four sub-operations: * upload the payloads. * listing of payloads summary

Re: [Xen-devel] [PATCHv1 2/2] passthrough: improve locking when iterating over interrupts bound to VMs

>>> On 23.10.15 at 13:05, wrote: > radix_tree_gang_lookup() only requires a RCU read lock, not the > per-domain event_lock. ... when not caring about a consistent snapshot. > @@ -678,9 +684,7 @@ void hvm_dpci_msi_eoi(struct domain *d, int vector) > if (

Re: [Xen-devel] [PATCH V8 1/7] libxl: export some functions for pvusb use

On 10/21/2015 11:08 AM, Chunyan Liu wrote: Signed-off-by: Chunyan Liu Signed-off-by: Simon Cao Reviewed-by: Wei Liu --- tools/libxl/libxl.c | 4 ++-- tools/libxl/libxl_internal.h | 3 +++ 2 files changed, 5 insertions(+),

Re: [Xen-devel] [PATCH v3 1/5] xl: convert main() exit codes to EXIT_[SUCCESS|FAILURE]

On Tue, 2015-10-27 at 11:11 +, Wei Liu wrote: > On Tue, Oct 27, 2015 at 03:20:48PM +0530, Harmandeep Kaur wrote: > [...] > > }; > > > > +/* > > + *The xl process should always return either EXIT_SUCCESS or > > + *EXIT_FAILURE. main_* functions, implementing the various xl > > + *commands,

Re: [Xen-devel] [PATCH v1] xen/serial: Return actual bytes stored in TX FIFO for OMAP

On 27/10/15 11:05, Jan Beulich wrote: On 27.10.15 at 11:54, wrote: >> On 27/10/15 10:50, Jan Beulich wrote: >> On 27.10.15 at 11:36, wrote: --- a/xen/include/xen/8250-uart.h +++ b/xen/include/xen/8250-uart.h

Re: [Xen-devel] [PATCH v3 3/5] xl: improve return and exit codes of vcpu related functions

On Tue, 2015-10-27 at 15:20 +0530, Harmandeep Kaur wrote: > Turning vcpu manipulation functions exit codes toward using the > EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary > numbers > or libxl return codes. > > Signed-off-by: Harmandeep Kaur >

[Xen-devel] [distros-debian-snapshot test] 38215: regressions - FAIL

flight 38215 distros-debian-snapshot real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/38215/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-i386-current-netinst-pygrub 9 debian-di-install fail REGR. vs.

Re: [Xen-devel] [PATCH v3 4/5] xl: improve return and exit codes of cpupool related functions

On Tue, 2015-10-27 at 15:20 +0530, Harmandeep Kaur wrote: > Turning cpupools related functions exit codes towards using the > EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary > numbers > or libxl return codes. > > Signed-off-by: Harmandeep Kaur >

Re: [Xen-devel] [PATCH V8 5/7] xl: add pvusb commands

On 10/21/2015 11:08 AM, Chunyan Liu wrote: Add pvusb commands: usbctrl-attach, usbctrl-detach, usb-list, usb-attach and usb-detach. To attach a usb device to guest through pvusb, one could follow following example: #xl usbctrl-attach test_vm version=1 ports=8 #xl usb-list test_vm will

Re: [Xen-devel] [PATCH V8 6/7] xl: add usb-assignable-list command

On 10/21/2015 11:08 AM, Chunyan Liu wrote: Add xl usb-assignable-list command to list assignable USB devices. Assignable USB device means the USB device type is assignable and it's not assigned to any guest yet. Signed-off-by: Chunyan Liu Acked-by: Juergen Gross

[Xen-devel] [PATCH v3] dom variable error handled in Xenstore

xc_dom_allocate function in build function in init-xenstore-domain.c returns NULL on failure. In that case, variable rv is set to ENOMEM and directed to failure path err. Signed-off-by: Lasya Venneti --- tools/xenstore/init-xenstore-domain.c | 4 1 file

[Xen-devel] [PATCH v3] Leaking of xs_fd fixed in Xenstore

The success path isn't closed xs_fd in build function in init-xenstore-domain.c . Added that line before return 0. Signed-off-by: Lasya Venneti --- tools/xenstore/init-xenstore-domain.c | 1 + 1 file changed, 1 insertion(+) diff --git

[Xen-devel] [linux-3.10 test] 63318: regressions - trouble: broken/fail/pass

flight 63318 linux-3.10 real [real] http://logs.test-lab.xenproject.org/osstest/logs/63318/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvops 5 kernel-build fail REGR. vs. 62642 Tests which are

Re: [Xen-devel] [PATCH V8 4/7] libxl: add libxl_device_usb_assignable_list API

On 10/21/2015 11:08 AM, Chunyan Liu wrote: Add API for listing assignable USB devices info. Assignable USB device means the USB device type is assignable and it's not assigned to any guest yet. Signed-off-by: Chunyan Liu Acked-by: Juergen Gross Juergen

Re: [Xen-devel] [PATCH v1] xen/serial: Return actual bytes stored in TX FIFO for OMAP

Hi, all. Although OMAP and 8250 compatible UARTs have a lot of common, they differs at least in configuration steps since OMAP UART has such thing as "register access mode", also OMAP UART has additional features and as a result a subset of additional registers. On Tue, Oct 27, 2015 at 1:15 PM,

Re: [Xen-devel] [PATCH] xen/mm: Improve message in populate physmap when the domain is direct mapped

Hi Andrew, On 27/10/15 11:45, Andrew Cooper wrote: > On 27/10/15 11:33, Julien Grall wrote: >> The current domain and the domain pointed by the variable "d" are not >> the same. >> >> However, when it's not possible to get a reference on the page, the >> target domain ID is not printed. This

Re: [Xen-devel] [PATCHv1 1/2] passthrough: use per-interrupt lock when injecting an interrupt

>>> On 23.10.15 at 13:05, wrote: > The use of the per-domain event_lock in hvm_dirq_assist() does not scale > with many VCPUs or interrupts. > > Add a per-interrupt lock to reduce contention. When a interrupt for a > passthrough device is being setup or teared down, we

Re: [Xen-devel] OSSTest nested patch PART2 -- L2 installation failure

Hu, Robert writes ("OSSTest nested patch PART2 -- L2 installation failure"): > Now I get to L2 installation. > ... > L1 as host seems not having ether-prefix base defined. ... > L1 as host seems not have dhcp watch method defined I suggest replacing the calls to get_host_property with

Re: [Xen-devel] [Minios-devel] [PATCH MINI-OS v2] xenbus: notify the other end when necessary

On Tue, Oct 27, 2015 at 11:54:01AM +0100, Samuel Thibault wrote: > Wei Liu, le Tue 27 Oct 2015 10:32:18 +, a écrit : > > I haven't checked if cxenstored behaves the same, though. > > It doesn't: it checks for room in rings before sleeping. > Thanks for checking! And I confirm with my test

Re: [Xen-devel] [PATCH] xen/mm: Improve message in populate physmap when the domain is direct mapped

On 27/10/15 11:49, Julien Grall wrote: > Hi Andrew, > > On 27/10/15 11:45, Andrew Cooper wrote: >> On 27/10/15 11:33, Julien Grall wrote: >>> The current domain and the domain pointed by the variable "d" are not >>> the same. >>> >>> However, when it's not possible to get a reference on the page,

[Xen-devel] [PATCHv1] x86/xen: add reschedule point when mapping foreign GFNs

Mapping a large range of foreign GFNs can take a long time, add a reschedule point after each batch of 16 GFNs. Signed-off-by: David Vrabel --- arch/x86/xen/mmu.c | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/x86/xen/mmu.c b/arch/x86/xen/mmu.c index

Re: [Xen-devel] [PATCH v8 15/17] vmx: VT-d posted-interrupt core logic handling

Oh, one more thing. On Mon, 2015-10-12 at 16:55 +0800, Feng Wu wrote: > diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c > index e448b31..cad70b4 100644 > --- a/xen/arch/x86/hvm/vmx/vmx.c > +++ b/xen/arch/x86/hvm/vmx/vmx.c > +void vmx_vcpu_block_cancel(struct vcpu *v) > +{

Re: [Xen-devel] [PATCH] x86/mm: don't call HVM-only function for PV guests

On 27/10/15 15:23, Jan Beulich wrote: > Somehow I managed to drop the HVM dependency from v2 to v3 of what > became commit 5c23c760a8 ("x86/HVM: correct page dirty marking in > hvm_map_guest_frame_rw()"), obviously breaking migration of PV guests. > > Signed-off-by: Jan Beulich

Re: [Xen-devel] [Minios-devel] [PATCH MINI-OS v2] xenbus: notify the other end when necessary

Samuel Thibault, le Mon 26 Oct 2015 18:11:04 +0100, a écrit : > diff --git a/tools/ocaml/libs/xb/xb.ml b/tools/ocaml/libs/xb/xb.ml > index 50944b5..33298d2 100644 > --- a/tools/ocaml/libs/xb/xb.ml > +++ b/tools/ocaml/libs/xb/xb.ml > @@ -91,10 +91,12 @@ let write_fd back con s len = >

[Xen-devel] [PATCH v5 1/5] xl: convert main() exit codes to EXIT_[SUCCESS|FAILURE]

Turning main() function exit codes towards using the EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary numbers or libxl return codes. Also includes a document comment in xl.h stating xl process should always return EXIT_FOO and main_* can be treated as main() as if they are

[Xen-devel] [PATCH v5 5/5] xl: improve return and exit codes of parse related functions

Turning parsing related functions exit codes towards using the EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary numbers or libxl return codes. - for main_*: arbitrary -> EXIT_SUCCESS|EXIT_FAILURE. - for internal fucntion: arbitrary -> 0/1. Don't touch

[Xen-devel] [PATCH v5 3/5] xl: improve return and exit codes of vcpu related functions

Turning vcpu manipulation functions exit codes toward using the EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary numbers or libxl return codes. Signed-off-by: Harmandeep Kaur Reviewed-by: Dario Faggioli Acked-by: Wei Liu

Re: [Xen-devel] [PATCH 3/6] xen/common: grant_table: Avoid to shadow "frame" in __gnttab_map_grant_ref

>>> On 27.10.15 at 16:39, wrote: > The variable "frame" is declared twice within the function > __gntab_map_grant_ref. This makes the code quite confusing to read. > > The second definition is not useful as the first one is never used > until then. So drop it. That's

Re: [Xen-devel] [PATCH 4/6] xen/common: memory: Avoid to shadow the variable "d" in do_memory_op

>>> On 27.10.15 at 16:39, wrote: > The variable "d" is declared multiple times within do_memory_op. > > The subsequent declaration are not useful because the top one is never > used. So drop them. The patch is correct, but the description is slightly off: The top one is

[Xen-devel] What is the correct way to enable the Base repositories on XenServer Dundee?

Im trying to enable the yum repos on XenServer Dundee so I can install a few packages (git, make, dev stuff etc) and do some experimental development. I have enabled the base repository as such CentOS-7.0.1406.el7.centos.2.5 Base enabled: 0 CentOS-7 - Debuginfo

[Xen-devel] Oxenstored short-write issue

Hi Dave We discovered an issue in oxenstored: when it writes to the ring, it writes a chunk of contiguous data. When it tries to write across ring boundary, it returns a short-write. That leads to stalling mini-os's xenbus ring. Samuel provided a diff which solves the issue:

[Xen-devel] [PATCH v5 2/5] xl: improve return and exit codes of scheduling related functions

Turning scheduling related functions exit codes towards using the EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary numbers or libxl return codes. - for main_*: arbitrary -> EXIT_SUCCESS|EXIT_FAILURE. - for internal fucntion: arbitrary -> 0/1. Signed-off-by:

[Xen-devel] [PATCH v5 4/5] xl: improve return and exit codes of cpupool related functions

Turning cpupools related functions exit codes towards using the EXIT_[SUCCESS|FAILURE] constants, instead of instead of arbitrary numbers or libxl return codes. Signed-off-by: Harmandeep Kaur Reviewed-by: Dario Faggioli Acked-by: Wei Liu

  1   2   3   >