On 10/09/19 12:23, Igor Mammedov wrote:
> On Tue, 8 Oct 2019 23:12:10 +0200
> Laszlo Ersek wrote:
>
>> On 10/08/19 17:06, Igor Mammedov wrote:
>>> On Tue, 8 Oct 2019 13:27:14 +0200
>>> Laszlo Ersek wrote:
>>>
MaxCpuCountInitialization() currently handles the following options:
On Tue, 8 Oct 2019 23:12:10 +0200
Laszlo Ersek wrote:
> On 10/08/19 17:06, Igor Mammedov wrote:
> > On Tue, 8 Oct 2019 13:27:14 +0200
> > Laszlo Ersek wrote:
> >
> >> MaxCpuCountInitialization() currently handles the following options:
> >>
> >> (1) QEMU does not report the boot CPU count.
>
On 10/08/19 17:06, Igor Mammedov wrote:
> On Tue, 8 Oct 2019 13:27:14 +0200
> Laszlo Ersek wrote:
>
>> MaxCpuCountInitialization() currently handles the following options:
>>
>> (1) QEMU does not report the boot CPU count.
>>
>> In this case, PlatformPei makes MpInitLib enumerate APs up to
On Tue, 8 Oct 2019 13:27:14 +0200
Laszlo Ersek wrote:
> MaxCpuCountInitialization() currently handles the following options:
>
> (1) QEMU does not report the boot CPU count.
>
> In this case, PlatformPei makes MpInitLib enumerate APs up to the
> default PcdCpuMaxLogicalProcessorNumber
MaxCpuCountInitialization() currently handles the following options:
(1) QEMU does not report the boot CPU count.
In this case, PlatformPei makes MpInitLib enumerate APs up to the
default PcdCpuMaxLogicalProcessorNumber value (64) minus 1, or until
the default
