From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: HPET configuration in Seabios Date: Mon, 29 Aug 2011 13:05:06 +0200 Message-ID: <4E5B7262.4010902@siemens.com> References: <4B17C12B.4020300@linux.vnet.ibm.com> <4B17CC5F.20101@redhat.com> <4E59F15E.6000201@redhat.com> <4E5AA849.5090400@web.de> <20110828221437.GA27777@morn.localdomain> <4E5B2450.3050209@redhat.com> <4E5B691C.9050507@siemens.com> <4E5B7168.5070306@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Andrew Theurer , Gleb Natapov , "kvm@vger.kernel.org list" , seabios , ya su , Alexander Graf , QEMU Developers , Kevin O'Connor To: Avi Kivity Return-path: In-Reply-To: <4E5B7168.5070306@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org On 2011-08-29 13:00, Avi Kivity wrote: > On 08/29/2011 01:25 PM, Jan Kiszka wrote: >>> >>> Can't seabios just poke at the hpet itself and see if it exists or not? >>> >> >> Would be hard for the BIOS to guess the locations of the blocks unless >> we define the addresses used by QEMU as something like base + hpet_no * >> block_size in all cases. >> > > Currently we have a fixed address. We could do: > > if available in fw_cfg: > use that (may indicate no hpet) > elif fixed address works: > use that > else > no hpet Currently, we also only have a single HPET block, but that's just because of some QEMU limitations that will vanish sooner or later. Then nothing will prevent multiple "-device hpet,base=XXX". Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux