From: Janosch Frank <frankja@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
david@redhat.com, thuth@redhat.com, cohuck@redhat.com
Subject: Re: [kvm-unit-tests PATCH 3/8] lib: s390x: Print addressing related exception information
Date: Fri, 13 Aug 2021 13:34:29 +0200 [thread overview]
Message-ID: <4c6682cc-f4b5-2a70-167c-00af4b333c2d@linux.ibm.com> (raw)
In-Reply-To: <20210813104017.6e669d72@p-imbrenda>
On 8/13/21 10:40 AM, Claudio Imbrenda wrote:
> On Fri, 13 Aug 2021 07:36:10 +0000
> Janosch Frank <frankja@linux.ibm.com> wrote:
>
>> Right now we only get told the kind of program exception as well as
>> the PSW at the point where it happened.
>>
>> For addressing exceptions the PSW is not always enough so let's print
>> the TEID which contains the failing address and flags that tell us
>> more about the kind of address exception.
>>
>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>> ---
>> lib/s390x/asm/arch_def.h | 4 +++
>> lib/s390x/interrupt.c | 72
>> ++++++++++++++++++++++++++++++++++++++++ 2 files changed, 76
>> insertions(+)
>>
>> diff --git a/lib/s390x/asm/arch_def.h b/lib/s390x/asm/arch_def.h
>> index 4ca02c1d..39c5ba99 100644
>> --- a/lib/s390x/asm/arch_def.h
>> +++ b/lib/s390x/asm/arch_def.h
>> @@ -41,6 +41,10 @@ struct psw {
>> uint64_t addr;
>> };
>>
>> +/* Let's ignore spaces we don't expect to use for now. */
>> +#define AS_PRIM 0
>> +#define AS_HOME 3
>> +
>> #define PSW_MASK_EXT 0x0100000000000000UL
>> #define PSW_MASK_IO 0x0200000000000000UL
>> #define PSW_MASK_DAT 0x0400000000000000UL
>> diff --git a/lib/s390x/interrupt.c b/lib/s390x/interrupt.c
>> index 01ded49d..1248bceb 100644
>> --- a/lib/s390x/interrupt.c
>> +++ b/lib/s390x/interrupt.c
>> @@ -12,6 +12,7 @@
>> #include <sclp.h>
>> #include <interrupt.h>
>> #include <sie.h>
>> +#include <asm/page.h>
>>
>> static bool pgm_int_expected;
>> static bool ext_int_expected;
>> @@ -126,6 +127,73 @@ static void fixup_pgm_int(struct stack_frame_int
>> *stack) /* suppressed/terminated/completed point already at the next
>> address */ }
>>
>> +static void decode_pgm_prot(uint64_t teid)
>
> it is actually more complicated than this.
I know it hurts to look at the spec :)
>
> if you don't want to add all the possibilities because they are
> unlikely and/or not relevant, maybe add a comment
Will do!
>
>> +{
>> + /* Low-address protection exception, 100 */
>> + if (test_bit_inv(56, &teid) && !test_bit_inv(60, &teid) &&
>> !test_bit_inv(61, &teid)) {
>> + printf("Type: LAP\n");
>> + return;
>> + }
>> +
>> + /* Instruction execution prevention, i.e. no-execute, 101 */
>> + if (test_bit_inv(56, &teid) && !test_bit_inv(60, &teid) &&
>> test_bit_inv(61, &teid)) {
>> + printf("Type: IEP\n");
>> + return;
>> + }
>> +
>> + /* Standard DAT exception, 001 */
>> + if (!test_bit_inv(56, &teid) && !test_bit_inv(60, &teid) &&
>> test_bit_inv(61, &teid)) {
>> + printf("Type: DAT\n");
>> + return;
>> + }
>> +}
>> +
>> +static void decode_teid(uint64_t teid)
>> +{
>> + int asce_id = lc->trans_exc_id & 3;
>> + bool dat = lc->pgm_old_psw.mask & PSW_MASK_DAT;
>> +
>> + printf("Memory exception information:\n");
>> + printf("TEID: %lx\n", teid);
>> + printf("DAT: %s\n", dat ? "on" : "off");
>> + printf("AS: %s\n", asce_id == AS_PRIM ? "Primary" : "Home");
>> +
>> + if (lc->pgm_int_code == PGM_INT_CODE_PROTECTION)
>> + decode_pgm_prot(teid);
>> +
>> + /*
>> + * If teid bit 61 is off for these two exception the reported
>> + * address is unpredictable.
>> + */
>> + if ((lc->pgm_int_code == PGM_INT_CODE_SECURE_STOR_ACCESS ||
>> + lc->pgm_int_code == PGM_INT_CODE_SECURE_STOR_VIOLATION)
>> &&
>> + !test_bit_inv(61, &teid)) {
>> + printf("Address: %lx, unpredictable\n ", teid &
>> PAGE_MASK);
>> + return;
>> + }
>> + printf("Address: %lx\n\n", teid & PAGE_MASK);
>> +}
>> +
>> +static void print_storage_exception_information(void)
>> +{
>> + switch (lc->pgm_int_code) {
>> + case PGM_INT_CODE_PROTECTION:
>> + case PGM_INT_CODE_PAGE_TRANSLATION:
>> + case PGM_INT_CODE_SEGMENT_TRANSLATION:
>> + case PGM_INT_CODE_ASCE_TYPE:
>> + case PGM_INT_CODE_REGION_FIRST_TRANS:
>> + case PGM_INT_CODE_REGION_SECOND_TRANS:
>> + case PGM_INT_CODE_REGION_THIRD_TRANS:
>> + case PGM_INT_CODE_SECURE_STOR_ACCESS:
>> + case PGM_INT_CODE_NON_SECURE_STOR_ACCESS:
>> + case PGM_INT_CODE_SECURE_STOR_VIOLATION:
>> + decode_teid(lc->trans_exc_id);
>> + break;
>> + default:
>> + return;
>> + }
>> +}
>> +
>> static void print_int_regs(struct stack_frame_int *stack)
>> {
>> printf("\n");
>> @@ -155,6 +223,10 @@ static void print_pgm_info(struct
>> stack_frame_int *stack) lc->pgm_int_code, stap(),
>> lc->pgm_old_psw.addr, lc->pgm_int_id); print_int_regs(stack);
>> dump_stack();
>> +
>> + /* Dump stack doesn't end with a \n so we add it here
>> instead */
>> + printf("\n");
>> + print_storage_exception_information();
>> report_summary();
>> abort();
>> }
>
next prev parent reply other threads:[~2021-08-13 11:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 7:36 [kvm-unit-tests PATCH 0/8] s390x: Cleanup and maintenance Janosch Frank
2021-08-13 7:36 ` [kvm-unit-tests PATCH 1/8] s390x: lib: Extend bitops Janosch Frank
2021-08-13 8:32 ` Claudio Imbrenda
2021-08-13 11:31 ` Janosch Frank
2021-08-18 8:20 ` Thomas Huth
2021-08-18 8:39 ` Janosch Frank
2021-08-18 8:57 ` Thomas Huth
2021-08-13 7:36 ` [kvm-unit-tests PATCH 2/8] lib: s390x: Add 0x3d, 0x3e and 0x3f PGM constants Janosch Frank
2021-08-13 8:20 ` Claudio Imbrenda
2021-08-13 7:36 ` [kvm-unit-tests PATCH 3/8] lib: s390x: Print addressing related exception information Janosch Frank
2021-08-13 8:40 ` Claudio Imbrenda
2021-08-13 11:34 ` Janosch Frank [this message]
2021-08-18 9:12 ` Thomas Huth
2021-08-18 9:29 ` Claudio Imbrenda
2021-08-18 9:53 ` Janosch Frank
2021-08-13 7:36 ` [kvm-unit-tests PATCH 4/8] lib: s390x: Start using bitops instead of magic constants Janosch Frank
2021-08-13 8:41 ` Claudio Imbrenda
2021-08-18 9:24 ` Thomas Huth
2021-08-13 7:36 ` [kvm-unit-tests PATCH 5/8] s390x: uv-host: Explain why we set up the home space and remove the space change Janosch Frank
2021-08-13 8:45 ` Claudio Imbrenda
2021-08-13 13:14 ` Janosch Frank
2021-08-13 7:36 ` [kvm-unit-tests PATCH 6/8] lib: s390x: Add PSW_MASK_64 Janosch Frank
2021-08-13 8:46 ` Claudio Imbrenda
2021-08-18 9:28 ` Thomas Huth
2021-08-13 7:36 ` [kvm-unit-tests PATCH 7/8] lib: s390x: Control register constant cleanup Janosch Frank
2021-08-13 8:49 ` Claudio Imbrenda
2021-08-13 9:09 ` Janosch Frank
2021-08-13 7:36 ` [kvm-unit-tests PATCH 8/8] lib: s390x: uv: Add rc 0x100 query error handling Janosch Frank
2021-08-13 8:50 ` Claudio Imbrenda
2021-08-18 9:30 ` Thomas Huth
2021-08-18 9:57 ` Janosch Frank
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=4c6682cc-f4b5-2a70-167c-00af4b333c2d@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=thuth@redhat.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