search for: nr_pirqs

Looking at the MSI implementation I have a couple of questions: 1) There currently seems to be a hidden requirement of NR_PIRQS in the kernel needing to be no smaller than NR_IRQS in the hypervisor. Otherwise, the pirq returned from PHYSDEVOP_map_pirq may collide with the dynamic IRQs in the kernel or even be out of range altogether. Therefore I think that NR_PIRQS has to become a variable defaulting to 256 but getting init...

...M_IRQ_DPCI_*_MSI bits is actually the correct one. Having a single structure only would make it a lot easier to convert struct hvm_mirq_dpci_mapping * in struct hvm_irq_dpci to a sparse struct hvm_mirq_dpci_mapping ** (populating slots only as they get used), thus shrinking the currently two d->nr_pirqs sized array allocations in pt_irq_create_bind_vtd() to a single one with only pointer size array elements (allowing up to about 512 domain pirqs rather than currently slightly above 80 without exceeding PAGE_SIZE on allocation). Also I''m wondering why the PT_IRQ_TYPE_MSI path of pt_irq_cr...

...ctor_pirq[vector] = pirq; done: + spin_unlock_irqrestore(&desc->lock, flags); return ret; } @@ -139,18 +127,18 @@ static int unmap_domain_pirq(struct doma unsigned long flags; irq_desc_t *desc; int vector, ret = 0; - - if ( d == NULL || pirq < 0 || pirq >= NR_PIRQS ) + bool_t forced_unbind; + + if ( (pirq < 0) || (pirq >= NR_PIRQS) ) return -EINVAL; if ( !IS_PRIV(current->domain) ) return -EINVAL; - ASSERT(spin_is_locked(&d->arch.irq_lock)); + ASSERT(spin_is_locked(&d->evtchn_lock)); vector = d...

(moving to xen-devel, xen-arm is for the older PV ARM port) On Tue, 2013-06-25 at 23:59 +0000, Eric Trudeau wrote: > Hi, I am trying to build the XEN tools for our port of XEN to our > Cortex A15-based platform. > > I am using the repo at git://xenbits.xenproject.org/xen.git to > cross-compile the tools into our rootfs. Which branch/changeset are you using? I've heard that

...58 (error -22) [ 2.836769] xen:events: Failed to obtain physical IRQ 59 (error -22) [ 2.836780] xen:events: Failed to obtain physical IRQ 60 (error -22) [ 2.836793] xen:events: Failed to obtain physical IRQ 61 (error -22) There is a check: 463 if ( (pirq < 0) || (pirq >= d->nr_pirqs) ) 464 return -EINVAL; But there is also a call to pirq_guest_bind, which could return EINVAL. > Anyhow for PV guests in the hypervisor there is a check: > 414 if ( !is_hvm_domain(d) && !pirq_access_permitted(d, pirq) ) > 415 return -EPERM; > 416 >...

...over the same problem that has been described quite well by Mark Doll in his posting "xen_net: Failed to connect all virtual interfaces: err=-100" here: http://lists.xensource.com/archives/html/xen-users/2005-04/msg00447.html As it was still present in 2.0.6, I tried 3.0-devel and found NR_PIRQS and NR_DYNIRQS had been adjusted there - so I hoped for the best. I was then able to fire up my virtual test network and get it running with 20 nodes and approx. 120 interfaces, without problems at first. The vifs are wired to ~60 bridge interfaces, 2 vifs each, and I can access all domU-nodes wit...

...over the same problem that has been described quite well by Mark Doll in his posting "xen_net: Failed to connect all virtual interfaces: err=-100" here: http://lists.xensource.com/archives/html/xen-users/2005-04/msg00447.html As it was still present in 2.0.6, I tried 3.0-devel and found NR_PIRQS and NR_DYNIRQS had been adjusted there - so I hoped for the best. I was then able to fire up my virtual test network and get it running with 20 nodes and approx. 120 interfaces, without problems at first. The vifs are wired to ~60 bridge interfaces, 2 vifs each, and I can access all domU-nodes wit...

These two patches were originally part of the XSM series that I have posted, and remain prerequisites for that series. However, they are independent of the XSM changes and are a useful simplification regardless of the use of XSM. The Acked-bys on these patches were provided before rebasing them over the copyback changes in 26268:1b72138bddda, which had minor conflicts that I resolved. [PATCH

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Hey, Are there any known issues with the Intel''s integrated HD graphics 4000? I just bought a new laptop and have tried everything I can think of to get Xen to load. After choosing Xen in GRUB, it just boots to a black screen. There is no error message , no dmesg output, nothing. I have no idea what is causing this problem. I''ve gotten Xen to install with no problems on another

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Hi. This patchset implements xen/ia64 domU support. Qing He and Eddie Dong also has been woring on pv_ops so that I want to discuss before going further and avoid duplicated work. I suppose that Eddie will also post his own patch. So reviewing both patches, we can reach to better pv_ops interface. - I didn't changed the ia64 intrinsic paravirtulization abi from the last post. Presumably it

Hi. This patchset implements xen/ia64 domU support. Qing He and Eddie Dong also has been woring on pv_ops so that I want to discuss before going further and avoid duplicated work. I suppose that Eddie will also post his own patch. So reviewing both patches, we can reach to better pv_ops interface. - I didn't changed the ia64 intrinsic paravirtulization abi from the last post. Presumably it

Hi, All Intel QA conducted a full validation for xen 4.1 rc1, it includes VT-x, VT-d, SRIOV, RAS, TXT and xl tools testing. 24 issues were exposed. Refer the bug list, please. We already assigned 14 bugs to Intel developers (which has an ''Intel'' tag in the bug title), most of the rest 10 bugs are related xl command. For the these bugs, need community''s help to fix