From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, linux-kernel@vger.kernel.org
Cc: frankja@linux.ibm.com, david@redhat.com, cohuck@redhat.com,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
stable@vger.kernel.org, Janosch Frank <frankja@de.ibm.com>
Subject: Re: [PATCH v5 2/3] s390/kvm: extend kvm_s390_shadow_fault to return entry pointer
Date: Fri, 5 Mar 2021 18:01:02 +0100 [thread overview]
Message-ID: <5b3af39c-d141-c51d-156a-a2ed0f9396ee@de.ibm.com> (raw)
In-Reply-To: <20210302174443.514363-3-imbrenda@linux.ibm.com>
On 02.03.21 18:44, Claudio Imbrenda wrote:
> Extend kvm_s390_shadow_fault to return the pointer to the valid leaf
> DAT table entry, or to the invalid entry.
>
> Also return some flags in the lower bits of the address:
> PEI_DAT_PROT: indicates that DAT protection applies because of the
> protection bit in the segment (or, if EDAT, region) tables.
> PEI_NOT_PTE: indicates that the address of the DAT table entry returned
> does not refer to a PTE, but to a segment or region table.
>
> Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Cc: stable@vger.kernel.org
> Reviewed-by: Janosch Frank <frankja@de.ibm.com>
> Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
next prev parent reply other threads:[~2021-03-05 17:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 17:44 [PATCH v5 0/3] s390/kvm: fix MVPG when in VSIE Claudio Imbrenda
2021-03-02 17:44 ` [PATCH v5 1/3] s390/kvm: split kvm_s390_logical_to_effective Claudio Imbrenda
2021-03-05 15:08 ` Christian Borntraeger
2021-03-02 17:44 ` [PATCH v5 2/3] s390/kvm: extend kvm_s390_shadow_fault to return entry pointer Claudio Imbrenda
2021-03-05 17:01 ` Christian Borntraeger [this message]
2021-03-02 17:44 ` [PATCH v5 3/3] s390/kvm: VSIE: correctly handle MVPG when in VSIE Claudio Imbrenda
2021-03-08 15:18 ` Christian Borntraeger
2021-03-08 15:19 ` [PATCH v5 0/3] s390/kvm: fix " Christian Borntraeger
2021-03-08 15:26 ` Janosch Frank
2021-03-08 15:30 ` Claudio Imbrenda
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=5b3af39c-d141-c51d-156a-a2ed0f9396ee@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@de.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).