From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <kraxel@redhat.com>
Cc: "'Pawel Polawski'" <ppolawsk@redhat.com>,
"'Oliver Steffen'" <osteffen@redhat.com>,
"'Laszlo Ersek'" <lersek@redhat.com>
Subject: 回复: [edk2-devel] [PATCH 1/1] OvmfPkg: fix PcdFSBClock
Date: Wed, 25 May 2022 09:42:50 +0800 [thread overview]
Message-ID: <021e01d86fd8$be8c1460$3ba43d20$@byosoft.com.cn> (raw)
In-Reply-To: <20220524062922.f3hxehguhpgvlrjh@sirius.home.kraxel.org>
Gerd:
I am OK to merge this bug fix for stable tag 202205 once this patch passes
code review.
Thanks
Liming
> -----邮件原件-----
> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Gerd
> Hoffmann
> 发送时间: 2022年5月24日 14:29
> 收件人: devel@edk2.groups.io; gaoliming@byosoft.com.cn
> 抄送: Pawel Polawski <ppolawsk@redhat.com>; Oliver Steffen
> <osteffen@redhat.com>; Laszlo Ersek <lersek@redhat.com>
> 主题: Re: [edk2-devel] [PATCH 1/1] OvmfPkg: fix PcdFSBClock
>
> 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
>
>
>
>
>
next prev parent reply other threads:[~2022-05-25 1:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 13:45 [PATCH 1/1] OvmfPkg: fix PcdFSBClock Gerd Hoffmann
2022-05-24 6:29 ` Gerd Hoffmann
2022-05-25 1:42 ` gaoliming [this message]
2022-05-25 3:00 ` [edk2-devel] " Yao, Jiewen
2022-05-25 13:43 ` Yao, Jiewen
2022-05-24 17:50 ` Laszlo Ersek
2022-05-25 6:28 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='021e01d86fd8$be8c1460$3ba43d20$@byosoft.com.cn' \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox