WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Interrupt forwarding

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Interrupt forwarding
From: Jon Smirl <jonsmirl@xxxxxxxxx>
Date: Sat, 12 Mar 2005 15:07:17 -0500
Cc: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx, ian.pratt@xxxxxxxxxxxx
Delivery-date: Sat, 12 Mar 2005 20:08:59 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ZfIi4I+036Q4KqXWvUSZ2JTQwkCLfeTeeoq6Po6/KR+h0STFeNnI3RVMTySpaxX2256pfwVT7TnqpqAz6Oz77+ewfdy7aEaGK1n/kAw0jhFz6TyvVmdqm7DU846QMOrv5YhWz6yCEU6yaQmC6eZCvsfzXkt1DKm49WBXDRfnch8=
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3607@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3607@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: Jon Smirl <jonsmirl@xxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
On Sat, 12 Mar 2005 19:59:15 -0000, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
> 
> 
> > > We don't go that far. A sensible approach would be to require the
> > > driver to be restarted, and to reset the hardware device, before
> > > unmasking. Or to rate limit each interrupt line to an
> > > administrator-configurable 'reasonable' number of IRQs per second --
> > > this might also catch bugs where drivers are not properly acking
> > > devices for other reasons.
> >
> > In x86 boxes almost everything is shared. Leaving the interrupt masked
> > off will probably disable 20% of the hardware in the box.
> 
> That's not my experience, certainly on modern server hardware. On
> systems with an IOAPIC its rare to see a shared interrupt, and even if
> you do you can typically avoid it just by swapping a couple of PCI cards
> around.
> 
> Ian
> 

If I load video drivers two more drivers will share interrupts. 169
with have 4 devices on it instead of three.

[jonsmirl@jonsmirl proc]$ cat interrupts
           CPU0       CPU1
  0:     484259     448188    IO-APIC-edge  timer
  8:          0          0    IO-APIC-edge  rtc
  9:          0          0   IO-APIC-level  acpi
 14:        776        762    IO-APIC-edge  ide0
 15:       8040       7726    IO-APIC-edge  ide1
169:      37509          0   IO-APIC-level  libata, uhci_hcd:usb4, eth0
185:          5          0   IO-APIC-level  ehci_hcd:usb1
193:        548        272   IO-APIC-level  uhci_hcd:usb2, uhci_hcd:usb5
201:          0          0   IO-APIC-level  uhci_hcd:usb3
209:          3          0   IO-APIC-level  ohci1394
NMI:          0          0
LOC:     932357     932306
ERR:          0
MIS:          0
[jonsmirl@jonsmirl proc]$

-- 
Jon Smirl
jonsmirl@xxxxxxxxx


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel