public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH RFC 2/2] KVM: s390: vsie: store guest addresses of satellite blocks in vsie_page
Date: Tue, 06 Mar 2018 13:16:19 +0000	[thread overview]
Message-ID: <1ba0d3ff-2ab1-447c-ac5f-4cad595c2e2e@redhat.com> (raw)
In-Reply-To: <ca50248c-944b-e5de-4633-b5cea593ccd6@de.ibm.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]

On 06.03.2018 14:14, Christian Borntraeger wrote:
> 
> 
> On 03/06/2018 02:01 PM, David Hildenbrand wrote:
>> On 06.03.2018 12:53, Christian Borntraeger wrote:
>>>
>>>
>>> On 03/06/2018 12:38 PM, Christian Borntraeger wrote:
>>>> On 03/06/2018 12:32 PM, Christian Borntraeger wrote:
>>>>> David, 
>>>>>
>>>>> this seems to have broken VSIE f�r guests with >64vcpus as we only pin
>>>>> the first page of the SCA. Starting guest3 with 240 vcpu triggers
>>>>> quickly guest2 crashes. Can you have a look?
>>>>>
>>>>
>>>> Hmm, or maybe it was always broken and we never supported pinning of
>>>> ESCA properly?
>>>
>>> 4.15.0 is also broken, must be an earlier change.
>>>
>>
>> Maybe something as simple as this:
>>
>> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
>> index 77d7818130db..321bfbc67d3d 100644
>> --- a/arch/s390/kvm/kvm-s390.c
>> +++ b/arch/s390/kvm/kvm-s390.c
>> @@ -2146,6 +2146,7 @@ static void sca_add_vcpu(struct kvm_vcpu *vcpu)
>>                 /* we still need the basic sca for the ipte control */
>>                 vcpu->arch.sie_block->scaoh = (__u32)(((__u64)sca) >> 32);
>>                 vcpu->arch.sie_block->scaol = (__u32)(__u64)sca;
>> +               return;
>>         }
>>         read_lock(&vcpu->kvm->arch.sca_lock);
>>         if (vcpu->kvm->arch.use_esca) {
>>
>>
> 
> 
> Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
> 
> can you spin a patch with proper Fixes tags?
> 

Sure, thanks for reporting!

-- 

Thanks,

David / dhildenb

       reply	other threads:[~2018-03-06 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ca50248c-944b-e5de-4633-b5cea593ccd6@de.ibm.com>
2018-03-06 13:16 ` David Hildenbrand [this message]
2018-01-16 17:15 [PATCH RFC 0/2] KVM: s390: vsie: protect from VCPUS modifying the SCB David Hildenbrand
2018-01-16 17:15 ` [PATCH RFC 2/2] KVM: s390: vsie: store guest addresses of satellite blocks in vsie_page David Hildenbrand
2018-01-23 11:18   ` Christian Borntraeger
2018-01-23 12:29   ` Cornelia Huck

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=1ba0d3ff-2ab1-447c-ac5f-4cad595c2e2e@redhat.com \
    --to=david@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    /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