From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: kvm@vger.kernel.org, thuth@redhat.com, nrb@linux.ibm.com,
linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH 1/5] lib: s390x: Add ap library
Date: Thu, 30 Mar 2023 18:09:00 +0200 [thread overview]
Message-ID: <20230330180900.723c060d@p-imbrenda> (raw)
In-Reply-To: <20230330114244.35559-2-frankja@linux.ibm.com>
On Thu, 30 Mar 2023 11:42:40 +0000
Janosch Frank <frankja@linux.ibm.com> wrote:
> Add functions and definitions needed to test the Adjunct
> Processor (AP) crypto interface.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>
[...]
> +bool ap_check(void)
> +{
> + struct ap_queue_status r1 = {};
> + struct pqap_r2 r2 = {};
> +
> + /* Base AP support has no STFLE or SCLP feature bit */
this is true, but you are also indiscriminately using a feature for
which there is a STFLE feature. since it seems you depend on that, you
might as well just check bit for STFLE.12 and assume the base support
is there if it's set
> + expect_pgm_int();
> + ap_pqap_tapq(0, 0, &r1, &r2);
> +
> + if (clear_pgm_int() == PGM_INT_CODE_OPERATION)
> + return false;
> +
> + return true;
> +}
[...]
> +struct ap_config_info {
> + uint8_t apsc : 1; /* S bit */
> + uint8_t apxa : 1; /* N bit */
> + uint8_t qact : 1; /* C bit */
> + uint8_t rc8a : 1; /* R bit */
> + uint8_t l : 1; /* L bit */
> + uint8_t lext : 3; /* Lext bits */
> + uint8_t reserved2[3];
> + uint8_t Na; /* max # of APs - 1 */
> + uint8_t Nd; /* max # of Domains - 1 */
> + uint8_t reserved6[10];
> + uint32_t apm[8]; /* AP ID mask */
is there a specific reason why these are uint32_t?
uint64_t would maybe make your life easier in subsequent patches (see my
comments there)
> + uint32_t aqm[8]; /* AP (usage) queue mask */
> + uint32_t adm[8]; /* AP (control) domain mask */
> + uint8_t _reserved4[16];
> +} __attribute__((aligned(8))) __attribute__ ((__packed__));
> +_Static_assert(sizeof(struct ap_config_info) == 128, "PQAP QCI size");
> +
> +struct pqap_r0 {
> + uint32_t pad0;
> + uint8_t fc;
> + uint8_t t : 1; /* Test facilities (TAPQ)*/
> + uint8_t pad1 : 7;
> + uint8_t ap;
> + uint8_t qn;
> +} __attribute__((packed)) __attribute__((aligned(8)));
> +
> +struct pqap_r2 {
> + uint8_t s : 1; /* Special Command facility */
> + uint8_t m : 1; /* AP4KM */
> + uint8_t c : 1; /* AP4KC */
> + uint8_t cop : 1; /* AP is in coprocessor mode */
> + uint8_t acc : 1; /* AP is in accelerator mode */
> + uint8_t xcp : 1; /* AP is in XCP-mode */
> + uint8_t n : 1; /* AP extended addressing facility */
> + uint8_t pad_0 : 1;
> + uint8_t pad_1[3];
> + uint8_t at;
> + uint8_t nd;
> + uint8_t pad_6;
> + uint8_t pad_7 : 4;
> + uint8_t qd : 4;
> +} __attribute__((packed)) __attribute__((aligned(8)));
> +_Static_assert(sizeof(struct pqap_r2) == sizeof(uint64_t), "pqap_r2 size");
> +
> +bool ap_check(void);
> +int ap_pqap_tapq(uint8_t ap, uint8_t qn, struct ap_queue_status *apqsw,
> + struct pqap_r2 *r2);
> +int ap_pqap_qci(struct ap_config_info *info);
> +#endif
next prev parent reply other threads:[~2023-03-30 16:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 11:42 [kvm-unit-tests PATCH 0/5] s390x: Add base AP support Janosch Frank
2023-03-30 11:42 ` [kvm-unit-tests PATCH 1/5] lib: s390x: Add ap library Janosch Frank
2023-03-30 16:09 ` Claudio Imbrenda [this message]
2023-03-31 7:32 ` Janosch Frank
2023-03-30 11:42 ` [kvm-unit-tests PATCH 2/5] s390x: Add guest 2 AP test Janosch Frank
2023-03-30 16:34 ` Claudio Imbrenda
2023-03-31 8:52 ` Janosch Frank
2023-03-30 11:42 ` [kvm-unit-tests PATCH 3/5] lib: s390x: ap: Add ap_setup Janosch Frank
2023-03-30 16:40 ` Claudio Imbrenda
2023-03-30 11:42 ` [kvm-unit-tests PATCH 4/5] s390x: ap: Add pqap aqic tests Janosch Frank
2023-03-30 16:44 ` Claudio Imbrenda
2023-03-30 11:42 ` [kvm-unit-tests PATCH 5/5] s390x: ap: Add reset tests Janosch Frank
2023-03-30 16:48 ` Claudio Imbrenda
2023-04-03 14:57 ` Pierre Morel
2023-04-04 11:40 ` Janosch Frank
2023-04-04 15:23 ` 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=20230330180900.723c060d@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@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