From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1N7tva-0007lb-DI
	for qemu-devel@nongnu.org; Tue, 10 Nov 2009 11:50:46 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1N7tvV-0007hY-LG
	for qemu-devel@nongnu.org; Tue, 10 Nov 2009 11:50:45 -0500
Received: from [199.232.76.173] (port=43906 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1N7tvV-0007hP-HY
	for qemu-devel@nongnu.org; Tue, 10 Nov 2009 11:50:41 -0500
Received: from mx1.redhat.com ([209.132.183.28]:4332)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1N7tvV-0000qm-0b
	for qemu-devel@nongnu.org; Tue, 10 Nov 2009 11:50:41 -0500
Message-ID: <4AF999D8.8080600@redhat.com>
Date: Tue, 10 Nov 2009 18:50:32 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH V2 2/3] usb-gotemp: new module emulating
	a  USB thermometer
References: <1257845850-4660-1-git-send-email-scottt.tw@gmail.com>
	<1257845850-4660-2-git-send-email-scottt.tw@gmail.com>
	<1257845850-4660-3-git-send-email-scottt.tw@gmail.com>
	<4AF97D3B.8080601@redhat.com>
	<ef2f888d0911100714k351de5b8hea3a2b48935bde25@mail.gmail.com>
	<374D220D-FE6E-410B-83F3-E8988BA61A6D@suse.de>
In-Reply-To: <374D220D-FE6E-410B-83F3-E8988BA61A6D@suse.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexander Graf <agraf@suse.de>
Cc: Scott Tsai <scottt.tw@gmail.com>, qemu-devel@nongnu.org

On 11/10/2009 05:33 PM, Alexander Graf wrote:
> How about having a monitor command to change the temperature, 
> leveraging a "common interface"?
> That way in the future real host temperature measurements could maybe 
> get forwarded there too. At least for battery I've had several people 
> ask already if it's possible to read the host battery status (incl. AC 
> status) from inside the VM.

More ACPI functionality, so we can forward ACPI events from the host to 
the guest, would be welcome indeed.

-- 
error compiling committee.c: too many arguments to function