On Wed, 6 Dec 2017 10:15:51 +0100
Pierre Morel wrote:
> On 05/12/2017 16:01, Tony Krowiak wrote:
> > On 12/05/2017 09:04 AM, Cornelia Huck wrote:
> >> On Tue, 5 Dec 2017 08:52:57 +0100
> >> Harald Freudenberger wrote:
> >>
> >>> On
On Wed, 6 Dec 2017 10:15:51 +0100
Pierre Morel wrote:
> On 05/12/2017 16:01, Tony Krowiak wrote:
> > On 12/05/2017 09:04 AM, Cornelia Huck wrote:
> >> On Tue, 5 Dec 2017 08:52:57 +0100
> >> Harald Freudenberger wrote:
> >>
> >>> On 12/02/2017 02:30 AM, Tony Krowiak wrote:
> I agree
On 05/12/2017 16:01, Tony Krowiak wrote:
On 12/05/2017 09:04 AM, Cornelia Huck wrote:
On Tue, 5 Dec 2017 08:52:57 +0100
Harald Freudenberger wrote:
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
I agree with your suggestion that defining a new CPU model feature
is
On 05/12/2017 16:01, Tony Krowiak wrote:
On 12/05/2017 09:04 AM, Cornelia Huck wrote:
On Tue, 5 Dec 2017 08:52:57 +0100
Harald Freudenberger wrote:
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
I agree with your suggestion that defining a new CPU model feature
is probably
the best way to
On 12/05/2017 09:23 AM, Pierre Morel wrote:
On 05/12/2017 15:04, Cornelia Huck wrote:
On Tue, 5 Dec 2017 08:52:57 +0100
Harald Freudenberger wrote:
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
I agree with your suggestion that defining a new CPU model feature
is
On 12/05/2017 09:23 AM, Pierre Morel wrote:
On 05/12/2017 15:04, Cornelia Huck wrote:
On Tue, 5 Dec 2017 08:52:57 +0100
Harald Freudenberger wrote:
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
I agree with your suggestion that defining a new CPU model feature
is probably
the best way to
On 12/05/2017 09:04 AM, Cornelia Huck wrote:
On Tue, 5 Dec 2017 08:52:57 +0100
Harald Freudenberger wrote:
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
I agree with your suggestion that defining a new CPU model feature is probably
the best way to resolve this issue.
On 12/05/2017 09:04 AM, Cornelia Huck wrote:
On Tue, 5 Dec 2017 08:52:57 +0100
Harald Freudenberger wrote:
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
I agree with your suggestion that defining a new CPU model feature is probably
the best way to resolve this issue. The question is, should we
On 05/12/2017 15:30, Cornelia Huck wrote:
On Tue, 5 Dec 2017 15:23:50 +0100
Pierre Morel wrote:
On 05/12/2017 15:04, Cornelia Huck wrote:
On Tue, 5 Dec 2017 08:52:57 +0100
Harald Freudenberger wrote:
On 12/02/2017 02:30 AM, Tony
On 05/12/2017 15:30, Cornelia Huck wrote:
On Tue, 5 Dec 2017 15:23:50 +0100
Pierre Morel wrote:
On 05/12/2017 15:04, Cornelia Huck wrote:
On Tue, 5 Dec 2017 08:52:57 +0100
Harald Freudenberger wrote:
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
I agree with your suggestion that
On Tue, 5 Dec 2017 15:23:50 +0100
Pierre Morel wrote:
> On 05/12/2017 15:04, Cornelia Huck wrote:
> > On Tue, 5 Dec 2017 08:52:57 +0100
> > Harald Freudenberger wrote:
> >
> >> On 12/02/2017 02:30 AM, Tony Krowiak wrote:
> >
> >>> I
On Tue, 5 Dec 2017 15:23:50 +0100
Pierre Morel wrote:
> On 05/12/2017 15:04, Cornelia Huck wrote:
> > On Tue, 5 Dec 2017 08:52:57 +0100
> > Harald Freudenberger wrote:
> >
> >> On 12/02/2017 02:30 AM, Tony Krowiak wrote:
> >
> >>> I agree with your suggestion that defining a new CPU
On 05/12/2017 15:04, Cornelia Huck wrote:
On Tue, 5 Dec 2017 08:52:57 +0100
Harald Freudenberger wrote:
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
I agree with your suggestion that defining a new CPU model feature is probably
the best way to resolve this issue.
On 05/12/2017 15:04, Cornelia Huck wrote:
On Tue, 5 Dec 2017 08:52:57 +0100
Harald Freudenberger wrote:
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
I agree with your suggestion that defining a new CPU model feature is probably
the best way to resolve this issue. The question is, should we
On 12/05/2017 02:52 AM, Harald Freudenberger wrote:
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
On 11/03/2017 04:47 AM, Christian Borntraeger wrote:
On 11/02/2017 07:49 PM, Tony Krowiak wrote:
On 11/02/2017 11:53 AM, Christian Borntraeger wrote:
On 11/02/2017 04:36 PM, Tony Krowiak wrote:
On 12/05/2017 02:52 AM, Harald Freudenberger wrote:
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
On 11/03/2017 04:47 AM, Christian Borntraeger wrote:
On 11/02/2017 07:49 PM, Tony Krowiak wrote:
On 11/02/2017 11:53 AM, Christian Borntraeger wrote:
On 11/02/2017 04:36 PM, Tony Krowiak wrote:
On Tue, 5 Dec 2017 08:52:57 +0100
Harald Freudenberger wrote:
> On 12/02/2017 02:30 AM, Tony Krowiak wrote:
> > I agree with your suggestion that defining a new CPU model feature is
> > probably
> > the best way to resolve this issue. The question is, should we
On Tue, 5 Dec 2017 08:52:57 +0100
Harald Freudenberger wrote:
> On 12/02/2017 02:30 AM, Tony Krowiak wrote:
> > I agree with your suggestion that defining a new CPU model feature is
> > probably
> > the best way to resolve this issue. The question is, should we define a
> > single
> > feature
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
> On 11/03/2017 04:47 AM, Christian Borntraeger wrote:
>>
>> On 11/02/2017 07:49 PM, Tony Krowiak wrote:
>>> On 11/02/2017 11:53 AM, Christian Borntraeger wrote:
On 11/02/2017 04:36 PM, Tony Krowiak wrote:
> On 11/02/2017 08:08 AM, Christian
On 12/02/2017 02:30 AM, Tony Krowiak wrote:
> On 11/03/2017 04:47 AM, Christian Borntraeger wrote:
>>
>> On 11/02/2017 07:49 PM, Tony Krowiak wrote:
>>> On 11/02/2017 11:53 AM, Christian Borntraeger wrote:
On 11/02/2017 04:36 PM, Tony Krowiak wrote:
> On 11/02/2017 08:08 AM, Christian
On 11/03/2017 04:47 AM, Christian Borntraeger wrote:
On 11/02/2017 07:49 PM, Tony Krowiak wrote:
On 11/02/2017 11:53 AM, Christian Borntraeger wrote:
On 11/02/2017 04:36 PM, Tony Krowiak wrote:
On 11/02/2017 08:08 AM, Christian Borntraeger wrote:
On 10/16/2017 11:25 AM, Martin Schwidefsky
On 11/03/2017 04:47 AM, Christian Borntraeger wrote:
On 11/02/2017 07:49 PM, Tony Krowiak wrote:
On 11/02/2017 11:53 AM, Christian Borntraeger wrote:
On 11/02/2017 04:36 PM, Tony Krowiak wrote:
On 11/02/2017 08:08 AM, Christian Borntraeger wrote:
On 10/16/2017 11:25 AM, Martin Schwidefsky
On 11/03/2017 09:14 AM, Harald Freudenberger wrote:
> I talked with the firmware guys about this.
> The answer is that the AP 3 instructions (NQAP, DQAP, PQAP) are always
> available.
That is true for basic mode and LPAR, but certainly not for z/VM or KVM guests.
> Tony is right with the
On 11/03/2017 09:14 AM, Harald Freudenberger wrote:
> I talked with the firmware guys about this.
> The answer is that the AP 3 instructions (NQAP, DQAP, PQAP) are always
> available.
That is true for basic mode and LPAR, but certainly not for z/VM or KVM guests.
> Tony is right with the
On 11/02/2017 07:49 PM, Tony Krowiak wrote:
> On 11/02/2017 11:53 AM, Christian Borntraeger wrote:
>>
>> On 11/02/2017 04:36 PM, Tony Krowiak wrote:
>>> On 11/02/2017 08:08 AM, Christian Borntraeger wrote:
On 10/16/2017 11:25 AM, Martin Schwidefsky wrote:
> On Fri, 13 Oct 2017 13:39:04
On 11/02/2017 07:49 PM, Tony Krowiak wrote:
> On 11/02/2017 11:53 AM, Christian Borntraeger wrote:
>>
>> On 11/02/2017 04:36 PM, Tony Krowiak wrote:
>>> On 11/02/2017 08:08 AM, Christian Borntraeger wrote:
On 10/16/2017 11:25 AM, Martin Schwidefsky wrote:
> On Fri, 13 Oct 2017 13:39:04
On 11/02/2017 11:53 AM, Christian Borntraeger wrote:
On 11/02/2017 04:36 PM, Tony Krowiak wrote:
On 11/02/2017 08:08 AM, Christian Borntraeger wrote:
On 10/16/2017 11:25 AM, Martin Schwidefsky wrote:
On Fri, 13 Oct 2017 13:39:04 -0400
Tony Krowiak wrote:
Sets
On 11/02/2017 11:53 AM, Christian Borntraeger wrote:
On 11/02/2017 04:36 PM, Tony Krowiak wrote:
On 11/02/2017 08:08 AM, Christian Borntraeger wrote:
On 10/16/2017 11:25 AM, Martin Schwidefsky wrote:
On Fri, 13 Oct 2017 13:39:04 -0400
Tony Krowiak wrote:
Sets up the following facilities
On 11/02/2017 04:36 PM, Tony Krowiak wrote:
> On 11/02/2017 08:08 AM, Christian Borntraeger wrote:
>>
>> On 10/16/2017 11:25 AM, Martin Schwidefsky wrote:
>>> On Fri, 13 Oct 2017 13:39:04 -0400
>>> Tony Krowiak wrote:
>>>
Sets up the following facilities bits
On 11/02/2017 04:36 PM, Tony Krowiak wrote:
> On 11/02/2017 08:08 AM, Christian Borntraeger wrote:
>>
>> On 10/16/2017 11:25 AM, Martin Schwidefsky wrote:
>>> On Fri, 13 Oct 2017 13:39:04 -0400
>>> Tony Krowiak wrote:
>>>
Sets up the following facilities bits to enable the specified AP
On 11/02/2017 01:08 PM, Christian Borntraeger wrote:
>
>
> On 10/16/2017 11:25 AM, Martin Schwidefsky wrote:
>> On Fri, 13 Oct 2017 13:39:04 -0400
>> Tony Krowiak wrote:
>>
>>> Sets up the following facilities bits to enable the specified AP
>>> facilities for the
On 11/02/2017 01:08 PM, Christian Borntraeger wrote:
>
>
> On 10/16/2017 11:25 AM, Martin Schwidefsky wrote:
>> On Fri, 13 Oct 2017 13:39:04 -0400
>> Tony Krowiak wrote:
>>
>>> Sets up the following facilities bits to enable the specified AP
>>> facilities for the guest VM:
>>> *
On 10/16/2017 11:25 AM, Martin Schwidefsky wrote:
> On Fri, 13 Oct 2017 13:39:04 -0400
> Tony Krowiak wrote:
>
>> Sets up the following facilities bits to enable the specified AP
>> facilities for the guest VM:
>> * STFLE.12: Enables the AP Query Configuration
On 10/16/2017 11:25 AM, Martin Schwidefsky wrote:
> On Fri, 13 Oct 2017 13:39:04 -0400
> Tony Krowiak wrote:
>
>> Sets up the following facilities bits to enable the specified AP
>> facilities for the guest VM:
>> * STFLE.12: Enables the AP Query Configuration Information
>>
On Fri, 13 Oct 2017 13:39:04 -0400
Tony Krowiak wrote:
> Sets up the following facilities bits to enable the specified AP
> facilities for the guest VM:
> * STFLE.12: Enables the AP Query Configuration Information
> facility. The AP bus running in
On Fri, 13 Oct 2017 13:39:04 -0400
Tony Krowiak wrote:
> Sets up the following facilities bits to enable the specified AP
> facilities for the guest VM:
> * STFLE.12: Enables the AP Query Configuration Information
> facility. The AP bus running in the guest uses
>
Sets up the following facilities bits to enable the specified AP
facilities for the guest VM:
* STFLE.12: Enables the AP Query Configuration Information
facility. The AP bus running in the guest uses
the information returned from this instruction
Sets up the following facilities bits to enable the specified AP
facilities for the guest VM:
* STFLE.12: Enables the AP Query Configuration Information
facility. The AP bus running in the guest uses
the information returned from this instruction
38 matches
Mail list logo