From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124])
 by mx.groups.io with SMTP id smtpd.web09.6229.1653373771245569462
 for <devel@edk2.groups.io>;
 Mon, 23 May 2022 23:29:31 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Ti3IeWLE;
 spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1653373770;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=NLaOHFFNVFeuCvyCLU48JmATZSujg8aN4oKYxhTCds4=;
	b=Ti3IeWLEwXZSpeoVqfSSj7ek9O8tx28U5YGxLm9lIaR6vaSyXJ9EHEpWURJvFspL+g4Fbt
	k9GpscZUBIl2SF25V//BWEKnqHiQQvBS53Iuy6t1yKml67xLTueZH3tivQIJc7oRXaXrjX
	EROVefoUetZt5FOS+L+lxZDMRp/nQKg=
Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com
 [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS
 (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 us-mta-608-yCsa05c2NkSRPUXoPdTDVA-1; Tue, 24 May 2022 02:29:27 -0400
X-MC-Unique: yCsa05c2NkSRPUXoPdTDVA-1
Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E736D380673C;
	Tue, 24 May 2022 06:29:26 +0000 (UTC)
Received: from sirius.home.kraxel.org (unknown [10.39.192.41])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 9B7DA401E63;
	Tue, 24 May 2022 06:29:24 +0000 (UTC)
Received: by sirius.home.kraxel.org (Postfix, from userid 1000)
	id A90501800393; Tue, 24 May 2022 08:29:22 +0200 (CEST)
Date: Tue, 24 May 2022 08:29:22 +0200
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, gaoliming@byosoft.com.cn
Cc: Pawel Polawski <ppolawsk@redhat.com>,
	Oliver Steffen <osteffen@redhat.com>,
	Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH 1/1] OvmfPkg: fix PcdFSBClock
Message-ID: <20220524062922.f3hxehguhpgvlrjh@sirius.home.kraxel.org>
References: <20220523134504.1304459-1-kraxel@redhat.com>
MIME-Version: 1.0
In-Reply-To: <20220523134504.1304459-1-kraxel@redhat.com>
X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10
Authentication-Results: relay.mimecast.com;
	auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kraxel@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, May 23, 2022 at 03:45:04PM +0200, Gerd Hoffmann wrote:
> kvm FSB clock is 1GHz, not 100 MHz.  Timings are off by factor 10.
> Fix all affected build configurations.  Not changed: Microvm and
> Cloudhw (they have already have the correct value), and Xen (has
> no fixed frequency, the PCD is configured at runtime by platform
> initialization code).
> 
> Fixes: c37cbc030d96 ("OvmfPkg: Switch timer in build time for OvmfPkg")

Cc'ing gaoliming.

This fixes a regression and should go into 220205

thanks,
  Gerd