All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>, kvm@vger.kernel.org
Cc: frankja@linux.ibm.com, david@redhat.com, thuth@redhat.com,
	imbrenda@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH 1/1] s390x: css: check the CSS is working with any ISC
Date: Thu, 12 Aug 2021 14:31:38 +0200	[thread overview]
Message-ID: <87fsvevo7p.fsf@redhat.com> (raw)
In-Reply-To: <1628769189-10699-2-git-send-email-pmorel@linux.ibm.com>

On Thu, Aug 12 2021, Pierre Morel <pmorel@linux.ibm.com> wrote:

> In the previous version we did only check that one ISC dedicated by
> Linux for I/O is working fine.
>
> However, there is no reason to prefer one ISC to another ISC, we are
> free to take anyone.
>
> Let's check all possible ISC to verify that QEMU/KVM is really ISC
> independent.

It's probably a good idea to test for a non-standard isc. Not sure
whether we need all of them, but it doesn't hurt.

Do you also have plans for a test to verify the priority handling for
the different iscs?

>
> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
> ---
>  s390x/css.c | 25 +++++++++++++++++--------
>  1 file changed, 17 insertions(+), 8 deletions(-)
>

(...)

> @@ -142,7 +143,6 @@ static void sense_id(void)
>  
>  static void css_init(void)
>  {
> -	assert(register_io_int_func(css_irq_io) == 0);
>  	lowcore_ptr->io_int_param = 0;
>  
>  	report(get_chsc_scsc(), "Store Channel Characteristics");
> @@ -351,11 +351,20 @@ int main(int argc, char *argv[])
>  	int i;
>  
>  	report_prefix_push("Channel Subsystem");
> -	enable_io_isc(0x80 >> IO_SCH_ISC);
> -	for (i = 0; tests[i].name; i++) {
> -		report_prefix_push(tests[i].name);
> -		tests[i].func();
> -		report_prefix_pop();
> +
> +	for (io_isc = 0; io_isc < 8; io_isc++) {
> +		report_info("ISC: %d\n", io_isc);
> +
> +		enable_io_isc(0x80 >> io_isc);
> +		assert(register_io_int_func(css_irq_io) == 0);

Why are you registering/deregistering the irq handler multiple times? It
should be the same, regardless of the isc?

> +
> +		for (i = 0; tests[i].name; i++) {
> +			report_prefix_push(tests[i].name);
> +			tests[i].func();
> +			report_prefix_pop();
> +		}
> +
> +		unregister_io_int_func(css_irq_io);
>  	}
>  	report_prefix_pop();
>  
>


  reply	other threads:[~2021-08-12 12:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 11:53 [kvm-unit-tests PATCH 0/1] s390x: css: check the CSS is working with any ISC Pierre Morel
2021-08-12 11:53 ` [kvm-unit-tests PATCH 1/1] " Pierre Morel
2021-08-12 12:31   ` Cornelia Huck [this message]
2021-08-12 14:59     ` Pierre Morel
2021-08-18  7:40   ` Thomas Huth
2021-08-23  9:16     ` Pierre Morel

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=87fsvevo7p.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=pmorel@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 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.