From mboxrd@z Thu Jan  1 00:00:00 1970
From: Janusz <januszmk6@gmail.com>
Subject: Re: [edk2] KVM: MTRR: fix memory type handling if MTRR is completely
 disabled
Date: Tue, 20 Oct 2015 19:27:24 +0200
Message-ID: <5626797C.2020108@gmail.com>
References: <55FBDB6D.4040207@gmail.com> <55FBE248.4010809@redhat.com>
 <55FC4E6F.8030104@gmail.com> <55FF7095.5060106@linux.intel.com>
 <BLU437-SMTP104744D03206E82EA10655C80460@phx.gbl>
 <55FF7C41.7070400@linux.intel.com> <560D3F31.5000703@gmail.com>
 <560D40C2.5080205@redhat.com> <560E96D8.9080007@gmail.com>
 <561DD2EC.5040800@linux.intel.com> <561E0655.8080508@gmail.com>
 <561E1121.7030502@linux.intel.com> <561E1329.5080109@linux.intel.com>
 <561E9A36.3080302@gmail.com> <561F2952.5060300@linux.intel.com>
 <561F4589.5050609@gmail.com> <561F4AAE.3060204@linux.intel.com>
 <561F4E92.3090403@gmail.com> <561F516D.7070504@linux.intel.com>
 <561FD1D8.3030605@redhat.com>
 <E92EE9817A31E24EB0585FDF735412F563254548@ORSMSX113.amr.corp.intel.com>
 <561FF492.90608@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"Justen, Jordan L" <jordan.l.justen@intel.com>,
	"edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>,
	Alex Williamson <alex.williamson@redhat.com>,
	Chen Fan <chen.fan.fnst@cn.fujitsu.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Wanpeng Li <wanpeng.li@hotmail.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	Xiao Guangrong <guangrong.xiao@linux.intel.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-lb0-f173.google.com ([209.85.217.173]:34496 "EHLO
	mail-lb0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750966AbbJTR11 (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 20 Oct 2015 13:27:27 -0400
Received: by lbbwb3 with SMTP id wb3so20660739lbb.1
        for <kvm@vger.kernel.org>; Tue, 20 Oct 2015 10:27:26 -0700 (PDT)
In-Reply-To: <561FF492.90608@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

W dniu 15.10.2015 o 20:46, Laszlo Ersek pisze:
> On 10/15/15 18:53, Kinney, Michael D wrote:
>> Laszlo,
>>
>> There is already a PCD for this timeout that is used by CpuMpPei.
>>
>> 	gUefiCpuPkgTokenSpaceGuid.PcdCpuApInitTimeOutInMicroSeconds
>>
>> I noticed that CpuDxe is using a hard coded AP timeout.  I think we should just use this same PCD for both the PEI and DXE CPU module and then set it for OVMF to the compatible value.
> Perfect, thank you!
>
> (I notice the default in the DEC file is 50000, which is half of what
> the DXE driver hardcodes.)
>
> Now we only need a recommended (or experimental) value for it, and an
> explanation why 100*1000 is no longer sufficient on KVM :)
>
> Thanks!
> Laszlo
>
>
>
Laszlo,

I saw that there is already some change in ovmf for MicroSecondDelay
https://github.com/tianocore/edk2/commit/1e410eadd80c328e66868263b3006a274ce81ae0
Is that a fix for it? Because I tried it and it still doesn't work for
me: https://bpaste.net/show/2514b51bf41f
I still get internal error