search for: is_idle_vcpu

Address some credit2 issues. This patch series, along with the recent changes to the cpupools interface, should address some of the strange credit2 instability. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...her APs. Signed-off-by Kevin Tian <kevin.tian@intel.com> diff -r bf41be7bddea xen/common/domain.c --- a/xen/common/domain.c Mon Dec 01 14:46:11 2008 -0500 +++ b/xen/common/domain.c Tue Dec 09 20:56:23 2008 -0500 @@ -135,7 +135,8 @@ v->vcpu_id = vcpu_id; v->runstate.state = is_idle_vcpu(v) ? RUNSTATE_running : RUNSTATE_offline; - v->runstate.state_entry_time = NOW(); + /* Don''t use NOW() before xen time sub-system is intialized */ + v->runstate.state_entry_time = is_idle_vcpu(v) ? 0 : NOW(); spin_lock_init(&v->virq_lock); __________________...

...u); - set_timer(&spc->ticker, NOW() + MILLISECS(CSCHED_MSECS_PER_TICK)); + set_timer(&spc->ticker, NOW() + MICROSECS(prv->tick_period_us) ); } static struct csched_vcpu * @@ -1375,7 +1374,7 @@ csched_schedule( * Return task to run next... */ ret.time = (is_idle_vcpu(snext->vcpu) ? - -1 : MILLISECS(CSCHED_MSECS_PER_TSLICE)); + -1 : MILLISECS(prv->tslice_ms)); ret.task = snext->vcpu; CSCHED_VCPU_CHECK(ret.task); @@ -1469,10 +1468,9 @@ csched_dump(const struct scheduler *ops) "\tweight...

...{ update_dom_time(next); if ( next->sleep_tick != schedule_data[cpu].tick ) - send_guest_virq(next, VIRQ_TIMER); + arch_send_timer_event(next); } TRACE_4D(TRC_SCHED_SWITCH, @@ -501,7 +501,7 @@ static void t_timer_fn(void *unused) if ( !is_idle_vcpu(v) ) { update_dom_time(v); - send_guest_virq(v, VIRQ_TIMER); + arch_send_timer_event(v); } page_scrub_schedule_work(); @@ -515,7 +515,7 @@ static void dom_timer_fn(void *data) struct vcpu *v = data; update_dom_time(v); - send_guest_virq(v, VIRQ...

...state sync forced earlier. + */ +#if defined(CONFIG_X86_64) +unsigned long saved_lstar, saved_cstar; +#endif +void save_rest_processor_state(void) +{ + /* + * Net effect of unlazy_fpu is to set cr0.ts and thus there''s no + * need to restore fpu after resume. + */ + if (!is_idle_vcpu(current)) + unlazy_fpu(current); + +#if defined(CONFIG_X86_64) + rdmsrl(MSR_CSTAR, saved_cstar); + rdmsrl(MSR_LSTAR, saved_lstar); +#endif +} + +#define loaddebug(_v,_reg) \ + __asm__ __volatile__ ("mov %0,%%db" #_reg : : "r" ((_v)->debugreg[_reg])) + +void re...

In order to avoid high-frequency cpu migration, vcpus may in fact be scheduled slightly out-of-order. Account for this situation properly. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> credit2: Fix erronous ASSERT In order to avoid high-frequency cpu migration, vcpus may in fact be scheduled slightly out-of-order. Account for this situation properly. v2: - Update comment

...heduled) { @@ -789,13 +731,14 @@ static struct task_slice sedf_do_schedul struct sedf_vcpu_info *runinf, *waitinf; struct task_slice ret; - /*idle tasks don''t need any of the following stuf*/ + /* Idle tasks don''t need any of the following stuf */ if ( is_idle_vcpu(current) ) goto check_waitq; - /* create local state of the status of the domain, in order to avoid - inconsistent state during scheduling decisions, because data for - vcpu_runnable is not protected by the scheduling lock!*/ + /* Create local state of the status of th...

This patch series is a reworking of a series developed by Mukesh Rathor at Oracle. The entirety of the design and development was done by him; I have only reworked, reorganized, and simplified things in a way that I think makes more sense. The vast majority of the credit for this effort therefore goes to him. This version is labelled v13 because it is based on his most recent series, v11.

...e(); + sleep_diff = now - sleep_start; + wc_sec = now; + jiffies += sleep_diff * HZ; + + stime_platform_stamp += SECONDS(sleep_diff); + if (cur_timer->resume) + cur_timer->resume(); + + init_percpu_time(); + /* Resume may happen on an idle vcpu */ + if (!is_idle_vcpu(current)) + update_vcpu_system_time(current); + return 0; } /* diff -r 3ef0510e44d0 xen/drivers/char/console.c --- a/xen/drivers/char/console.c Tue May 08 10:21:23 2007 +0100 +++ b/xen/drivers/char/console.c Mon May 14 15:05:28 2007 -0400 @@ -914,6 +914,26 @@ void __warn(char *file, i...

...,7 +82,7 @@ struct vcpu *alloc_vcpu( v->domain = d; v->vcpu_id = vcpu_id; - v->vcpu_info = &d->shared_info->vcpu_info[vcpu_id]; + v->vcpu_info = shared_info_addr(d, vcpu_info[vcpu_id]); spin_lock_init(&v->pause_lock); v->runstate.state = is_idle_vcpu(v) ? RUNSTATE_running : RUNSTATE_offline; Index: 2006-10-04/xen/common/event_channel.c =================================================================== --- 2006-10-04.orig/xen/common/event_channel.c 2006-08-07 09:07:03.000000000 +0200 +++ 2006-10-04/xen/common/event_channel.c 2006-10-04 15:11:03...

The first patch really isn''t as much of a follow-up than what triggered the security issues to be noticed in the first place. 1: x86: preserve FPU selectors for 32-bit guest code 2: x86: fix XCR0 handling 3: x86/xsave: adjust state management 4: x86/fxsave: bring in line with recent xsave adjustments The first two I would see as candidates for 4.3 (as well as subsequent backporting,

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

I''ve addressed all (I think/hope) of the review comments. The main change is to expose the guest virtual platform (e.g. memory layout and interrupt usage etc) to the toolstack via the public interface. This is then used during FDT generation. I have just codified the current defacto standard layout, it''s probably not the best layout but any change can be a separate patch/series.

Biggest change is to switch the new DTB node to /xen-core-devices instead of /xen at Stefano''s request. I also dropped the few patches title HACK etc which weren''t supposed to be there and fixed up some bits and pieces which folks commented on. George, WRT the freeze I think this is functionality which we cannot ship Xen 4.4 without. The impact is entirely constrained to the

This round implements all of the review comments from V2 and all patches are now acked. Unless there are any objections I intend to apply later this morning. Ian.

First off, Apologies for the massive patch series... This series boots a 32-bit dom0 kernel to a command prompt on an ARMv8 (AArch64) model. The kernel is the same one as I am currently using with the 32 bit hypervisor I haven''t yet tried starting a guest or anything super advanced like that ;-). Also there is not real support for 64-bit domains at all, although in one or two places I