public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: Nina Schoetterl-Glausch <nsg@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	Ilya Leoshkevich <iii@linux.ibm.com>
Subject: Re: [kvm-unit-tests PATCH v3 3/3] s390x/spec_ex: Add test of EXECUTE with odd target address
Date: Mon, 20 Mar 2023 13:21:31 +0100	[thread overview]
Message-ID: <36e0a286-d3ee-7bbc-5b8c-e484fa75e672@linux.ibm.com> (raw)
In-Reply-To: <d9d18828-596f-cd92-887d-aa3c7cbb6e6f@redhat.com>

On 3/17/23 17:37, Thomas Huth wrote:
> On 17/03/2023 16.36, Claudio Imbrenda wrote:
>> On Fri, 17 Mar 2023 15:11:35 +0100
>> Thomas Huth <thuth@redhat.com> wrote:
>>
>>> On 17/03/2023 15.09, Thomas Huth wrote:
>>>> On 15/03/2023 16.54, Nina Schoetterl-Glausch wrote:
>>>>> The EXECUTE instruction executes the instruction at the given target
>>>>> address. This address must be halfword aligned, otherwise a
>>>>> specification exception occurs.
>>>>> Add a test for this.
>>>>>
>>>>> Signed-off-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
>>>>> ---
>>>>>     s390x/spec_ex.c | 25 +++++++++++++++++++++++++
>>>>>     1 file changed, 25 insertions(+)
>>>>>
>>>>> diff --git a/s390x/spec_ex.c b/s390x/spec_ex.c
>>>>> index 83b8c58e..5fa05dba 100644
>>>>> --- a/s390x/spec_ex.c
>>>>> +++ b/s390x/spec_ex.c
>>>>> @@ -177,6 +177,30 @@ static int short_psw_bit_12_is_0(void)
>>>>>         return 0;
>>>>>     }
>>>>> +static int odd_ex_target(void)
>>>>> +{
>>>>> +    uint64_t pre_target_addr;
>>>>> +    int to = 0, from = 0x0dd;
>>>>> +
>>>>> +    asm volatile ( ".pushsection .text.ex_odd\n"
>>>>> +        "    .balign    2\n"
>>>>> +        "pre_odd_ex_target:\n"
>>>>> +        "    . = . + 1\n"
>>>>> +        "    lr    %[to],%[from]\n"
>>>>> +        "    .popsection\n"
>>>>> +
>>>>> +        "    larl    %[pre_target_addr],pre_odd_ex_target\n"
>>>>> +        "    ex    0,1(%[pre_target_addr])\n"
>>>>> +        : [pre_target_addr] "=&a" (pre_target_addr),
>>>>> +          [to] "+d" (to)
>>>>> +        : [from] "d" (from)
>>>>> +    );
>>>>> +
>>>>> +    assert((pre_target_addr + 1) & 1);
>>>>> +    report(to != from, "did not perform ex with odd target");
>>>>> +    return 0;
>>>>> +}
>>>>
>>>> Can this be triggered with KVM, or is this just a test for TCG?
>>>
>>> With "triggered" I mean: Can this cause an interception in KVM?
>>
>> AFAIK no, but KVM and TCG are not the only things we might want to test.
> 
> Ok, fair, KVM unit tests are not for KVM only anymore since quite a while,
> so if this is helpful elsewhere, I'm fine with this.
> 
> Acked-by: Thomas Huth <thuth@redhat.com>

Yes, we might be due for a rename on s390x. On multiple occasions I had 
to tell people that even if the name starts with KVM we're fully capable 
of testing LPAR and zVM :-)

I also want this in for completeness, the line count is certainly of no 
concern here.

      reply	other threads:[~2023-03-20 12:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 15:54 [kvm-unit-tests PATCH v3 0/3] s390x: Add misaligned instruction tests Nina Schoetterl-Glausch
2023-03-15 15:54 ` [kvm-unit-tests PATCH v3 1/3] s390x/spec_ex: Use PSW macro Nina Schoetterl-Glausch
2023-03-15 15:54 ` [kvm-unit-tests PATCH v3 2/3] s390x/spec_ex: Add test introducing odd address into PSW Nina Schoetterl-Glausch
2023-03-17  9:26   ` Janosch Frank
2023-03-17 10:51     ` Nina Schoetterl-Glausch
2023-03-17 12:21       ` Janosch Frank
2023-03-15 15:54 ` [kvm-unit-tests PATCH v3 3/3] s390x/spec_ex: Add test of EXECUTE with odd target address Nina Schoetterl-Glausch
2023-03-17  9:51   ` Janosch Frank
2023-03-17 14:09   ` Thomas Huth
2023-03-17 14:11     ` Thomas Huth
2023-03-17 15:36       ` Claudio Imbrenda
2023-03-17 16:37         ` Thomas Huth
2023-03-20 12:21           ` Janosch Frank [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=36e0a286-d3ee-7bbc-5b8c-e484fa75e672@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=iii@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nsg@linux.ibm.com \
    --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