From: Thomas Huth <thuth@redhat.com>
To: Mike Kowal <kowal@linux.ibm.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, clg@kaod.org, fbarrat@linux.ibm.com,
npiggin@gmail.com, milesg@linux.ibm.com, lvivier@redhat.com,
pbonzini@redhat.com
Subject: Re: [PATCH] tests/qtest: Add XIVE tests for the powernv10 machine
Date: Thu, 19 Sep 2024 07:19:12 +0200 [thread overview]
Message-ID: <128f9e37-fa1d-4086-8a93-25ac6c44ee6c@redhat.com> (raw)
In-Reply-To: <5eca0fa0-7925-47c3-a857-34f500f98312@linux.ibm.com>
On 18/09/2024 19.08, Mike Kowal wrote:
>
> On 9/18/2024 10:05 AM, Thomas Huth wrote:
...
>> That also does not look like proper content for a header file. Please put
>> it into a .c file instead.
>
> When these test were originally written, the authors had all of the tests
> and their functions in one .c file. Some thought it was too large and
> confusing and I separated the different test functions into separate .h
> files (and including .c files is not typically done). I suppose I could
> have the different functions as individual qtests, opposed to one XIVE
> test... And I couldn't find an example multiple qtest .c files compiled
> and linked together into one qtest.
There are a bunch of qtests that are linked with the object files from
multiple .c files. Have a look at tests/qtest/meson.build, look for the
"qtests = {" around line 320. I think you could do something similar for
your tests here, too.
Thomas
next prev parent reply other threads:[~2024-09-19 5:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 18:23 [PATCH] tests/qtest: Add XIVE tests for the powernv10 machine Michael Kowal
2024-09-18 15:05 ` Thomas Huth
2024-09-18 17:08 ` Mike Kowal
2024-09-19 5:19 ` Thomas Huth [this message]
2024-09-18 15:46 ` Cédric Le Goater
2024-09-18 19:25 ` Mike Kowal
2024-09-18 19:50 ` Mike Kowal
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=128f9e37-fa1d-4086-8a93-25ac6c44ee6c@redhat.com \
--to=thuth@redhat.com \
--cc=clg@kaod.org \
--cc=fbarrat@linux.ibm.com \
--cc=kowal@linux.ibm.com \
--cc=lvivier@redhat.com \
--cc=milesg@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).