 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] [PATCH] Reuse irq number for virq/ipi after vcpu unplug/plug
| To: | <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] [PATCH] Reuse irq number for virq/ipi after vcpu unplug/plug |
| From: | "Tian, Kevin" <kevin.tian@xxxxxxxxx> |
| Date: | Sat, 3 Feb 2007 12:49:08 +0800 |
| Delivery-date: | Fri, 02 Feb 2007 20:48:45 -0800 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
| Thread-index: | AcdHTqIuaJIC5LiAQZGiyexI3PPLIQ== |
| Thread-topic: | [PATCH] Reuse irq number for virq/ipi after vcpu unplug/plug |
Irq nunmber for per-vcpu event (virq/ipi) needs kept
accross vcpu plug/unplug, once allocated. We just
reuse this irq number and bind it to a new event port.
Or else, /proc/interrupt exports messed statistics
like:
ot@localhost ~]# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
256: 423066 0 0 0 Dynamic-irq timer0
257: 3014 0 0 0 Dynamic-irq
resched0
258: 37 0 0 0 Dynamic-irq
callfunc0
259: 713 0 0 0 Dynamic-irq xenbus
260: 343 1323 65 50 Dynamic-irq
xencons
261: 270 62 0 0 Dynamic-irq blkif
262: 0 1053818 1220 855 Dynamic-irq
resched1
263: 0 0 2165 53 Dynamic-irq
callfunc1
264: 0 3218 69 0 Dynamic-irq timer1
265: 0 0 42768 228 Dynamic-irq
resched2
266: 0 45 0 1867 Dynamic-irq
callfunc2
267: 0 0 39543 256 Dynamic-irq timer2
268: 0 2244 46 33027 Dynamic-irq
resched3
269: 1585 0 0 0 Dynamic-irq
callfunc3
270: 11273 0 1885 1073 Dynamic-irq timer3
NMI: 0 0 0 0
LOC: 0 0 0 0
ERR: 0
MIS: 0
You can see from above that each virq/ipi have
statistics on several vcpus, when that data on
other vcpus belong to other virq/ipi before unplug.
This also applies to save/restore for same issue.
Signed-off-by Kevin Tian <kevin.tian@xxxxxxxxx>
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] Re: [patch] pvfb: Split mouse and keyboard into separate devices., Daniel P. Berrange |
|---|---|
| Next by Date: | [Xen-devel] A Performance Comparison of Hypervisors, Nicholas Lee |
| Previous by Thread: | [Xen-devel]building domU vm by specifying kernel?, cm ko |
| Next by Thread: | Re: [Xen-devel] [PATCH] Reuse irq number for virq/ipi after vcpu unplug/plug, Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
