On 11/21/19 3:17 PM, Cornelia Huck wrote:
> On Thu, 21 Nov 2019 15:04:31 +0100
> Janosch Frank wrote:
>
>> On 11/21/19 2:50 PM, Cornelia Huck wrote:
>>> On Wed, 20 Nov 2019 06:43:26 -0500
>>> Janosch Frank wrote:
>>
>>>
run_on_cpu(cs, s390_do_cpu_load_normal,
On Thu, 21 Nov 2019 15:04:31 +0100
Janosch Frank wrote:
> On 11/21/19 2:50 PM, Cornelia Huck wrote:
> > On Wed, 20 Nov 2019 06:43:26 -0500
> > Janosch Frank wrote:
>
> >
> >> run_on_cpu(cs, s390_do_cpu_load_normal, RUN_ON_CPU_NULL);
> >> break;
> >> case
On 11/21/19 2:50 PM, Cornelia Huck wrote:
> On Wed, 20 Nov 2019 06:43:26 -0500
> Janosch Frank wrote:
>
>> run_on_cpu(cs, s390_do_cpu_load_normal, RUN_ON_CPU_NULL);
>> break;
>> case S390_RESET_LOAD_NORMAL: /* Subcode 1*/
>
> missing blank before */ (introduced in a
On 11/21/19 2:50 PM, Cornelia Huck wrote:
> On Wed, 20 Nov 2019 06:43:26 -0500
> Janosch Frank wrote:
>
>> Now that we know the protection state off the cpus, we can start
>> handling all diag 308 subcodes in the protected state.
>
> "As we now have access to the protection state of the cpus,
On Wed, 20 Nov 2019 06:43:26 -0500
Janosch Frank wrote:
> Now that we know the protection state off the cpus, we can start
> handling all diag 308 subcodes in the protected state.
"As we now have access to the protection state of the cpus, we can
implement special handling of diag 308 subcodes
Now that we know the protection state off the cpus, we can start
handling all diag 308 subcodes in the protected state.
For subcodes 0 and 1 we need to unshare all pages before continuing,
so the guest doesn't accidently expose data when dumping.
For subcode 3/4 we tear down the protected VM and
