 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] [PATCH]HVM acpi timer update
| To: | "Wang, Winston L" <winston.l.wang@xxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] [PATCH]HVM acpi timer update |
| From: | "Christian Limpach" <christian.limpach@xxxxxxxxx> |
| Date: | Thu, 27 Jul 2006 11:36:47 +0100 |
| Cc: | Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Tang Liang <tangliang@xxxxxxxxxx> |
| Delivery-date: | Thu, 27 Jul 2006 03:37:10 -0700 |
| 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:content-disposition:references; b=K0kLV0N+jFtpUTY+/WdyUZAHHR+sZrqX9GYv0phGeYUi26jFXSwE28pJ/LCm3m3fvf6V731zEMyDSqWEwNm0Jh5nS50sXEO4KcoT9jYDcYMp9DOg/3Wovtcm8lbf4iim1ioFK66yksaJgKh9aYq8HPU+IDL5sONRr73+yPK/oPU= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| In-reply-to: | <33C3AAF1C7AF99469FD89F86616C52455A654F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| 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> |
| References: | <33C3AAF1C7AF99469FD89F86616C52455A654F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Reply-to: | Christian.Limpach@xxxxxxxxxxxx |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On 7/27/06, Wang, Winston L <winston.l.wang@xxxxxxxxx> wrote: The patch updated the hvm acpi timer by reducing invocations to timer_update and some minor code style clean up: 1) Fixed new qemu 0.8.1 pm timer incorrect frequency and allow acpi windows install and boot correctly 2) Resolved performance issues caused by old acpi timer, testing showing guest IDE DMA and kernel build have the same performance on non-acpi mode. Why does this still need a timer at all? Why can't we just compute the acpi timer's value when it is being read: (get_vm_clock() - vm_clock_value_when_domain_was_started) divided/multiplied to get the expected frequency? Also, since this is using vm_clock, the acpi_timer will advance even if the domain is not scheduled -- is this the expected behaviour? christian _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] [PATCH] [HVM] Rename file hvm_info_table.h to platform.h, Li, Xin B |
|---|---|
| Next by Date: | [Xen-devel] [PATCH] remove unused definitions in xc_hvm_build.c, Li, Xin B |
| Previous by Thread: | [Xen-devel] [PATCH]HVM acpi timer update, Wang, Winston L |
| Next by Thread: | RE: [Xen-devel] [PATCH]HVM acpi timer update, Wang, Winston L |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
