From: Janosch Frank <frankja@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>, kvm@vger.kernel.org
Cc: thuth@redhat.com, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH 1/2] s390x: smp: Use full PSW to bringup new cpu
Date: Wed, 11 Dec 2019 13:34:39 +0100 [thread overview]
Message-ID: <7391e55e-7be5-c69b-a1e5-5e1ddadbc06c@linux.ibm.com> (raw)
In-Reply-To: <6433a418-e42f-0cf6-9cd4-bbe9912b901d@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1671 bytes --]
On 12/11/19 1:31 PM, David Hildenbrand wrote:
> On 11.12.19 12:59, Janosch Frank wrote:
>> Up to now we ignored the psw mask and only used the psw address when
>> bringing up a new cpu. For DAT we need to also load the mask, so let's
>> do that.
>>
>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>> ---
>> lib/s390x/smp.c | 2 ++
>> s390x/cstart64.S | 2 +-
>> 2 files changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/lib/s390x/smp.c b/lib/s390x/smp.c
>> index f57f420..e17751a 100644
>> --- a/lib/s390x/smp.c
>> +++ b/lib/s390x/smp.c
>> @@ -185,6 +185,8 @@ int smp_cpu_setup(uint16_t addr, struct psw psw)
>> cpu->stack = (uint64_t *)alloc_pages(2);
>>
>> /* Start without DAT and any other mask bits. */
>> + cpu->lowcore->sw_int_psw.mask = psw.mask;
>> + cpu->lowcore->sw_int_psw.addr = psw.addr;
>> cpu->lowcore->sw_int_grs[14] = psw.addr;
>
> Not looking at the code (sorry :D ), do we still need this then? (you
> drop the br bewlo)
r14 is the return address, saving/initialising it doesn't sound like a
bad idea to me. If we ever have stack traces, it might show up, or won't it?
>
>> cpu->lowcore->sw_int_grs[15] = (uint64_t)cpu->stack + (PAGE_SIZE * 4);
>> lc->restart_new_psw.mask = 0x0000000180000000UL;
>> diff --git a/s390x/cstart64.S b/s390x/cstart64.S
>> index 86dd4c4..e6a6bdb 100644
>> --- a/s390x/cstart64.S
>> +++ b/s390x/cstart64.S
>> @@ -159,7 +159,7 @@ smp_cpu_setup_state:
>> xgr %r1, %r1
>> lmg %r0, %r15, GEN_LC_SW_INT_GRS
>> lctlg %c0, %c0, GEN_LC_SW_INT_CRS
>> - br %r14
>> + lpswe GEN_LC_SW_INT_PSW
>>
>> pgm_int:
>> SAVE_REGS
>>
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-11 12:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 11:59 [kvm-unit-tests PATCH 0/2] s390x: smp: Improve setup of additional cpus Janosch Frank
2019-12-11 11:59 ` [kvm-unit-tests PATCH 1/2] s390x: smp: Use full PSW to bringup new cpu Janosch Frank
2019-12-11 12:31 ` David Hildenbrand
2019-12-11 12:34 ` Janosch Frank [this message]
2019-12-11 12:54 ` David Hildenbrand
2019-12-12 14:16 ` David Hildenbrand
2019-12-11 11:59 ` [kvm-unit-tests PATCH 2/2] s390x: smp: Setup CRs from cpu 0 Janosch Frank
2019-12-11 12:32 ` David Hildenbrand
2019-12-11 12:37 ` Janosch Frank
2019-12-11 12:54 ` David Hildenbrand
2019-12-11 13:08 ` Janosch Frank
2019-12-11 13:14 ` David Hildenbrand
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=7391e55e-7be5-c69b-a1e5-5e1ddadbc06c@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=david@redhat.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