From: David Hildenbrand <david@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: thuth@redhat.com, borntraeger@de.ibm.com,
linux-s390@vger.kernel.org, cohuck@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 3/7] s390x: Add cpu id to interrupt error prints
Date: Thu, 16 Jan 2020 14:19:01 +0100 [thread overview]
Message-ID: <7308d55c-eaa8-3b43-12b2-86af7641514a@redhat.com> (raw)
In-Reply-To: <95c0a6af-7334-1825-226e-5973a639035a@linux.ibm.com>
On 16.01.20 14:04, Janosch Frank wrote:
> On 1/16/20 1:17 PM, David Hildenbrand wrote:
>> On 16.01.20 13:05, Janosch Frank wrote:
>>> It's good to know which cpu broke the test.
>>>
>>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>>> ---
>>> lib/s390x/interrupt.c | 20 ++++++++++----------
>>> 1 file changed, 10 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/lib/s390x/interrupt.c b/lib/s390x/interrupt.c
>>> index 05f30be..773752a 100644
>>> --- a/lib/s390x/interrupt.c
>>> +++ b/lib/s390x/interrupt.c
>>> @@ -107,8 +107,8 @@ static void fixup_pgm_int(void)
>>> void handle_pgm_int(void)
>>> {
>>> if (!pgm_int_expected)
>>> - report_abort("Unexpected program interrupt: %d at %#lx, ilen %d\n",
>>> - lc->pgm_int_code, lc->pgm_old_psw.addr,
>>> + report_abort("Unexpected program interrupt: %d on cpu %d at %#lx, ilen %d\n",
>>> + lc->pgm_int_code, stap(), lc->pgm_old_psw.addr,
>>> lc->pgm_int_id);
>>
>> nit: "cpu: %d"
>>
>>>
>>> pgm_int_expected = false;
>>> @@ -119,8 +119,8 @@ void handle_ext_int(void)
>>> {
>>> if (!ext_int_expected &&
>>> lc->ext_int_code != EXT_IRQ_SERVICE_SIG) {
>>> - report_abort("Unexpected external call interrupt (code %#x): at %#lx",
>>> - lc->ext_int_code, lc->ext_old_psw.addr);
>>> + report_abort("Unexpected external call interrupt (code %#x): on cpu %d at %#lx",
>>> + stap(), lc->ext_int_code, lc->ext_old_psw.addr);
>>
>> nit: "(code %#x) on cpu: %d" ...
>
> So, should I move the old : or add a second one?
No strong feelings, whatever you prefer. (you can also keep it
unchanged, it's just a test error output after all)
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-01-16 13:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 12:05 [kvm-unit-tests PATCH v2 0/7] s390x: smp: Improve smp code and reset checks Janosch Frank
2020-01-16 12:05 ` [kvm-unit-tests PATCH v2 1/7] s390x: smp: Cleanup smp.c Janosch Frank
2020-01-16 12:13 ` David Hildenbrand
2020-01-16 13:01 ` Janosch Frank
2020-01-16 12:05 ` [kvm-unit-tests PATCH v2 2/7] s390x: smp: Only use smp_cpu_setup once Janosch Frank
2020-01-16 12:18 ` David Hildenbrand
2020-01-16 13:01 ` Janosch Frank
2020-01-16 12:05 ` [kvm-unit-tests PATCH v2 3/7] s390x: Add cpu id to interrupt error prints Janosch Frank
2020-01-16 12:17 ` David Hildenbrand
2020-01-16 13:04 ` Janosch Frank
2020-01-16 13:19 ` David Hildenbrand [this message]
2020-01-16 13:59 ` Cornelia Huck
2020-01-16 14:11 ` Janosch Frank
2020-01-16 12:05 ` [kvm-unit-tests PATCH v2 4/7] s390x: smp: Rework cpu start and active tracking Janosch Frank
2020-01-16 14:14 ` Cornelia Huck
2020-01-16 14:44 ` Janosch Frank
2020-01-16 15:05 ` Cornelia Huck
2020-01-16 12:05 ` [kvm-unit-tests PATCH v2 5/7] s390x: smp: Wait for cpu setup to finish Janosch Frank
2020-01-16 12:19 ` David Hildenbrand
2020-01-16 12:05 ` [kvm-unit-tests PATCH v2 6/7] s390x: smp: Test all CRs on initial reset Janosch Frank
2020-01-16 12:24 ` David Hildenbrand
2020-01-16 13:07 ` Janosch Frank
2020-01-16 13:18 ` David Hildenbrand
2020-01-16 12:05 ` [kvm-unit-tests PATCH v2 7/7] s390x: smp: Dirty fpc before initial reset test Janosch Frank
2020-01-17 10:20 ` David Hildenbrand
2020-01-17 10:29 ` Thomas Huth
2020-01-17 10:41 ` 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=7308d55c-eaa8-3b43-12b2-86af7641514a@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=frankja@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.