On Thu, 8 Feb 2018 18:02:07 +0100
Viktor Mihajlovski wrote:
> On 08.02.2018 17:22, Luiz Capitulino wrote:
> > On Thu, 8 Feb 2018 16:52:28 +0100
> > Viktor Mihajlovski wrote:
> >
> >> diff --git a/qapi-schema.json b/qapi-schema.json
>
On 08.02.2018 17:22, Luiz Capitulino wrote:
> On Thu, 8 Feb 2018 16:52:28 +0100
> Viktor Mihajlovski wrote:
>
>> diff --git a/qapi-schema.json b/qapi-schema.json
>> index 12c7dc8..0b36860 100644
>> --- a/qapi-schema.json
>> +++ b/qapi-schema.json
>> @@ -607,7 +607,27
On Thu, 8 Feb 2018 16:52:28 +0100
Viktor Mihajlovski wrote:
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 12c7dc8..0b36860 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -607,7 +607,27 @@
> ##
> { 'struct': 'CpuInfo2',
>'data':
On 08.02.2018 16:30, Luiz Capitulino wrote:
> On Thu, 8 Feb 2018 16:21:26 +0100
> Cornelia Huck wrote:
>
>> On Thu, 8 Feb 2018 09:09:04 -0500
>> Luiz Capitulino wrote:
>>
>>> On Thu, 8 Feb 2018 10:48:08 +0100
>>> Viktor Mihajlovski
On Thu, 8 Feb 2018 16:21:26 +0100
Cornelia Huck wrote:
> On Thu, 8 Feb 2018 09:09:04 -0500
> Luiz Capitulino wrote:
>
> > On Thu, 8 Feb 2018 10:48:08 +0100
> > Viktor Mihajlovski wrote:
> >
> > > Presently s390x is
On 08.02.2018 16:19, Eric Blake wrote:
>
> Missing a documentation line that mentions when the enum grew. Also, has
> a conflict with this other proposed addition, which demonstrates what
> the documentation should look like (should be easy to resolve, though):
>
On 02/08/2018 04:37 AM, Cornelia Huck wrote:
@@ -373,7 +373,7 @@ static void s390_machine_reset(void)
/* all cpus are stopped - configure and start the ipl cpu only */
s390_ipl_prepare_cpu(ipl_cpu);
-s390_cpu_set_state(CPU_STATE_OPERATING, ipl_cpu);
+
On Thu, 8 Feb 2018 09:09:04 -0500
Luiz Capitulino wrote:
> On Thu, 8 Feb 2018 10:48:08 +0100
> Viktor Mihajlovski wrote:
>
> > Presently s390x is the only architecture not exposing specific
> > CPU information via QMP query-cpus. Upstream
On 02/08/2018 03:48 AM, Viktor Mihajlovski wrote:
Presently s390x is the only architecture not exposing specific
CPU information via QMP query-cpus. Upstream discussion has shown
that it could make sense to report the architecture specific CPU
state, e.g. to detect that a CPU has been stopped.
On Thu, 8 Feb 2018 10:48:08 +0100
Viktor Mihajlovski wrote:
> Presently s390x is the only architecture not exposing specific
> CPU information via QMP query-cpus. Upstream discussion has shown
> that it could make sense to report the architecture specific CPU
>
On Thu, 8 Feb 2018 11:24:48 +0100
Christian Borntraeger wrote:
> On 02/08/2018 11:16 AM, Cornelia Huck wrote:
> > On Thu, 8 Feb 2018 10:48:08 +0100
> > Viktor Mihajlovski wrote:
> >> diff --git a/hw/s390x/s390-virtio-ccw.c
On 02/08/2018 11:16 AM, Cornelia Huck wrote:
> On Thu, 8 Feb 2018 10:48:08 +0100
> Viktor Mihajlovski wrote:
>
> [added some cc:s]
>
>> Presently s390x is the only architecture not exposing specific
>> CPU information via QMP query-cpus. Upstream discussion has
On Thu, 8 Feb 2018 10:48:08 +0100
Viktor Mihajlovski wrote:
[added some cc:s]
> Presently s390x is the only architecture not exposing specific
> CPU information via QMP query-cpus. Upstream discussion has shown
> that it could make sense to report the architecture
Presently s390x is the only architecture not exposing specific
CPU information via QMP query-cpus. Upstream discussion has shown
that it could make sense to report the architecture specific CPU
state, e.g. to detect that a CPU has been stopped.
With this change the output of query-cpus will look
14 matches
Mail list logo