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/
Home Products Support Community News


Re: [Xen-devel] [PATCH] new hvm platform vhpet enable parameter

To: "dan.magenheimer@xxxxxxxxxx" <dan.magenheimer@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] new hvm platform vhpet enable parameter
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 14 Feb 2008 17:52:14 +0000
Delivery-date: Thu, 14 Feb 2008 09:53:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080214095226125.00000001516@djm-pc>
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: AchpsV707M1mJgwlSGunlYGnJNsR0QAAQJ/OAADzrCAAAJFmswAEdqXAAVfVoBAAAit5rg==
Thread-topic: [Xen-devel] [PATCH] new hvm platform vhpet enable parameter
User-agent: Microsoft-Entourage/
It has been taken. Xen-unstable:17017.

 -- Keir

On 14/2/08 16:52, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> I see this patch hasn't been taken yet.  Is there something
> else I need to do or are you not in agreement that the
> acpi part is cosmetic?
> Thanks,
> Dan
>> -----Original Message-----
>> From: Dan Magenheimer [mailto:dan.magenheimer@xxxxxxxxxx]
>> Sent: Thursday, February 07, 2008 1:54 PM
>> To: 'Keir Fraser'; 'xen-devel@xxxxxxxxxxxxxxxxxxx'
>> Subject: RE: [Xen-devel] [PATCH] new hvm platform vhpet
>> enable parameter
>>> Yes, tools/firmware/hvmloader/acpi/dsdt.asl. The right way to
>>> do this will
>>> be to gate it on a flag set up in memory by hvmloader (we
>>> already do this
>>> e.g., for com1 and com2 -- see construct_bios_info_table() in
>>> build.c in the
>>> same directory). That might be a bit tricky as it probably
>>> needs a bit of
>>> ASL hacking, which has a little learning curve. I can take a
>>> look maybe next
>>> week.
>> OK, here's the updated patch:
>> 1) hpet instead of vhpet
>> 2) against 3.2-testing tip
>> This will work without the acpi changes so could be checked in
>> independently.  Though it may be a bit misleading for the
>> guest to print out that it found an hpet in acpi and then
>> be unable to use it, the acpi part is largely cosmetic
>> and (as you point out) a bit tricky so better left for
>> your capable hands.
>> Thanks,
>> Dan

Xen-devel mailing list