From: Janosch Frank <frankja@linux.vnet.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
David Hildenbrand <david@redhat.com>
Cc: KVM <kvm@vger.kernel.org>, Cornelia Huck <cohuck@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [PATCH] KVM: s390: force bp isolation for VSIE
Date: Wed, 14 Feb 2018 12:44:18 +0100 [thread overview]
Message-ID: <5ec41177-f405-0346-9489-9fd776552ba3@linux.vnet.ibm.com> (raw)
In-Reply-To: <c443d2c9-ddee-57bf-e192-4b586500e286@de.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 705 bytes --]
On 14.02.2018 12:05, Christian Borntraeger wrote:
>
>
> On 02/14/2018 11:37 AM, David Hildenbrand wrote:
>> On 14.02.2018 11:14, Christian Borntraeger wrote:
>>>
>>>
>>> On 02/14/2018 11:06 AM, David Hildenbrand wrote:
>>>> On 14.02.2018 09:34, Christian Borntraeger wrote:
>>>>> If the guest runs with bp isolation when doing a SIE instruction,
>>>>> we must also run the nested guest with bp isolation when emulating
>>>>> that SIE instruction.
This is done by activating BPBC in the lpar, which acts as an override
for lower level guests.
Reviewed-by: Janosch Frank <frankja@linux.vnet.ibm.com>
Maybe also add a short comment, that the fpf bit is a logical or in
shadow_scb?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2018-02-14 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 8:34 [PATCH] KVM: s390: force bp isolation for VSIE Christian Borntraeger
2018-02-14 10:06 ` David Hildenbrand
2018-02-14 10:14 ` Christian Borntraeger
2018-02-14 10:20 ` Christian Borntraeger
2018-02-14 10:37 ` David Hildenbrand
2018-02-14 11:05 ` Christian Borntraeger
2018-02-14 11:16 ` David Hildenbrand
2018-02-14 11:44 ` Janosch Frank [this message]
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=5ec41177-f405-0346-9489-9fd776552ba3@linux.vnet.ibm.com \
--to=frankja@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=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