From: "Alex Bennée" <alex.bennee@linaro.org>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Ben Widawsky" <ben.widawsky@intel.com>,
qemu-devel@nongnu.org, "Saransh Gupta1" <saransh@ibm.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Shreyas Shah" <shreyas.shah@elastics.cloud>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
shameerali.kolothum.thodi@huawei.com
Subject: Re: Follow-up on the CXL discussion at OFTC
Date: Wed, 01 Dec 2021 10:29:53 +0000 [thread overview]
Message-ID: <871r2wzhto.fsf@linaro.org> (raw)
In-Reply-To: <20211201095532.000035d8@Huawei.com>
Jonathan Cameron <Jonathan.Cameron@Huawei.com> writes:
> On Tue, 30 Nov 2021 09:21:58 -0800
> Ben Widawsky <ben.widawsky@intel.com> wrote:
>
>> On 21-11-30 13:09:56, Jonathan Cameron wrote:
>> > On Mon, 29 Nov 2021 18:28:43 +0000
>> > Alex Bennée <alex.bennee@linaro.org> wrote:
>> >
>> > > Ben Widawsky <ben.widawsky@intel.com> writes:
>> > >
>> > > > On 21-11-26 12:08:08, Alex Bennée wrote:
>> > > >>
>> > > >> Ben Widawsky <ben.widawsky@intel.com> writes:
>> > > >>
<snip>
>> > >
>> > > >> * Some means at least ensuring qtest can instantiate the device and not
>> > > >> fall over. Obviously more testing is better but it can always be
>> > > >> expanded on in later series.
>> > > >
>> > > > This was in the patch series. It could use more testing for sure, but I had
>> > > > basic functional testing in place via qtest.
>> > >
>> > > More is always better but the basic qtest does ensure a device doesn't
>> > > segfault if it's instantiated.
>> >
>> > I'll confess this is a bit I haven't looked at yet. Will get Shameer to give
>> > me a hand.
>> >
>> > Thanks
>>
>> I'd certainly feel better if we had more tests. I also suspect the qtest I wrote
>> originally no longer works. The biggest challenge I had was getting gitlab CI
>> working for me.
>
> Looks like it'll be tests that slow things down. *sigh*.
Hopefully the GitLab stuff has stabilised over the last year as we've
aggressively pushed out stuff that times out and also limited some test
to only run on upstream staging branches.
The biggest hole is properly exercising KVM stuff (due to the
limitations of GitLab runners). As a result you fall back to TCG which
can get slow if your booting full distros with it.
> Why are there not enough days in the week?
"oh it's softfreeze already?" - a regular occurrence for me ;-)
>
> Jonathan
--
Alex Bennée
next prev parent reply other threads:[~2021-12-01 11:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF255704A1.78FEF164-ON0025878E.00821084-0025878F.00015560@ibm.com>
[not found] ` <20211117165719.pqig62t5z2grgjvv@intel.com>
2021-11-17 17:32 ` Follow-up on the CXL discussion at OFTC Jonathan Cameron
2021-11-18 22:20 ` Saransh Gupta1
2021-11-18 22:52 ` Shreyas Shah via
2021-11-19 1:48 ` Ben Widawsky
2021-11-19 2:29 ` Shreyas Shah via
2021-11-19 3:25 ` Ben Widawsky
2021-11-26 12:08 ` Alex Bennée
2021-11-29 17:16 ` Ben Widawsky
2021-11-29 18:28 ` Alex Bennée
2021-11-30 13:09 ` Jonathan Cameron via
2021-11-30 17:21 ` Ben Widawsky
2021-12-01 9:55 ` Jonathan Cameron via
2021-12-01 10:29 ` Alex Bennée [this message]
2021-11-19 1:52 ` Ben Widawsky
2021-11-19 18:53 ` Jonathan Cameron
2021-11-19 20:21 ` Ben Widawsky
2021-11-26 10:59 ` Jonathan Cameron via
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=871r2wzhto.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=ben.widawsky@intel.com \
--cc=f4bug@amsat.org \
--cc=linux-cxl@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=saransh@ibm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shreyas.shah@elastics.cloud \
/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).