This patch set adds nested HVM test case for osstest.
In this test case, a Xen hypervisor (L1) runs on top of another Xen hypervisor
(L0).
Upon L1 hypervisor, we will then create a nested guest (L2), and test if the
Linux guest can then be installed and run well.
About nested Xen virtualization,
From: "longtao.pang"
1. Increase disk size to accomodate to nested test requirment.
2. Since 'Debain-xxx-.iso' image will be stored there, therefore needs more
disk capacity, increase root partition size in preseed generation.
3. In L1 installation context, assign more memory to it; since it
acts
From: "longtao.pang"
>From a hvm kernel build from Linux stable Kernel tree,
the auto generated grub2 menu will have 'submenu' primitive, upon the
'menuentry' items. Xen boot entries will be grouped into a submenu. This
patch adds capability to support such grub formats.
---
Osstest/Debian.pm |
From: "longtao.pang"
1. In this script, make some appropriate runvars which selecthost would
recognise.
2. Prepare the configurations for installing L2 guest VM.
3. Create a lv disk in L0 and hot-attach it to L1, need to restart L1 to make
the block disk to be recognized by L1 system, then using
From: "longtao.pang"
---
sg-run-job | 11 +++
1 file changed, 11 insertions(+)
diff --git a/sg-run-job b/sg-run-job
index 94d091b..ababebe 100755
--- a/sg-run-job
+++ b/sg-run-job
@@ -297,6 +297,17 @@ proc run-job/test-pair {} {
#run-ts . remus-failover ts-remus-check src
From: "longtao.pang"
This patch adds creation of the nested test job, when job creation procedure
is invoked.
'NESTED_OS_IMAGE' is the name of 'Debian ISO Images', which defined in
standalone.config.
---
make-flight | 20
1 file changed, 20 insertions(+)
diff --git a/mak
From: "longtao.pang"
1. Designate vif model to 'e1000', otherwise, with default device model,
the L1 eth0 interface disappear, hence xenbridge cannot work.
Maybe this limitation can be removed later after some fix it. For now, we
have to accomodate to it.
2. Since reboot L1 guest VM will take mor
Typedefs are duplicated in stubdom/vtpmmgr/tcg.h and supported compilers
do not cope with current staging branch.
Signed-off-by: Olaf Hering
Signed-off-by: Quan Xu
---
stubdom/vtpmmgr/common_types.h |9 +
stubdom/vtpmmgr/tcg.h |7 +--
stubdom/vtpmmgr/tpm2.c
On 03/04/2015 12:41 PM, Ian Campbell wrote:
On Wed, 2015-03-04 at 12:22 +0100, Juergen Gross wrote:
It would either be used like intended,
Which is how? That is what is really missing here.
So far this appears to be a bit which enables some as yet unspecified[0]
behaviour in one particular OS
On Friday 27 February 2015 10:20 PM, Ian Campbell wrote:
On Fri, 2015-02-27 at 16:35 +, Jan Beulich wrote:
On 27.02.15 at 16:24, wrote:
On Fri, 2015-02-27 at 14:54 +, Stefano Stabellini wrote:
MMCFG is a Linux config option, not to be confused with
PHYSDEVOP_pci_mmcfg_reserved that i
On Monday 09 March 2015 08:04 AM, Yijing Wang wrote:
Now we could pass PCI domain combined with bus number
in u32 argu. Because in arm/arm64, PCI domain number
is assigned by pci_bus_assign_domain_nr(). So we leave
pci_scan_root_bus() and pci_create_root_bus() in arm/arm64
unchanged. A new funct
On 17/03/15 00:10, Slutz, Donald Christopher wrote:
> On 03/16/15 17:19, Ian Murray wrote:
>> - Original Message -
>>> From: Paul Durrant
>>> To: Ian Murray ; "xen-de...@lists.xensource.com"
>>>
>>> Cc:
>>> Sent: Monday, 16 March 2015, 9:45
>>> Subject: Re: [Xen-devel] Compliling Xen 4.
On 3/16/15, Jan Beulich wrote:
> So where do you expect the major performance / scalability
> improvement to be gained? Internally to Xen, each page will need
> to be tracked separately anyway, as what appears physically
> contiguous in the granting guest may (and likely will) not be
> contiguous
On 03/16/15 17:19, Ian Murray wrote:
> - Original Message -
>> From: Paul Durrant
>> To: Ian Murray ; "xen-de...@lists.xensource.com"
>>
>> Cc:
>> Sent: Monday, 16 March 2015, 9:45
>> Subject: Re: [Xen-devel] Compliling Xen 4.5.0 Fails with error:
>> ‘bufioreq_pfn’ may be used uninitia
On 16/03/15 14:12, Konrad Rzeszutek Wilk wrote:
> On Sun, Mar 15, 2015 at 09:34:16PM +, Ian Murray wrote:
>> Hi,
>>
>> I have a domU guest that booted fine under Xen 4.4.1 with pvh=1 but now
>> fails to boot with it under Xen 4.5.0. Removing pvh=1, i.e. booting it as
>> traditional PV results
Hello
I want to know when there is context switch between processes in guest
the xen hypervisor can handle this switch.
Is there any possibility to get this context switch from hypervisor?
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://list
- Original Message -
> From: Paul Durrant
> To: Ian Murray ; "xen-de...@lists.xensource.com"
>
> Cc:
> Sent: Monday, 16 March 2015, 9:45
> Subject: Re: [Xen-devel] Compliling Xen 4.5.0 Fails with error:
> ‘bufioreq_pfn’ may be used uninitialised in this function
> [-Werror=uninit
Hi Dario,
2015-03-16 13:05 GMT-04:00 Dario Faggioli :
> In fact, printing the cpupool's CPU online mask
> for each vCPU is just redundant, as that is the
> same for all the vCPUs of all the domains in the
> same cpupool, while hard affinity is already part
> of the output of dumping domains info.
2015-03-16 13:04 GMT-04:00 Dario Faggioli :
> being serviced by the RTDS scheduler, as that is a
> legit situation to be in: think, for instance, of a
> newly created RTDS cpupool, with no domains migrated
> to it yet.
>
> Signed-off-by: Dario Faggioli
> Cc: George Dunlap
> Cc: Meng Xu
> Cc: Jan
2015-03-16 13:05 GMT-04:00 Dario Faggioli :
> and more consistent. In fact, before this changes, it looks
> like this:
>
> (XEN) VCPU information and callbacks for domain 0:
> (XEN) VCPU0: CPU4 [has=F] poll=0 upcall_pend = 00, upcall_mask = 00
> dirty_cpus={4} cpu_affinity={0-15}
> (XEN) cp
2015-03-16 13:05 GMT-04:00 Dario Faggioli :
> such as it is taken care of by the various schedulers, rather
> than happening in schedule.c. In fact, it is the schedulers
> that know better which locks are necessary for the specific
> dumping operations.
>
> While there, fix a few style issues (inde
branch xen-unstable
xen branch xen-unstable
job build-amd64-rumpuserxen
test rumpuserxen-build
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
Tree: rumpuserxen https://github.com/rumpkernel/rumprun-xen
Tree: rumpu
On 03/16/2015 05:05 PM, Dario Faggioli wrote:
> In fact, printing the cpupool's CPU online mask
> for each vCPU is just redundant, as that is the
> same for all the vCPUs of all the domains in the
> same cpupool, while hard affinity is already part
> of the output of dumping domains info.
>
> Inst
On 03/16/2015 05:05 PM, Dario Faggioli wrote:
> more specifically, for each runqueue, print what pCPUs
> belong to it, which ones are idle and which ones have
> been tickled.
>
> While there, also convert the whole file to use
> keyhandler_scratch for printing cpumask-s.
>
> Signed-off-b: Dario F
On 03/16/2015 05:05 PM, Dario Faggioli wrote:
> and more consistent. In fact, before this changes, it looks
> like this:
>
> (XEN) VCPU information and callbacks for domain 0:
> (XEN) VCPU0: CPU4 [has=F] poll=0 upcall_pend = 00, upcall_mask = 00
> dirty_cpus={4} cpu_affinity={0-15}
> (XEN)
On 03/16/2015 05:05 PM, Dario Faggioli wrote:
> e.g., with `xl debug-key r'. This change adds something
> like the following lines to the dump output:
>
> (XEN) Num online Cpus: 16, cpu_online_map: 0-15
> (XEN) Num free Cpus: 8, cpupool_free_cpus: 8-15
>
> Meaning there are 16 pCPUs online,
On 03/16/2015 05:05 PM, Dario Faggioli wrote:
> such as it is taken care of by the various schedulers, rather
> than happening in schedule.c. In fact, it is the schedulers
> that know better which locks are necessary for the specific
> dumping operations.
>
> While there, fix a few style issues (i
On 03/16/2015 06:05 PM, Dario Faggioli wrote:
e.g., with `xl debug-key r'. This change adds something
like the following lines to the dump output:
(XEN) Num online Cpus: 16, cpu_online_map: 0-15
(XEN) Num free Cpus: 8, cpupool_free_cpus: 8-15
Meaning there are 16 pCPUs online, and they a
From: "Paul E. McKenney"
This commit removes the open-coded CPU-offline notification with new
common code. Among other things, this change avoids calling scheduler
code using RCU from an offline CPU that RCU is ignoring. It also allows
Xen to notice at online time that the CPU did not go offlin
Hi Dario,
2015-03-16 13:10 GMT-04:00 Dario Faggioli :
> On Mon, 2015-03-16 at 18:04 +0100, Dario Faggioli wrote:
>> which is called by cpu_schedule_down(), and is necessary
>> for resetting the spinlock pointers in schedule_data from
>> the RTDS global runqueue lock, back to the default _lock
>> f
On 03/16/2015 05:04 PM, Dario Faggioli wrote:
> which is called by cpu_schedule_down(), and is necessary
> for resetting the spinlock pointers in schedule_data from
> the RTDS global runqueue lock, back to the default _lock
> fields in the struct.
>
> Not doing so causes Xen to explode, e.g., when
On 03/16/2015 05:04 PM, Dario Faggioli wrote:
> being serviced by the RTDS scheduler, as that is a
> legit situation to be in: think, for instance, of a
> newly created RTDS cpupool, with no domains migrated
> to it yet.
>
> Signed-off-by: Dario Faggioli
> Cc: George Dunlap
> Cc: Meng Xu
> Cc:
2015-03-16 13:04 GMT-04:00 Dario Faggioli :
> which is called by cpu_schedule_down(), and is necessary
> for resetting the spinlock pointers in schedule_data from
> the RTDS global runqueue lock, back to the default _lock
> fields in the struct.
>
> Not doing so causes Xen to explode, e.g., when re
On Tue, Mar 10, 2015 at 12:03:13PM +, Bob Ball wrote:
> For the last few weeks Anthony and I have been working on creating a CI
> environment to run against all OpenStack jobs. We're now in a position where
> we can share the current status, overview of how it works and next steps. We
> ac
> > If we do explicitly we run risk of dead-lock. See below of an draft
> > (not even compiled tested) of what I think you mean.
>
> That's no different from the code you proposed before, just that
> the live-lock is better hidden there: By re-raising a softirq from a
> softirq handler, you arrang
On Fri, Mar 13, 2015 at 10:34:34AM +, 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)
On 02/27/2015 04:51 PM, Dario Faggioli wrote:
> for events that are specific to Credit2 (as it happens
> for Credit1 already).
>
> Signed-off-by: Dario Faggioli
> Cc: George Dunlap
> Cc: Jan Beulich
> Cc: Keir Fraser
> Acked-by: Jan Beulich
> ---
> Changes from v1:
> * fixed the repeated typ
On 02/27/2015 04:51 PM, Dario Faggioli wrote:
> and update them from Credit2 and RTDS. In Credit2, while there,
> remove some stale comments too.
>
> Signed-off-by: Dario Faggioli
> Cc: George Dunlap
> Cc: Meng Xu
> Cc: Jan Beulich
> Cc: Keir Fraser
> Reviewed-by: Meng Xu
> Acked-by: Jan Beu
On 02/27/2015 04:51 PM, Dario Faggioli wrote:
> and update them from Credit2 and RTDS schedulers.
>
> Signed-off-by: Dario Faggioli
> Cc: Meng Xu
> Cc: George Dunlap
> Cc: Jan Beulich
> Cc: Keir Fraser
> Reviewed-by: Meng Xu
> Acked-by: Jan Beulich
Acked-by: George Dunlap
> ---
> Changes
>>> On 13.03.15 at 11:13, wrote:
> --- a/xen/arch/x86/domctl.c
> +++ b/xen/arch/x86/domctl.c
> @@ -1324,6 +1324,24 @@ long arch_do_domctl(
> }
> break;
>
> +case XEN_DOMCTL_psr_cat_op:
> +switch ( domctl->u.psr_cat_op.cmd )
> +{
> +case XEN_DOMCTL_PS
On Mon, 2015-03-16 at 18:04 +0100, Dario Faggioli wrote:
> which is called by cpu_schedule_down(), and is necessary
> for resetting the spinlock pointers in schedule_data from
> the RTDS global runqueue lock, back to the default _lock
> fields in the struct.
>
> Not doing so causes Xen to explode,
e.g., with `xl debug-key r'. This change adds something
like the following lines to the dump output:
(XEN) Num online Cpus: 16, cpu_online_map: 0-15
(XEN) Num free Cpus: 8, cpupool_free_cpus: 8-15
Meaning there are 16 pCPUs online, and they are pCPUs
0-15, and that 8 of them, more specifical
and more consistent. In fact, before this changes, it looks
like this:
(XEN) VCPU information and callbacks for domain 0:
(XEN) VCPU0: CPU4 [has=F] poll=0 upcall_pend = 00, upcall_mask = 00
dirty_cpus={4} cpu_affinity={0-15}
(XEN) cpu_soft_affinity={0-15}
(XEN) pause_count=0 pause_fla
In fact, printing the cpupool's CPU online mask
for each vCPU is just redundant, as that is the
same for all the vCPUs of all the domains in the
same cpupool, while hard affinity is already part
of the output of dumping domains info.
Instead, print the intersection between hard
affinity and online
more specifically, for each runqueue, print what pCPUs
belong to it, which ones are idle and which ones have
been tickled.
While there, also convert the whole file to use
keyhandler_scratch for printing cpumask-s.
Signed-off-b: Dario Faggioli
Cc: George Dunlap
Cc: Jan Beulich
Cc: Keir Fraser
such as it is taken care of by the various schedulers, rather
than happening in schedule.c. In fact, it is the schedulers
that know better which locks are necessary for the specific
dumping operations.
While there, fix a few style issues (indentation, trailing
whitespace, parentheses and blank lin
which is called by cpu_schedule_down(), and is necessary
for resetting the spinlock pointers in schedule_data from
the RTDS global runqueue lock, back to the default _lock
fields in the struct.
Not doing so causes Xen to explode, e.g., when removing
pCPUs from an RTDS cpupool and assigning them to
being serviced by the RTDS scheduler, as that is a
legit situation to be in: think, for instance, of a
newly created RTDS cpupool, with no domains migrated
to it yet.
Signed-off-by: Dario Faggioli
Cc: George Dunlap
Cc: Meng Xu
Cc: Jan Beulich
Cc: Keir Fraser
---
xen/common/sched_rt.c | 10
Hi,
Some pseudo-random bits for improving dumping (via debug keys) scheduling
related information.
In some more details, the series:
- fixes two bugs in the RTDS scheduler (patches 1 and 2),
- improve how the whole process of dumping scheduling info is serialized,
by moving all locking code
On 02/27/2015 04:50 PM, Dario Faggioli wrote:
> more specifically, about vCPU initialization and destruction events,
> in line with adb26c09f26e ("xen: sched: introduce a couple of counters
> in credit2 and SEDF").
>
> Signed-off-by: Dario Faggioli
> Cc: George Dunlap
> Cc: Meng Xu
> Cc: Jan Be
On 16/03/15 16:46, Ian Campbell wrote:
> On Mon, 2015-03-16 at 16:38 +, Julien Grall wrote:
>> On 16/03/15 16:22, Ian Campbell wrote:
> +if ( dt_device_type_is_equal(dev, "pci") )
> +return map_pci_device_ranges(d, dev, ranges, len);
> +
> +printk("Cannot handle
On Mon, 2015-03-16 at 16:38 +, Julien Grall wrote:
> On 16/03/15 16:22, Ian Campbell wrote:
> >>> +if ( dt_device_type_is_equal(dev, "pci") )
> >>> +return map_pci_device_ranges(d, dev, ranges, len);
> >>> +
> >>> +printk("Cannot handle ranges for non-PCI device %s type %s\n",
>
>>> On 13.03.15 at 11:13, wrote:
> @@ -1473,11 +1471,10 @@ static void __context_switch(void)
> }
> vcpu_restore_fpu_eager(n);
> n->arch.ctxt_switch_to(n);
> -
> -if ( psr_cmt_enabled() && n->domain->arch.psr_rmid > 0 )
> -psr_assoc_rmid(n->domain->ar
On Monday 16 March 2015 18:18:22 Razvan Cojocaru wrote:
> On 03/16/2015 06:00 PM, Lars Kurth wrote:
> >
> >> On 16 Mar 2015, at 13:01, Mihai Donțu wrote:
> >>
> >> On Thu, 12 Mar 2015 10:21:56 + wei.l...@citrix.com wrote:
> >>> We are now two months into 4.6 development window. This is an ema
On 16/03/15 16:22, Ian Campbell wrote:
>>> +if ( dt_device_type_is_equal(dev, "pci") )
>>> +return map_pci_device_ranges(d, dev, ranges, len);
>>> +
>>> +printk("Cannot handle ranges for non-PCI device %s type %s\n",
>>> + dt_node_name(dev), dev->type);
>>> +
>>
>> Is the
On Mon, 2015-03-16 at 16:14 +, Julien Grall wrote:
> Hi Ian,
>
> On 12/03/15 17:17, Ian Campbell wrote:
> > These properties are defined in ePAPR (2.3.8 and 2.4.3.1 respectively)
> > and the OpenFirmware PCI Bus Binding Specification (IEEE Std 1275-1994).
> >
> > This replaces the xgene speci
On 16/03/15 16:03, Vijay Kilari wrote:
Those 2 functions seems useful for me. Why did you drop them?
>>>
>>> These are callbacks registered for msi_chip in linux, Since we have removed
>>> msi_chip from its_node structure, these functions are supposed to be
>>> removed.
>>
>> How do you regis
On 03/16/2015 06:00 PM, Lars Kurth wrote:
>
>> On 16 Mar 2015, at 13:01, Mihai Donțu wrote:
>>
>> On Thu, 12 Mar 2015 10:21:56 + wei.l...@citrix.com wrote:
>>> We are now two months into 4.6 development window. This is an email to keep
>>> track of all the patch series I gathered. It is by no
Hi Ian,
On 12/03/15 17:17, Ian Campbell wrote:
> These properties are defined in ePAPR (2.3.8 and 2.4.3.1 respectively)
> and the OpenFirmware PCI Bus Binding Specification (IEEE Std 1275-1994).
>
> This replaces the xgene specific mapping. Tested on Mustang and on a
> model with a PCI virtio con
On Mon, Mar 16, 2015 at 7:50 PM, Julien Grall wrote:
> On 16/03/15 14:06, Vijay Kilari wrote:
@@ -343,17 +357,23 @@ static int its_queue_full(struct its_node *its)
static struct its_cmd_block *its_allocate_entry(struct its_node *its)
{
struct its_cmd_block *cmd;
Hi Ian,
On 12/03/15 17:17, Ian Campbell wrote:
> This is similar to 816f5bb1f074 "xen: arm: propagate gic's
> should propagate (rather than invent our own value) since this value
> is used to size fields within other properties within the tree.
> I'm not sure why I didn't do this as part of 816f5b
> On 16 Mar 2015, at 13:01, Mihai Donțu wrote:
>
> On Thu, 12 Mar 2015 10:21:56 + wei.l...@citrix.com wrote:
>> We are now two months into 4.6 development window. This is an email to keep
>> track of all the patch series I gathered. It is by no means complete and / or
>> acurate. Feel free t
> On 16 Mar 2015, at 10:43, Wei Liu wrote:
>
> On Fri, Mar 13, 2015 at 10:32:41AM +, Ian Campbell wrote:
>>
>> Wei, perhaps one or more of these could be applied:
>> * raise the bar for inclusion in the list for external projects to
>>be only the very largest most important ite
On Mon, 2015-03-16 at 12:00 +0100, Fabio Fantoni wrote:
> If usleep binary is missed in dom0 xendomains script use its function
> instead but as it is done now always rounds down to the nearest integer
> number, and in case it is less than 1 becomes 0.
> So for example in dom0 like those I use (d
On Mon, 2015-03-16 at 07:43 +0100, Juergen Gross wrote:
> On 03/04/2015 07:56 AM, Juergen Gross wrote:
> > In order to indicate the Xen tools capability to support the virtual
> > mapped linear p2m list instead the 3 level mfn tree add a flag to the
> > start_info page.
> >
> > Signed-off-by: Juerg
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 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(-)
diff --git a/tools/libxc/xg_save_restore.h b/tools/libxc/xg_save_restore.h
index bdd
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. Fortunatly 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.
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(-)
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 insertions(+)
diff --git a/tools/libxc/xc_core_arm.c b/tools/libxc/xc_core_arm.c
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
---
tools/libxc/xc_pm.c | 54 +++--
1 file changed, 36 insertions(+), 18 deletions(-)
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).
It also cleans up some of the invalid usage of errno (as the
underlaying calls already stash errno values) - and we just
need to bubble
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
---
tools/libxc/xc_offline_p
The goto looks very wrong when the rest of the code
has spaces.
Signed-off-by: Konrad Rzeszutek Wilk
---
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..828f234 100644
--- a/tools/
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
---
tools/libxc/xc_physdev.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
di
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_save.c | 8 +++-
3 files changed, 35 insertions(+), 8 deletions(-)
diff --g
We should be using the errno that the hypercall left
instead of overwritting it with the return value.
Signed-off-by: Konrad Rzeszutek Wilk
---
tools/libxl/libxl_x86.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/tools/libxl/libxl_x86.c b/tools/libxl/libxl_x86.c
i
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
>>> On 13.03.15 at 21:16, wrote:
> Given these extra config accesses, I am seriously wondering whether it
> would be more efficient overall to trap&emulate dom0 completely and
> allow Xen to cache things like the current control register state,
> locations of capability structures, etc. I genuine
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.
Signed-off-by: Konrad Rzeszutek Wilk
---
tools/libxc/xc_domain.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tool
Instead of just the return value.
Signed-off-by: Konrad Rzeszutek Wilk
---
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 bf06fe4..20e379c 100644
--- a/tools/libxc/xc_dom_x86.c
+++ b/to
On Mon, 2015-03-16 at 10:38 -0400, Konrad Rzeszutek Wilk wrote:
> Do you want me to post it now (v1) or are you right now looking at the
> patchset and would want to finish that?
I'm battling yakks right now not reading the series, so you may as well
send it!
>
> >
> > > +errno = saved_errn
Bob,
adding the Test WG.
As so far no-one has responded to your offer to organise an on-line meeting to
walk interested parties the CI loop. If you are, please reply to this thread.
If no-one comes back, I am wondering whether it may not be better to put some
wiki pages together explaining ho
On 11/03/15 13:52, Jan Beulich wrote:
> It's not clear to me why only the enabling operation got handled so
> far.
Applied to devel/for-linus-4.1, thanks.
David
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
On 17/02/15 07:02, Juergen Gross wrote:
> Up to now the pvscsi frontend hasn't supported domain suspend and
> resume. When a domain with an assigned pvscsi device was suspended
> and resumed again, it was not able to use the device any more: trying
> to do so resulted in hanging processes.
>
> Sup
On 17/02/15 07:02, Juergen Gross wrote:
> When a xen domain is being restored the LUN state of a pvscsi device
> is "Connected" and not "Initialising" as in case of attaching a new
> pvscsi LUN.
>
> This must be taken into account when adding a new pvscsi device for
> a domain as otherwise the pvs
On 10/03/15 20:49, Tao Chen wrote:
> Add the {xen-pvscsi: } prefix in pr_fmt and remove DPRINTK, then
> replace all DPRINTK with pr_debug.
>
> Also fixed up some comments just as eliminate redundant whitespace
> and format the code.
>
> These will make the code easier to read.
Applied to devel/f
On 05/03/15 11:24, Dan Carpenter wrote:
> Static checkers complain about the missing call to misc_deregister() if
> bind_virq_for_mce() fails.
>
> Also I reversed the tests so that we do error handling instead of
> success handling. That way we just have a series of function calls
> instead of th
On Mon, Mar 16, 2015 at 10:13:50AM +, Stefano Stabellini wrote:
> On Fri, 13 Mar 2015, Konrad Rzeszutek Wilk wrote:
> > As the libxc library follows (mostly) the return negative
> > for failure and stashes the error value in errno.
> >
> > Signed-off-by: Konrad Rzeszutek Wilk
>
> Acked-by: S
On Mon, Mar 16, 2015 at 02:23:22PM +, Ian Campbell wrote:
> On Mon, 2015-03-16 at 10:11 -0400, Konrad Rzeszutek Wilk wrote:
> > static void hypercall_buffer_cache_lock(xc_interface *xch)
> > {
> > +int saved_errno;
> > if ( xch->flags & XC_OPENFLAG_NON_REENTRANT )
> > return
On Mon, 2015-03-16 at 10:11 -0400, Konrad Rzeszutek Wilk wrote:
> static void hypercall_buffer_cache_lock(xc_interface *xch)
> {
> +int saved_errno;
> if ( xch->flags & XC_OPENFLAG_NON_REENTRANT )
> return;
> +saved_errno = errno;
You can do the init on declaration.
> diff
On 16/03/15 14:06, Vijay Kilari wrote:
>>> @@ -343,17 +357,23 @@ static int its_queue_full(struct its_node *its)
>>> static struct its_cmd_block *its_allocate_entry(struct its_node *its)
>>> {
>>> struct its_cmd_block *cmd;
>>> -u32 count = 100;/* 1s! */
>>> +bool_t timeou
On Sun, Mar 15, 2015 at 09:34:16PM +, Ian Murray wrote:
> Hi,
>
> I have a domU guest that booted fine under Xen 4.4.1 with pvh=1 but now fails
> to boot with it under Xen 4.5.0. Removing pvh=1, i.e. booting it as
> traditional PV results in it booting fine.
>
> The only odd thing is that I
On Sat, Mar 14, 2015 at 07:55:39AM +, Ian Campbell wrote:
> On Fri, 2015-03-13 at 15:40 -0400, Konrad Rzeszutek Wilk wrote:
> > On Fri, Mar 13, 2015 at 03:31:12PM -0400, Konrad Rzeszutek Wilk wrote:
> > > Instead put the -Exx in errno.
> > >
> > > Signed-off-by: Konrad Rzeszutek Wilk
> > > --
On 16/03/15 13:16, 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 stuf
Hi Julien,
On Fri, Mar 13, 2015 at 5:16 PM, Julien Grall wrote:
> Hello Vijay,
>
> On 02/03/2015 12:30, vijay.kil...@gmail.com wrote:
>>
>> @@ -228,10 +242,10 @@ static struct its_collection
>> *its_build_mapd_cmd(struct its_cmd_block *cmd,
>>st
>>> On 13.03.15 at 11:13, wrote:
> @@ -1112,6 +1117,12 @@ The following resources are available:
>total/local memory bandwidth. Follow the same options with Cache Monitoring
>Technology.
>
> +* Cache Alllocation Technology (Broadwell and later). Information regarding
> + the cache allo
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' and KVM only -- the Xen code was a little more
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 use a callee saved call for the unlock function w
From: Peter Zijlstra
When we allow for a max NR_CPUS < 2^14 we can optimize the pending
wait-acquire and the xchg_tail() operations.
By growing the pending bit to a byte, we reduce the tail to 16bit.
This means we can use xchg16 for the tail part and do away with all
the repeated compxchg() oper
1 - 100 of 177 matches
Mail list logo
