From: Pramod Devendra
Signed-off-by: Pramod Devendra
CC: Ian Jackson
CC: Stefano Stabellini
CC: Ian Campbell
CC: Wei Liu
---
Changed since v1:
1. Make sure sun_path does not overflow.
2. Close qmp_fd on error.
---
tools/libxl/libxl_qmp.c | 26 --
1 file changed, 20
Signed-off-by: Koushik Chakravarty
CC: Ian Jackson
CC: Stefano Stabellini
CC: Ian Campbell
CC: Wei Liu
---
tools/libxl/libxl_dm.c |8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c
index cb006df..2678be2 100644
--- a/t
Hi, all:
I am trying to use a HVM with PCI pass-through NIC as network driver domain.
However, when I send packets whose size are larger than 128 bytes from DomU
using pkt-gen tools, after several seconds, the network between driver domain
and destination host will be blocked.
The networking
Thanks for the comments!
> -Original Message-
> From: Konrad Rzeszutek Wilk [mailto:konrad.w...@oracle.com]
> Sent: Thursday, March 19, 2015 12:10 AM
> To: Wu, Feng
> Cc: xen-devel@lists.xen.org; Zhang, Yang Z; Tian, Kevin; Keir Fraser
> (k...@xen.org); Jan Beulich (jbeul...@suse.com)
> Su
For test, please ignore.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
On 03/16/2015 09:16 AM, Peter Zijlstra wrote:
Implement the paravirt qspinlock for x86-kvm.
We use the regular paravirt call patching to switch between:
native_queue_spin_lock_slowpath()__pv_queue_spin_lock_slowpath()
native_queue_spin_unlock() __pv_queue_spin_unlock()
We u
Konrad Rzeszutek Wilk wrote on 2015-03-19:
> On Wed, Mar 18, 2015 at 12:44:21PM +, Wu, Feng wrote:
>> VT-d Posted-interrupt (PI) design for XEN
>>
>> Background
>> ==
>> With the development of virtualization, there are more and more
>> device assignment requirements. However, today wh
flight 36518 qemu-upstream-4.3-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/36518/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-libvirt 9 guest-start fail never pass
test-amd64-amd64-xl-qemuu
This duplicates the code from above. I think this would be best done as:
static int libxl__detect_gfx_passthru_kind(libxl__gc *gc, guest_config)
{
if (b_info->u.hvm.gfx_passthru_kind != LIBXL_GFX_PASSTHRU_KIND_DEFAULT)
return 0;
if (libxl__is_igd_vga_passthru(gc, guest_config)
> -Original Message-
> From: Stefan Berger [mailto:stef...@linux.vnet.ibm.com]
> Sent: Thursday, March 19, 2015 3:17 AM
> To: Xu, Quan; stefano.stabell...@eu.citrix.com; qemu-de...@nongnu.org;
> arm...@redhat.com; lcapitul...@redhat.com; aligu...@amazon.com;
> pbonz...@redhat.com; ebl...@
Hi,
I've hit some deadlock in kernel xenstore client exposed via
/proc/xen/xenbus. Steps to reproduce are simple:
int main() {
struct xs_handle *xs;
xs = xs_open(0);
xs_watch(xs, "domid", "token");
xs_read(xs, 0, "name", NULL);
return 0;
}
xs_watch internal
On Wed, Mar 18, 2015 at 09:33:58PM +, Wei Liu wrote:
> There is already a typedef in libxlutil.h. Remove the one in
> libxlu_internal.h.
>
> Signed-off-by: Wei Liu
Missing the 'Reported-by: Konrad Rzeszutek Wilk '
> ---
> tools/libxl/libxlu_internal.h | 4 ++--
> 1 file changed, 2 insertion
Instead of just the return value.
Signed-off-by: Konrad Rzeszutek Wilk
Acked-by Ian Campbell
---
tools/libxc/xc_dom_x86.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/tools/libxc/xc_dom_x86.c b/tools/libxc/xc_dom_x86.c
index af0c9f4..3301f53 100644
--- a/tools/libx
The goto looks very wrong when the rest of the code
has spaces.
Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Ian Campbell
---
tools/libxc/xc_cpupool.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/libxc/xc_cpupool.c b/tools/libxc/xc_cpupool.c
index 6393cfb..828
Oddly enough the user of this API did the right thing -
check for return being negative and used 'errno' for the
real error.
Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Ian Campbell
---
tools/libxc/xc_pm.c | 54 +++--
1 file changed, 36 inserti
We don't need to put fill errno because xc_hypercall_buffer_alloc
fills the errno with the appropriate errno values and we just
need to pass them up the stack.
Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Ian Campbell
---
tools/libxc/xc_domain.c | 2 +-
1 file changed, 1 insertion(+), 1 delet
Instead of assuming everything is always OK. We stash
the gpfns value as an parameter.
Signed-off-by: Konrad Rzeszutek Wilk
---
tools/libxc/xc_core_arm.c| 17 ++---
tools/libxc/xc_core_x86.c| 24
tools/libxc/xc_domain_save.c | 8 +++-
3 files cha
Hey
Please see the following patches which fix an subset of
some of the various usages of return -Exx instead of
using -1 (and stashing in errno the error value).
We also clean up some cases where the errno is over-writen
- we want to bubble up the errnor that the underlaying
hypercall had done.
After we have done the hypercall - the errno has the failure
code. However our usage of pthread and munmap can trigger them
to manipulate the errno with their failure values. That would
be bad as what we care about is just the hypercall error value.
Another solution to this would be to save the 'e
The API returns now negative values on error and stashes
the error in errno. Fix the user of this API.
The 'xc_hypercall_bounce_pre' can fail - and if so it will
stash its errno values - no need to over-write it.
Signed-off-by: Konrad Rzeszutek Wilk
---
tools/libxc/xc_tmem.c |
instead of the -Exx values (which should go in errno).
This patch has HUGE implications. There is a lot of APIs
that are using do_memory_op. Fortunately most of them
check for 'if (do_memory_op(..) < 0)' so will function
properly. However there were some which printed the return
value to the user.
We should be using the errno that the hypercall left
instead of overwriting it with the return value.
Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Ian Campbell
---
tools/libxl/libxl_x86.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/tools/libxl/libxl_x86.c b/to
Instead of returning -Exx we now return -1 for error.
We could stash the -Exx values in errno values but why - the
underlaying functions we call all stash the proper errno
value. Hence we just propagate it up wherver it is needed.
Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Ian Campbell
---
If there is a negative return value - check for that and
also use errno for the proper error value.
Signed-off-by: Konrad Rzeszutek Wilk
---
tools/libxl/libxl.c | 4 ++--
tools/tests/mem-sharing/memshrtool.c | 12 ++--
2 files changed, 12 insertions(+), 4 deletions(-)
Instead of assuming everything is always OK. As such
we return now the return value (or zero for success).
The max_mfn is now passed in as the parameter.
Signed-off-by: Konrad Rzeszutek Wilk
---
tools/libxc/include/xenctrl.h | 2 +-
tools/libxc/xc_offline_page.c | 6 +++---
tools/libxc/xc_priv
The users of these (qemu) check for a negative value
so we are safe in regards to that. However they
also use the return value to inform the user of the
error.
Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Ian Campbell
---
tools/libxc/xc_physdev.c | 12
1 file changed, 8 insertion
Hello,
Wei Liu, le Tue 17 Mar 2015 14:29:07 +, a écrit :
> One of my lessons learned from the existing stubdom stuffs is that I
> should work with upstream and produce maintainable code.
Not only maintainable, but really make sure to have the time to stick
with upstream on the long run, first
flight 36516 xen-4.4-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/36516/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-pair17 guest-migrate/src_host/dst_host fail like 35919
Tests which did not succee
flight 36511 xen-4.5-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/36511/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-pvh-intel 9 guest-start fail never pass
test-amd64-amd64-rumpuserxen-amd64
flight 36517 qemu-upstream-4.5-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/36517/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-pvh-intel 9 guest-start fail never pass
test-armhf-armhf-libvirt
On 18/03/15 21:21, Anil Madhavapeddy wrote:
This is not an argument for or against; if you want to expose AF_WHATEVER to
applications running on a rump kernel, you need to sell AF_WHATEVER to NetBSD,
not to rumpkernel-users. Well, preferably you need to sell it to everyone
implementing socket
There is already a typedef in libxlutil.h. Remove the one in
libxlu_internal.h.
Signed-off-by: Wei Liu
---
tools/libxl/libxlu_internal.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/libxl/libxlu_internal.h b/tools/libxl/libxlu_internal.h
index 3451cfe..0acdde3 10
On Wed, Mar 18, 2015 at 04:18:32PM -0400, Konrad Rzeszutek Wilk wrote:
> Hey
>
> The git commit 1a09c5113a38dcf1fb6582d77285d727defeea6c
> "libxlu: rework internal representation of setting" breaks build:
>
> ~/xtt-x86_64/xen/tools/libxl> make
> rm -f _paths.h.tmp; echo "#define SBINDIR \"/usr/s
On 18 Mar 2015, at 20:23, Antti Kantee wrote:
>
> On 18/03/15 19:05, Anil Madhavapeddy wrote:
>>> This fits in with a couple of things I hope to make time to work on in the
>>> next couple of months:
>>>
>>> 1. Introspection of Rump Kernel domUs for ops purposes, i.e. get some
>>>basic "ps",
On 03/16/2015 09:16 AM, Peter Zijlstra wrote:
Implement simple paravirt support for the qspinlock.
Provide a separate (second) version of the spin_lock_slowpath for
paravirt along with a special unlock path.
The second slowpath is generated by adding a few pv hooks to the
normal slowpath, but w
On 03/16/2015 09:16 AM, Peter Zijlstra wrote:
Hi Waiman,
As promised; here is the paravirt stuff I did during the trip to BOS last week.
All the !paravirt patches are more or less the same as before (the only real
change is the copyright lines in the first patch).
The paravirt stuff is 'simple
On 18/03/15 19:05, Anil Madhavapeddy wrote:
This fits in with a couple of things I hope to make time to work on in the
next couple of months:
1. Introspection of Rump Kernel domUs for ops purposes, i.e. get some
basic "ps", "top", "vmstat"-like information about what the domU is
doing fr
Hey
The git commit 1a09c5113a38dcf1fb6582d77285d727defeea6c
"libxlu: rework internal representation of setting" breaks build:
~/xtt-x86_64/xen/tools/libxl> make
rm -f _paths.h.tmp; echo "#define SBINDIR \"/usr/sbin\"" >>_paths.h.tmp; echo
"#define BINDIR \"/usr/bin\"" >>_paths.h.tmp; echo "#d
On 03/10/2015 08:14 AM, Quan Xu wrote:
This Patch provides the glue for the TPM_TIS(Qemu frontend) to Xen
stubdom vTPM domain that provides the actual TPM functionality. It
sends data and TPM commends with xen_vtpm_frontend. It is similar as
another two vTPM backens:
*vTPM passthrough backen S
a...@recoil.org said:
> > Point 2. will further require implementing support in the Rump Kernel,
> > either for a shim which would proxy AF_UNIX / AF_INET transparently using
> > vchan, or possibly later implementing a separate socket family (AF_VCHAN /
> > AF_HYPER?). Once that is done you should
On 18 Mar 2015, at 11:20, Martin Lucina wrote:
>>
>> A bit background information. A stubdom is a service domain. With QEMU
>> stubdom we are able to run QEMU device emulation code in a separate
>> domain so that bugs in QEMU don't affect Dom0 (the controlling domain).
>> Xen currently has a QEM
Hello
Today I'm working on virtual machines working set size tracking in xen
hypervisor.
I follow the vmware approch I read in this article:
https://www.google.fr/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&sqi=2&ved=0CCEQFjAA&url=https%3A%2F%2Fwww.usenix.org%2Fevents%2Fosdi02%2Ftech%2Fwaldspurger
On 03/10/2015 08:14 AM, Quan Xu wrote:
This drvier transfers any request/repond between TPM xenstubdoms
driver and Xen vTPM stubdom, and facilitates communications between
Xen vTPM stubdom domain and vTPM xenstubdoms driver. It is a glue for
the TPM xenstubdoms driver and Xen stubdom vTPM domain
> the source codes I read maddr, paddr, pfn and mdfn.
> please can someone explain me the differences between these concepts in
> xen hypervisor.
I think Tim did a very good job here:
http://www.slideshare.net/xen_com_mgr/xen-memory-management
HTH,
Razvan
__
On Wed, Mar 18, 2015 at 04:43:07PM +, Ian Campbell wrote:
> On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> > Hey,
> >
> > Please see the following set of patches which fix the various
> > usage of return -Exx instead of return -1 for errors (and
> > stashing the error value
Hello guys.
I start to develop in xen hypervisor no so long. I work on memory. in
the source codes I read maddr, paddr, pfn and mdfn.
please can someone explain me the differences between these concepts in
xen hypervisor.
Thank you
___
Xen-devel mai
On Wed, Mar 18, 2015 at 04:36:40PM +, Ian Campbell wrote:
> On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> > If there is a negative return value - check for that and
> > also use errno for the proper error value.
>
> Was xc_sharing_freed_pages fixed earlier in the series (wh
Ian Campbell wrote:
> On Tue, 2015-03-17 at 17:34 +, Wei Liu wrote:
>
>> On Tue, Mar 17, 2015 at 09:30:58AM -0600, Jim Fehlig wrote:
>>
>>> From: Ian Jackson
>>>
>>> Unlock the userdata before we actually call xc_domain_destroy. This
>>> leaves open the possibility that other libxl ca
Ian Campbell wrote:
> On Tue, 2015-03-17 at 09:30 -0600, Jim Fehlig wrote:
>
>> From: Ian Jackson
>>
>> From: Ian Jackson
>>
>> When domain_death_xswatch_callback needed a further call to
>> xc_domain_getinfolist it would restart it with the last domain it
>> found rather than the first one it
On Wed, Mar 18, 2015 at 04:26:37PM +, Ian Campbell wrote:
> On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> > The API returns now negative values on error and stashes
> > the error in errno. Fix the user of this API.
> >
> > The 'xc_hypercall_bounce_pre' can fail - and if so
Hi, guys!
We continue bringing up System based on Xen hypervisor on Renesas Lager board.
We started 4 domains: Dom0 (Linux 3.14), Driver Domain (Linux 3.14),
Cluster Domain (Linux 3.14), and DomU (Tizen with 3.14 kernel).
Each domain has 2 VCPUs (4 physical CPUs are up).
Currently, we use Xen vers
On 03/18/2015 04:49 PM, Dario Faggioli wrote:
>> scheduler_init() is called before smp_prepare_cpus() in part because of
>> a dependency chain elsewhere: we cannot set up the idle domain until
>> scheduler_init() is called; and other places further on in the
>> initialization but before setting up
On Wed, Mar 18, 2015 at 04:43:40PM +, Jan Beulich wrote:
> >>> On 18.03.15 at 15:06, wrote:
> > On Wed, Mar 18, 2015 at 07:41:55AM +, Jan Beulich wrote:
> >> >>> On 17.03.15 at 18:44, wrote:
> >> > As you can see to preserve the existing functionality such as
> >> > being able to schedule
On Wed, 2015-03-18 at 12:45 +, Stefano Stabellini wrote:
> On Wed, 18 Mar 2015, Ian Campbell wrote:
> > On Wed, 2015-03-18 at 12:24 +0100, Martin Lucina wrote:
> > > ian.campb...@citrix.com said:
> > > > On Tue, 2015-03-17 at 15:27 +, Wei Liu wrote:
> > > > > This looks most interesting as
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> instead of the -Exx values (which should go in errno).
>
> This patch has HUGE implications.
For such a small patch!
> There is a lot of APIs
> that are using do_memory_op. Fortunatly most of them
"Fortunately".
> check for 'if
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> If there is a negative return value - check for that and
> also use errno for the proper error value.
Was xc_sharing_freed_pages fixed earlier in the series (which is
strictly speaking a bisection hazard, but nevermind) or was the e
On Wed, 2015-03-18 at 15:26 +, George Dunlap wrote:
> On 03/18/2015 08:53 AM, Dario Faggioli wrote:
> >>> @@ -1986,9 +1982,13 @@ static void init_pcpu(const struct scheduler *ops,
> >>> int cpu)
> >>> static void *
> >>> csched2_alloc_pdata(const struct scheduler *ops, int cpu)
> >>> {
> >>
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
$subject says libxl but means libxc.
Actually, now I notice it so do almost all of the patches! Once fixed
any acks I gave (or will give shortly) can still be applied.
> Instead of just the return value.
>
> Signed-off-by: Konrad R
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> Instead of assuming everything is always OK.
>
> Signed-off-by: Konrad Rzeszutek Wilk
> ---
> tools/libxc/xg_save_restore.h | 3 +++
> tools/misc/xen-mfndump.c | 2 +-
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
> di
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> Instead of assuming everything is always OK.
>
> Signed-off-by: Konrad Rzeszutek Wilk
> ---
> tools/libxc/xc_core_arm.c| 14 +++---
> tools/libxc/xc_core_x86.c| 21 +
> tools/libxc/xc_domain_sav
>>> On 18.03.15 at 15:06, wrote:
> On Wed, Mar 18, 2015 at 07:41:55AM +, Jan Beulich wrote:
>> >>> On 17.03.15 at 18:44, wrote:
>> > As you can see to preserve the existing functionality such as
>> > being able to schedule N amount of interrupt injections
>> > for the N interrupts we might ge
On Wed, Mar 18, 2015 at 05:21:08PM +0100, Imre Palik wrote:
> On 03/17/15 12:17, Wei Liu wrote:
> > On Fri, Mar 13, 2015 at 01:51:05PM +0100, Imre Palik wrote:
> >> From: "Palik, Imre"
> >>
> >> With the current netback, the bandwidth limiter's parameters are only
> >> settable during vif setup ti
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> Hey,
>
> Please see the following set of patches which fix the various
> usage of return -Exx instead of return -1 for errors (and
> stashing the error value in errno).
All of them, or just a subset of the callpaths?
If it's all o
On Tue, Mar 17, 2015 at 11:45 PM, Andrew Warkentin wrote:
> On 3/17/15, George Dunlap wrote:
>> Any deduplication code would run in as a process probably in domain 0,
>> and may be somewhat slow; but the actual mechanism of sharing is a
>> generic mechanism in the hypervisor which any client can
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> We should be using the errno that the hypercall left
> instead of overwritting it with the return value.
"overwriting"
> Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Ian Campbell
__
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> We don't need to put fill errno because xc_hypercall_buffer_alloc
> fills the errno with the appropiate errno values and we just
> need to pass them up the stack.
"appropriate"
> Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Ian
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> with proper value (ENOMEM) when reporting failures.
>
> Signed-off-by: Konrad Rzeszutek Wilk
> ---
> [v1: errno before using PERROR]
> ---
> tools/libxc/xc_core_arm.c | 1 +
> tools/libxc/xc_core_x86.c | 1 +
> 2 files changed, 2
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> After we have done the hypercall - the errno has the failure
> code. However our usage of pthread and munmap can trigger them
> to manipulate the errno with their failure values. That would
> be bad as what we care about is just the
On Wed, 2015-03-18 at 16:08 +, George Dunlap wrote:
> On 03/18/2015 03:59 PM, Jan Beulich wrote:
> On 18.03.15 at 16:26, wrote:
> >> In both cases there's a slight risk in using system_state to determine
> >> whether to rely on cpu_data[] or not, because there's actually a window
> >> for
On Wed, Mar 18, 2015 at 04:21:52PM +, Ian Campbell wrote:
> On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> > The users of these (qemu) check for a negative value
> > so we are safe in regards to that. However they
> > also use the return value to inform the user of the
> > er
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> The API returns now negative values on error and stashes
> the error in errno. Fix the user of this API.
>
> The 'xc_hypercall_bounce_pre' can fail - and if so it will
> stash its errno values - no need to over-write it.
>
> Signed
On Wed, 2015-03-11 at 11:51 -0600, Charles Arnold wrote:
> Now that Xen uses qdisks by default and qemu does not write out
> statistics to sysfs this patch queries the QMP for disk statistics.
>
> This patch depends on libyajl for parsing statistics returned from
> QMP. The runtime requires libyaj
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> Oddly enough the user of this API did the right thing -
> check for return being negative and used 'errno' for the
> real error.
>
> Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Ian Campbell
_
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> Instead of returning -Exx we now return -1 for error.
> We could stash the -Exx values in errno values but why - the
> underlaying functions we call all stash the proper errno
> value. Hence we just propagate it up wherver it is need
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> The users of these (qemu) check for a negative value
> so we are safe in regards to that. However they
> also use the return value to inform the user of the
> error.
IIRC I saw a qemu patch go past to fix the callers?
> Signed-off-
On 03/17/15 12:17, Wei Liu wrote:
> On Fri, Mar 13, 2015 at 01:51:05PM +0100, Imre Palik wrote:
>> From: "Palik, Imre"
>>
>> With the current netback, the bandwidth limiter's parameters are only
>> settable during vif setup time. This patch register a watch on them, and
>> thus makes them runtime
On Mon, 2015-03-16 at 11:39 -0400, Konrad Rzeszutek Wilk wrote:
> The goto looks very wrong when the rest of the code
> has spaces.
>
> Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Ian Campbell
___
Xen-devel mailing list
Xen-devel@lists.xen.org
On Wed, Mar 18, 2015 at 04:06:37PM +, Jan Beulich wrote:
> >>> On 18.03.15 at 14:58, wrote:
> > On Wed, Mar 18, 2015 at 07:38:12AM +, Jan Beulich wrote:
> >> >>> On 17.03.15 at 18:15, wrote:
> >> > The latest one (please see attached) would cause an dead-lock iff
> >> > on the CPU we are
On Wed, Mar 18, 2015 at 12:44:21PM +, Wu, Feng wrote:
> VT-d Posted-interrupt (PI) design for XEN
>
> Background
> ==
> With the development of virtualization, there are more and more device
> assignment requirements. However, today when a VM is running with
> assigned devices (such as
On 03/18/2015 03:59 PM, Jan Beulich wrote:
On 18.03.15 at 16:26, wrote:
>> In both cases there's a slight risk in using system_state to determine
>> whether to rely on cpu_data[] or not, because there's actually a window
>> for each processor after system_state == SYS_STATE_smp_boot where
>>
>>> On 18.03.15 at 14:58, wrote:
> On Wed, Mar 18, 2015 at 07:38:12AM +, Jan Beulich wrote:
>> >>> On 17.03.15 at 18:15, wrote:
>> > The latest one (please see attached) would cause an dead-lock iff
>> > on the CPU we are running the softirq and an do_IRQ comes for the
>> > exact dpci we are
>>> On 18.03.15 at 16:26, wrote:
> In both cases there's a slight risk in using system_state to determine
> whether to rely on cpu_data[] or not, because there's actually a window
> for each processor after system_state == SYS_STATE_smp_boot where
> cpu_data[] is *not* initialized, but it's not ob
On Fri, 2015-03-13 at 12:08 +0100, Dario Faggioli wrote:
> Dario Faggioli (7):
> xl: turn some int local variable into bool
> xl: add -c/--cpupool option to `xl list'
> libxl: introduce libxl_cpupool_cpu{add,remove}_cpumap()
> xl: enable using ranges of pCPUs when manipulati
Xen pv domains are using a domain private p2m list to convert guest pfns
to mfns. This p2m list has to be updated by the Xen tools during domain
restore and migration, as the mfns will most likely change. In order to
locate the p2m list the Xen tools need an interface provided by the
guest. Up to n
On 03/18/2015 08:53 AM, Dario Faggioli wrote:
>>> @@ -1986,9 +1982,13 @@ static void init_pcpu(const struct scheduler *ops,
>>> int cpu)
>>> static void *
>>> csched2_alloc_pdata(const struct scheduler *ops, int cpu)
>>> {
>>> -/* Check to see if the cpu is online yet */
>>> -/* Note: c
On Wed, Mar 18, 2015 at 01:59:58PM +, David Vrabel wrote:
> On 18/03/15 13:57, Juergen Gross wrote:
> > On 03/18/2015 11:36 AM, David Vrabel wrote:
> >> On 16/03/15 10:31, Juergen Gross wrote:
> >>> On 03/16/2015 11:03 AM, Daniel Kiper wrote:
> On Mon, Mar 16, 2015 at 06:35:04AM +0100, Jue
On Wed, Mar 18, 2015 at 01:12:50PM +, Lars Kurth wrote:
> Hi,
>
> I added all the people who raised their hands so far to the TO list. As far
> as I can tell we have people from the following timezones: GMT, GMT+1, MTZ,
> ETZ - if I got this wrong, please let me know your timezone. Depending
On Wed, Mar 18, 2015 at 02:09:09PM +, Dario Faggioli wrote:
> On Wed, 2015-03-18 at 13:08 +, Ian Campbell wrote:
> > On Wed, 2015-03-18 at 13:06 +, Ian Campbell wrote:
> > > On Fri, 2015-03-13 at 16:26 -0400, Konrad Rzeszutek Wilk wrote:
> > > > The function does not return any values a
Hi Ian,
On 24/02/2015 10:08, Ian Campbell wrote:
On Mon, 2015-02-23 at 22:02 +, Julien Grall wrote:
On 23/02/2015 14:36, Ian Campbell wrote:
On Thu, 2015-01-29 at 13:48 +, Julien Grall wrote:
On 29/01/15 12:28, Stefano Stabellini wrote:
On Thu, 29 Jan 2015, Julien Grall wrote:
On 2
On Wed, 2015-03-18 at 13:08 +, Ian Campbell wrote:
> On Wed, 2015-03-18 at 13:06 +, Ian Campbell wrote:
> > On Fri, 2015-03-13 at 16:26 -0400, Konrad Rzeszutek Wilk wrote:
> > > The function does not return any values at all. Convert the
> > > internal libxl ones (ERROR_FAIL, ..., etc) to p
On Wed, Mar 18, 2015 at 07:41:55AM +, Jan Beulich wrote:
> >>> On 17.03.15 at 18:44, wrote:
> > As you can see to preserve the existing functionality such as
> > being able to schedule N amount of interrupt injections
> > for the N interrupts we might get - I modified '->masked'
> > to be an a
On 18/03/15 13:57, Juergen Gross wrote:
> On 03/18/2015 11:36 AM, David Vrabel wrote:
>> On 16/03/15 10:31, Juergen Gross wrote:
>>> On 03/16/2015 11:03 AM, Daniel Kiper wrote:
On Mon, Mar 16, 2015 at 06:35:04AM +0100, Juergen Gross wrote:
> On 03/11/2015 04:40 PM, Boris Ostrovsky wrote:
>
On Wed, Mar 18, 2015 at 07:38:12AM +, Jan Beulich wrote:
> >>> On 17.03.15 at 18:15, wrote:
> > On Tue, Mar 17, 2015 at 04:06:14PM +, Jan Beulich wrote:
> >> >>> On 17.03.15 at 16:38, wrote:
> >> > --- a/xen/drivers/passthrough/io.c
> >> > +++ b/xen/drivers/passthrough/io.c
> >> > @@ -804
On 03/18/2015 11:36 AM, David Vrabel wrote:
On 16/03/15 10:31, Juergen Gross wrote:
On 03/16/2015 11:03 AM, Daniel Kiper wrote:
On Mon, Mar 16, 2015 at 06:35:04AM +0100, Juergen Gross wrote:
On 03/11/2015 04:40 PM, Boris Ostrovsky wrote:
On 03/11/2015 10:42 AM, David Vrabel wrote:
On 10/03/1
On Wed, Mar 18, 2015 at 01:06:18PM +, Ian Campbell wrote:
> On Fri, 2015-03-13 at 16:26 -0400, Konrad Rzeszutek Wilk wrote:
> > The function does not return any values at all. Convert the
> > internal libxl ones (ERROR_FAIL, ..., etc) to positive values
> > and for the other cases just return s
On Fri, 2015-03-13 at 10:34 +, Wei Liu wrote:
> Watch /local/domain/$dm_domid/device-model/$domid/state, wait until
> state turns "running" then unpause guest.
>
> LIBXL_STUBDOM_START_TIMEOUT is the timeout used wait for stubdom to be
> ready. My test on a very old machine (Core 2 6400) showed
On Fri, 2015-03-13 at 10:34 +, Wei Liu wrote:
> diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c
> index 3dedad4..4a38455 100644
> --- a/tools/libxl/libxl_dm.c
> +++ b/tools/libxl/libxl_dm.c
> @@ -998,7 +998,7 @@ void libxl__spawn_stub_dm(libxl__egc *egc,
> libxl__stub_dm_spawn_sta
On Fri, 2015-03-13 at 10:34 +, Wei Liu wrote:
> The function in question is libxl__spawn_local_dm. We should use
> LIBXL_TOOLSTACK_DOMID when constructing xenstore path.
>
> Currently LIBXL_TOOLSTACK_DOMID is 0, so this patch introduces no
> functional change.
As I mentioned on the previous p
On Fri, 2015-03-13 at 16:26 -0400, Konrad Rzeszutek Wilk wrote:
> The check is superflous. If the 'max_vcpus' (argument
> value) is greater than pCPU and --ignore-host has not
> been supplied we would print an warning and return
> and not call this code.
>
> If the --ignore-host parameter had bee
On Wed, 2015-03-18 at 13:21 +, Ian Campbell wrote:
> On Fri, 2015-03-13 at 10:34 +, Wei Liu wrote:
> > ... because it is the right place to clean up device model stuffs.
>
> ... and not devices_destroy_cb because it is the right ...
>
> (also "stuff").
>
> > And the path should use LIBXL
1 - 100 of 154 matches
Mail list logo
