(I've been dropped from the address list, not sure why)
On 10/22/19 19:17, Christophe de Dinechin wrote:
>
> Laszlo Ersek writes:
>
>> On 10/10/19 15:31, Laszlo Ersek wrote:
>>> 2nd round:
>>>
>>> On 10/09/19 15:22, Igor Mammedov wrote:
QEMU returns 0, in case of erro or invalid value in
Laszlo Ersek writes:
> On 10/10/19 15:31, Laszlo Ersek wrote:
>> 2nd round:
>>
>> On 10/09/19 15:22, Igor Mammedov wrote:
>>> QEMU returns 0, in case of erro or invalid value in 'Command field',
>>> make spec match reality, i.e.
>>
>> AHA! so this is exactly where you meant to list the
On 10/17/19 17:41, Igor Mammedov wrote:
> On Thu, 10 Oct 2019 14:33:19 +0200
> Laszlo Ersek wrote:
>
>> On 10/09/19 15:22, Igor Mammedov wrote:
>>> QEMU returns 0, in case of erro or invalid value in 'Command field',
>>> make spec match reality, i.e.
>>
>> Unfinished thought?
> yep, I'll fix
On Thu, 10 Oct 2019 14:33:19 +0200
Laszlo Ersek wrote:
> On 10/09/19 15:22, Igor Mammedov wrote:
> > QEMU returns 0, in case of erro or invalid value in 'Command field',
> > make spec match reality, i.e.
>
> Unfinished thought?
yep, I'll fix it up.
[...]
> > index ee219c8358..ac5903b2b1
2nd round:
On 10/09/19 15:22, Igor Mammedov wrote:
> QEMU returns 0, in case of erro or invalid value in 'Command field',
> make spec match reality, i.e.
AHA! so this is exactly where you meant to list the particular cases
when "command data" reads as 0:
- CPU >= max_cpus selected,
- CPU with
On 10/10/19 15:31, Laszlo Ersek wrote:
> 2nd round:
>
> On 10/09/19 15:22, Igor Mammedov wrote:
>> QEMU returns 0, in case of erro or invalid value in 'Command field',
>> make spec match reality, i.e.
>
> AHA! so this is exactly where you meant to list the particular cases
> when "command data"
On 10/09/19 15:22, Igor Mammedov wrote:
> QEMU returns 0, in case of erro or invalid value in 'Command field',
> make spec match reality, i.e.
Unfinished thought?
>
> Also fix returned value description in case 'Command field' == 0x0,
double space
> it's in not PXM but CPU selector value
