From: Nico Boehr <nrb@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
frankja@linux.ibm.com, thuth@redhat.com, david@redhat.com,
farman@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH 2/2] s390x: add test for SIGP STORE_ADTL_STATUS order
Date: Mon, 11 Apr 2022 15:23:17 +0200 [thread overview]
Message-ID: <243cc4903700b39072a20636f2433d43320fe4c2.camel@linux.ibm.com> (raw)
In-Reply-To: <20220406153107.0b071dcc@p-imbrenda>
On Wed, 2022-04-06 at 15:31 +0200, Claudio Imbrenda wrote:
> > diff --git a/s390x/adtl-status.c b/s390x/adtl-status.c
> > new file mode 100644
> > index 000000000000..c3ecdbc35a9d
> >
[...]
> > +static void restart_write_vector(void)
> > +{
> > + uint8_t *vec_reg;
> > + /* vlm handles at most 16 registers at a time */
> > + uint8_t *vec_reg_16_31 = &expected_vec_contents[16][0];
> > + uint64_t cr0, cr0_mask = ~(1ULL << CTL0_VECTOR);
>
> cr0_mask can be const, and you can use ~BIT_ULL(CTL0_VECTOR)
I don't think so, since ng in the inline ASM will store its result
there.
BIT_ULL is much better, thanks. I tend to forget about that.
>
> > + int one = 1;
>
> one can also be const, although I wonder if this can just become an
> constant in the asm statement
Yes, right, thanks. Should work with mvhi.
next prev parent reply other threads:[~2022-04-11 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 12:33 [kvm-unit-tests PATCH 0/2] s390x: Add tests for SIGP store adtl status Nico Boehr
2022-04-01 12:33 ` [kvm-unit-tests PATCH 1/2] s390x: gs: move to new header file Nico Boehr
2022-04-12 11:21 ` Thomas Huth
2022-04-01 12:33 ` [kvm-unit-tests PATCH 2/2] s390x: add test for SIGP STORE_ADTL_STATUS order Nico Boehr
2022-04-06 13:31 ` Claudio Imbrenda
2022-04-11 13:23 ` Nico Boehr [this message]
2022-04-11 14:05 ` Claudio Imbrenda
2022-04-12 15:20 ` [kvm-unit-tests PATCH 0/2] s390x: Add tests for SIGP store adtl status Claudio Imbrenda
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=243cc4903700b39072a20636f2433d43320fe4c2.camel@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@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