public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Christian Borntraeger <borntraeger@linux.ibm.com>,
	Thomas Huth <thuth@redhat.com>,
	kvm@vger.kernel.org, Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Hildenbrand <david@redhat.com>,
	"Collin L. Walling" <walling@linux.ibm.com>,
	Jason J Herne <jjherne@linux.ibm.com>
Subject: Re: [PATCH] KVM: s390: vsie: Fix the initialization of the epoch extension (epdx) field
Date: Thu, 24 Nov 2022 11:24:33 +0100	[thread overview]
Message-ID: <ee3999a2-7ae6-e72c-0a47-0890972bbd23@linux.ibm.com> (raw)
In-Reply-To: <e7f84070-aeec-99d6-8ac0-cf90ad61ba88@linux.ibm.com>

On 11/23/22 10:41, Christian Borntraeger wrote:
> 
> 
> Am 23.11.22 um 10:08 schrieb Thomas Huth:
>> We recently experienced some weird huge time jumps in nested guests when
>> rebooting them in certain cases. After adding some debug code to the epoch
>> handling in vsie.c (thanks to David Hildenbrand for the idea!), it was
>> obvious that the "epdx" field (the multi-epoch extension) did not get set
>> to 0xff in case the "epoch" field was negative.
>> Seems like the code misses to copy the value from the epdx field from
>> the guest to the shadow control block. By doing so, the weird time
>> jumps are gone in our scenarios.
>>
>> Link: https://bugzilla.redhat.com/show_bug.cgi?id=2140899
>> Fixes: 8fa1696ea781 ("KVM: s390: Multiple Epoch Facility support")
> 
> We might want to add cc stable, just in case.

I'm pushing this to devel for the CI with the following additions:

Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
Cc: stable@vger.kernel.org # 4.19+

> 
> Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com>
> 
> 
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>>    arch/s390/kvm/vsie.c | 4 +++-
>>    1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/s390/kvm/vsie.c b/arch/s390/kvm/vsie.c
>> index 94138f8f0c1c..ace2541ababd 100644
>> --- a/arch/s390/kvm/vsie.c
>> +++ b/arch/s390/kvm/vsie.c
>> @@ -546,8 +546,10 @@ static int shadow_scb(struct kvm_vcpu *vcpu, struct vsie_page *vsie_page)
>>    	if (test_kvm_cpu_feat(vcpu->kvm, KVM_S390_VM_CPU_FEAT_CEI))
>>    		scb_s->eca |= scb_o->eca & ECA_CEI;
>>    	/* Epoch Extension */
>> -	if (test_kvm_facility(vcpu->kvm, 139))
>> +	if (test_kvm_facility(vcpu->kvm, 139)) {
>>    		scb_s->ecd |= scb_o->ecd & ECD_MEF;
>> +		scb_s->epdx = scb_o->epdx;
>> +	}
>>    
>>    	/* etoken */
>>    	if (test_kvm_facility(vcpu->kvm, 156))


  reply	other threads:[~2022-11-24 10:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23  9:08 [PATCH] KVM: s390: vsie: Fix the initialization of the epoch extension (epdx) field Thomas Huth
2022-11-23  9:14 ` David Hildenbrand
2022-11-23  9:38 ` Claudio Imbrenda
2022-11-23  9:41 ` Christian Borntraeger
2022-11-24 10:24   ` Janosch Frank [this message]
2022-11-24 10:27 ` Janosch Frank
2022-11-24 10:46   ` Thomas Huth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ee3999a2-7ae6-e72c-0a47-0890972bbd23@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=jjherne@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=thuth@redhat.com \
    --cc=walling@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox