 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] "monitor"-ed address and IPI reduction
| To: | "Gang Wei" <gang.wei@xxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] "monitor"-ed address and IPI reduction |
| From: | "Jan Beulich" <JBeulich@xxxxxxxxxx> |
| Date: | Tue, 09 Mar 2010 08:08:36 +0000 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Tue, 09 Mar 2010 00:09:32 -0800 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| 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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
What is the point of specifying "current" as the address to monitor? The memory location of interest really is irq_stat[cpu].__softirq_pending, and if that was used it would then also be possible to actually avoid sending IPIs when monitor/mwait are in use, as is being done on Linux. Jan _______________________________________________ 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] unmodified drivers build error with 4.0.0-rc4 and 2.6.32 pv-ops, Pasi Kärkkäinen |
|---|---|
| Next by Date: | Re: [Xen-devel] Xen 4.0.0x allows for data corruption in Dom0, Pasi Kärkkäinen |
| Previous by Thread: | [Xen-devel] [PATCH] Add cpufreq sanity check, Yu, Ke |
| Next by Thread: | [Xen-devel] RE: "monitor"-ed address and IPI reduction, Wei, Gang |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
