From: David Hildenbrand <david@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: thuth@redhat.com, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH 2/2] s390x: smp: Setup CRs from cpu 0
Date: Wed, 11 Dec 2019 14:14:40 +0100 [thread overview]
Message-ID: <de8319a4-a1dd-3109-5ee5-aa6847494341@redhat.com> (raw)
In-Reply-To: <73296143-98cb-bb86-924d-400bcc027c34@linux.ibm.com>
On 11.12.19 14:08, Janosch Frank wrote:
> On 12/11/19 1:54 PM, David Hildenbrand wrote:
>> On 11.12.19 13:37, Janosch Frank wrote:
>>> On 12/11/19 1:32 PM, David Hildenbrand wrote:
>>>> On 11.12.19 12:59, Janosch Frank wrote:
>>>>> Grab the CRs (currently only 0, 1, 7, 13) from cpu 0, so we can
>>>>> bringup the new cpu in DAT mode or set other control options.
>>>>>
>>>>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>>>>> ---
>>>>> lib/s390x/smp.c | 5 ++++-
>>>>> s390x/cstart64.S | 2 +-
>>>>> 2 files changed, 5 insertions(+), 2 deletions(-)
>>>>>
>>>>> diff --git a/lib/s390x/smp.c b/lib/s390x/smp.c
>>>>> index e17751a..4dfe7c6 100644
>>>>> --- a/lib/s390x/smp.c
>>>>> +++ b/lib/s390x/smp.c
>>>>> @@ -191,7 +191,10 @@ int smp_cpu_setup(uint16_t addr, struct psw psw)
>>>>> cpu->lowcore->sw_int_grs[15] = (uint64_t)cpu->stack + (PAGE_SIZE * 4);
>>>>> lc->restart_new_psw.mask = 0x0000000180000000UL;
>>>>> lc->restart_new_psw.addr = (uint64_t)smp_cpu_setup_state;
>>>>> - lc->sw_int_crs[0] = 0x0000000000040000UL;
>>>>> + lc->sw_int_crs[0] = stctg(0);
>>>>> + lc->sw_int_crs[1] = stctg(1);
>>>>> + lc->sw_int_crs[7] = stctg(7);
>>>>> + lc->sw_int_crs[13] = stctg(13);
>>>>
>>>> Wouldn't it be better to also be able to specify the CRs explicitly here?
>>>>
>>>
>>> Yes, but currently there are no users for something like that and it
>>> would mean that we might need to add more code to support it.
>>>
>>> As I said in the cover letter, this is a good first step to allow DAT on
>>> additional cpus without any real setup needed in a test. Later we could
>>> add a function to specify the CRs explicitly.
>>>
>>
>> Can you clarify why we need this patch now (e.g., DAT)? This patch
>> sounds like it would make sense in the future only (it is easier to
>> review with future changes IMHO).
>>
>
> Some G1 UV calls need the home space and therefore I added this patch to
> my concurrency tests which are still in my queue. I thought these fixes
> might make sense anyway and could be flushed from my queue before the UV
> patches are ready.
Okay, so it needs e.g., CR13, but we only populate CR0 and CR1 right now
if I'm not wrong. IOW, let's send this with the other patches (or only
populate cr0/cr1 in this patch and add the other stuff on top later on).
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2019-12-11 13:14 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
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 [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=de8319a4-a1dd-3109-5ee5-aa6847494341@redhat.com \
--to=david@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox