search for: sdom

...sizeof(xc_shadow_op_stats_t)); - - if ( mb ) + + if ( mb ) *mb = domctl.u.shadow_op.mb; return (rc == 0) ? domctl.u.shadow_op.pages : rc; @@ -696,6 +696,79 @@ int xc_get_hvm_param(int handle, domid_t return rc; } +int xc_add_adom(int handle, domid_t adom, domid_t sdom, uint16_t *reason) +{ + int ret; + + DECLARE_DOMCTL; + + domctl.cmd = XEN_DOMCTL_scheduler_op; + domctl.u.scheduler_op.cmd = XEN_DOMCTL_SCHEDOP_sdom; + domctl.u.scheduler_op.u.sdom.op = SDOM_add_adom; + domctl.u.scheduler_op.u.sdom.adom = adom; + domctl.u.scheduler_op.u.sdom.sd...

...8,7 @@ __gnttab_map_grant_ref( */ for ( ; ; ) { - u32 scombo, prev_scombo, new_scombo; + union grant_combo scombo, prev_scombo, new_scombo; if ( unlikely((sflags & GTF_type_mask) != GTF_permit_access) || unlikely(sdom != led->domain->domain_id) ) @@ -186,22 +197,25 @@ __gnttab_map_grant_ref( sflags, sdom, led->domain->domain_id); /* Merge two 16-bit values into a 32-bit combined update. */ - /* NB. Endianness! */ - scombo = ((u32)sdom &lt...

...T_HEAD(&spc->runq); spc->runq_sort_last = prv->runq_sort; @@ -1002,7 +1001,7 @@ csched_acct(void* dummy) * for one full accounting period. We allow a domain to earn more * only when the system-wide credit balance is negative. */ - credit_peak = sdom->active_vcpu_count * CSCHED_CREDITS_PER_ACCT; + credit_peak = sdom->active_vcpu_count * prv->credits_per_tslice; if ( prv->credit_balance < 0 ) { credit_peak += ( ( -prv->credit_balance @@ -1014,7 +1013,7 @@ csched_acct(void* dummy)...

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

...e, a couple things: > Approximate dominators (for example, semi-dominators) can be computed > fast (a DFS walk of the CFG with no real additional computation) > Except in strange CFGs that jump around a lot, they are the dominators. > > More importantly, the dominator is either the sdom or a proper > ancestor of the sdom. > > The practical impact of this is that if you use them as if they were > dominators, the set of conditions you discover will not be "too > wrong". Occasionally wrong, but mostly not. > > My guess is the cost of doing approxima...

All, I'm working on an improvement to the inline cost model, but I'm unsure how to proceed. Let me begin by first describing the problem I'm trying to solve. Consider the following pseudo C code: *typedef struct element { unsigned idx; } element_t; * *static inline unsigned char fn2 (element_t *dst_ptr, const element_t *a_ptr, const element_t *b_ptr,

...in this way. Otherwise, a couple things: Approximate dominators (for example, semi-dominators) can be computed fast (a DFS walk of the CFG with no real additional computation) Except in strange CFGs that jump around a lot, they are the dominators. More importantly, the dominator is either the sdom or a proper ancestor of the sdom. The practical impact of this is that if you use them as if they were dominators, the set of conditions you discover will not be "too wrong". Occasionally wrong, but mostly not. My guess is the cost of doing approximate dominators is ~50-60% of the cost...

Hello, This small series deals with some weirdness in the mechanism with which the credit scheduler choses what PCPU to tickle upon a VCPU wake-up. Details are available in the changelog of the first patch. The new approach has been extensively benchmarked and proved itself either beneficial or harmless. That means it does not introduce any significant amount of overhead and/or performances

Hello, This series exposes global performance counters (PCOUNTER) to the userspace through the nvif interface by reworking most of the code related to the PM engine. This interface will allow the userspace to control and monitor complex hardware events like the proprietary driver already does, for example with CUPTI and PerfKit. For now, this series only exposes performance counters on NV50,

This patch set adds XSM security labels to useful debugging output locations, and fixes some assumptions that all interrupts behaved like GSI interrupts (which had useful non-dynamic IDs). It also cleans up the policy build process and adds an example of how to use the user field in the security context. Debug output: [PATCH 01/10] xsm: Add security labels to event-channel dump [PATCH 02/10] xsm:

...tors) can > be computed fast (a DFS walk of the CFG with no real > additional computation) > > Except in strange CFGs that jump around a lot, they are > the dominators. > > More importantly, the dominator is either the sdom or a > proper ancestor of the sdom. > > The practical impact of this is that if you use them as if > they were dominators, the set of conditions you discover > will not be "too wrong". Occasionally wrong, but mostly not. >...

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU