From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=pass header.i=@citrix.com header.s=securemail header.b=T5lFRmV5; spf=pass (domain: citrix.com, ip: 216.71.145.155, mailfrom: anthony.perard@citrix.com) Received: from esa3.hc3370-68.iphmx.com (esa3.hc3370-68.iphmx.com [216.71.145.155]) by groups.io with SMTP; Mon, 12 Aug 2019 07:45:09 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=citrix.com; s=securemail; t=1565621110; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=8LpCWNDEppu4zSi1KULQfGaE8LtZjXPeWGyd8nTtnlw=; b=T5lFRmV5N0fkEMIki8GPQ2df/IdItWPTQYgsEj5WnZtaBpHyD7g3K/4G mj+xlYx2D6vSVdOoNuTO6GGu2bY/UbWiFcjgfuv4U3aOmABsTijCUaVsj OmQ0NPiPjUnyohwJ4CXgFch96P6NirrJHLHCZaRgR9f1ILVWKtT8l9LtZ M=; Authentication-Results: esa3.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none; spf=None smtp.pra=anthony.perard@citrix.com; spf=Pass smtp.mailfrom=anthony.perard@citrix.com; spf=None smtp.helo=postmaster@mail.citrix.com Received-SPF: None (esa3.hc3370-68.iphmx.com: no sender authenticity information available from domain of anthony.perard@citrix.com) identity=pra; client-ip=162.221.158.21; receiver=esa3.hc3370-68.iphmx.com; envelope-from="anthony.perard@citrix.com"; x-sender="anthony.perard@citrix.com"; x-conformance=sidf_compatible Received-SPF: Pass (esa3.hc3370-68.iphmx.com: domain of anthony.perard@citrix.com designates 162.221.158.21 as permitted sender) identity=mailfrom; client-ip=162.221.158.21; receiver=esa3.hc3370-68.iphmx.com; envelope-from="anthony.perard@citrix.com"; x-sender="anthony.perard@citrix.com"; x-conformance=sidf_compatible; x-record-type="v=spf1"; x-record-text="v=spf1 ip4:209.167.231.154 ip4:178.63.86.133 ip4:195.66.111.40/30 ip4:85.115.9.32/28 ip4:199.102.83.4 ip4:192.28.146.160 ip4:192.28.146.107 ip4:216.52.6.88 ip4:216.52.6.188 ip4:162.221.158.21 ip4:162.221.156.83 ~all" Received-SPF: None (esa3.hc3370-68.iphmx.com: no sender authenticity information available from domain of postmaster@mail.citrix.com) identity=helo; client-ip=162.221.158.21; receiver=esa3.hc3370-68.iphmx.com; envelope-from="anthony.perard@citrix.com"; x-sender="postmaster@mail.citrix.com"; x-conformance=sidf_compatible IronPort-SDR: YyIoMticQ3ijvYXG0duzSw86KOHl67AXGgoFvwIU1YpO6bBwI9lDmr6JvcIs0aKdNlljZCI/Ju jrfS6w0Y8SBLFo2s1kgqK6JC/N3ePNdjF3hGS7yRXJ3hGFIiGTk41Uwu651Jo4ksFyo9FzJhEg YBwgydEYNRwdojetHrvNgIpJs0pHFt93g/+uj0GgwQs6lsP7+fxyvAqmluVpiQ5U5kQzKeKYcG 69tUvxwPGLwuiBvy0mbhWIJZfbRlsPkTT3NLEILvMX+BMqzvjMKrZDQkzf8NXN24H7v4RY762m wtI= X-SBRS: 2.7 X-MesageID: 4169836 X-Ironport-Server: esa3.hc3370-68.iphmx.com X-Remote-IP: 162.221.158.21 X-Policy: $RELAYED X-IronPort-AV: E=Sophos;i="5.64,377,1559534400"; d="scan'208";a="4169836" Date: Mon, 12 Aug 2019 15:45:00 +0100 From: "Anthony PERARD" To: Roger Pau =?iso-8859-1?Q?Monn=E9?= CC: , Julien Grall , , Jordan Justen , Ard Biesheuvel , Laszlo Ersek Subject: Re: [edk2-devel] [PATCH v4 29/35] OvmfPkg/OvmfXen: Override PcdFSBClock to Xen vLAPIC timer frequency Message-ID: <20190812144500.GA1289@perard.uk.xensource.com> References: <20190729153944.24239-1-anthony.perard@citrix.com> <20190729153944.24239-30-anthony.perard@citrix.com> <20190807155451.pkld6zhcxljzx6d7@Air-de-Roger> <20190808132832.GU1242@perard.uk.xensource.com> <20190808134423.ybqg3qkpw5ucfzk4@Air-de-Roger> <20190808142641.GX1242@perard.uk.xensource.com> <20190808151815.nwup2kwu2qhm54ch@Air-de-Roger> MIME-Version: 1.0 In-Reply-To: <20190808151815.nwup2kwu2qhm54ch@Air-de-Roger> User-Agent: Mutt/1.12.1 (2019-06-15) Return-Path: anthony.perard@citrix.com Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 8bit On Thu, Aug 08, 2019 at 05:18:15PM +0200, Roger Pau Monné wrote: > On Thu, Aug 08, 2019 at 03:26:41PM +0100, Anthony PERARD wrote: > > So EDKII doesn't have that capability, FSBClock is a build time value > > and can't be changed at run time. But OVMF (on KVM or HVM) doesn't use > > that value at all, it uses the ACPI timer instead. > > But after your series both PVH and HVM will use the lapic timer > instead of the ACPI timer, and thus rely on the value of FSBClock? Short answer, Yes. Longuer answer, after the series is applied, there will be a new platform, "OvmfXen" which will be for both Xen PVH and Xen HVM, but the OVMF that we know (OvmfPkgX64 that xen.git builds) will still be capable of running on Xen HVM for a short while and will still use the ACPI timer. -- Anthony PERARD