Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Collin Walling <walling@linux.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	kvm@vger.kernel.org, linux-kselftest@vger.kernel.org
Cc: david@redhat.com, thuth@redhat.com, cohuck@redhat.com,
	pbonzini@redhat.com, imbrenda@linux.ibm.com
Subject: Re: [PATCH v3] self_tests/kvm: sync_regs test for diag318
Date: Mon, 7 Dec 2020 10:26:48 -0500	[thread overview]
Message-ID: <5da42ff4-fdc4-ef84-94f6-07fe9a54c9f9@linux.ibm.com> (raw)
In-Reply-To: <06853772-8c12-b5e9-761f-9743ce01e270@de.ibm.com>

On 12/7/20 3:19 AM, Christian Borntraeger wrote:
> 
> 
> On 07.12.20 09:16, Janosch Frank wrote:
>> On 12/3/20 10:52 PM, Collin Walling wrote:
>>> The DIAGNOSE 0x0318 instruction, unique to s390x, is a privileged call
>>
>> s/call/instruction/
>>
>>> that must be intercepted via SIE, handled in userspace, and the
>>> information set by the instruction is communicated back to KVM.
>>>
>>> To test the instruction interception, an ad-hoc handler is defined which
>>> simply has a VM execute the instruction and then userspace will extract
>>> the necessary info. The handler is defined such that the instruction
>>> invocation occurs only once. It is up to the caller to determine how the
>>> info returned by this handler should be used.
>>>
>>> The diag318 info is communicated from userspace to KVM via a sync_regs
>>> call. This is tested during a sync_regs test, where the diag318 info is
>>> requested via the handler, then the info is stored in the appropriate
>>> register in KVM via a sync registers call.
>>>
>>> If KVM does not support diag318, then the tests will print a message
>>> stating that diag318 was skipped, and the asserts will simply test
>>> against a value of 0.
>>>
>>> Signed-off-by: Collin Walling <walling@linux.ibm.com>
>>
>> Acked-by: Janosch Frank <frankja@linux.ibm.com>
>>
>> Some nits below.
> 
> Collin, can you have a look at the nits and resubmit soon? Then I can pick this
> for 5.11.
> 

Will do.

[...[


-- 
Regards,
Collin

Stay safe and stay healthy

  reply	other threads:[~2020-12-07 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 21:52 [PATCH v3] self_tests/kvm: sync_regs test for diag318 Collin Walling
2020-12-07  8:16 ` Janosch Frank
2020-12-07  8:19   ` Christian Borntraeger
2020-12-07 15:26     ` Collin Walling [this message]
2020-12-07 15:26   ` Collin Walling

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=5da42ff4-fdc4-ef84-94f6-07fe9a54c9f9@linux.ibm.com \
    --to=walling@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=pbonzini@redhat.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