From: Petri Latvala <petri.latvala@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: igt-dev@lists.freedesktop.org,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-gfx@lists.freedesktop.org, "CQ Tang" <cq.tang@intel.com>
Subject: Re: [Intel-gfx] [igt-dev] [PATCH i-g-t 3/4] tests/gem_lmem_swapping: limit lmem to 4G
Date: Fri, 25 Mar 2022 12:02:37 +0200 [thread overview]
Message-ID: <Yj2TPQE3p16uIFLP@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <af23ceff-4899-6bef-87e5-273419f030f8@intel.com>
On Fri, Mar 25, 2022 at 08:40:45AM +0000, Matthew Auld wrote:
> On 24/03/2022 17:47, Dixit, Ashutosh wrote:
> > On Thu, 24 Mar 2022 07:26:20 -0700, Matthew Auld wrote:
> > >
> > > @@ -554,6 +560,7 @@ igt_main_args("", long_options, help_str, opt_handler, NULL)
> > > igt_fixture {
> > > free(regions);
> > > close(i915);
> > > + igt_i915_driver_unload();
> >
> > I thought we'd reload the module with default params here but when the next
> > test runs the module gets loaded automatically so maybe this is ok?
>
> Yeah, that at least matches my understanding. Adding Petri in case he has
> some comments here.
Yes, the convention is to either leave the module loaded with
defaults, or leave it unloaded. If the next test happens to be one
that wants to load the module with different params, we save some
time.
If loading the module again doesn't work we should see some fireworks
in CI results elsewhere anyway. Due to module loading problems we used
to limit them to known places (reloading tests, selftests, ...) so we
might need to revisit this topic later. But no need to FUD it at this
time.
--
Petri Latvala
next prev parent reply other threads:[~2022-03-25 10:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 14:26 [Intel-gfx] [PATCH i-g-t 0/4] Some gem_lmem_swapping tweaks Matthew Auld
2022-03-24 14:26 ` [Intel-gfx] [PATCH i-g-t 1/4] test/gem_lmem_swapping: account for object rounding Matthew Auld
2022-03-24 17:25 ` Dixit, Ashutosh
2022-03-25 8:05 ` Thomas Hellström
2022-03-24 14:26 ` [Intel-gfx] [PATCH i-g-t 2/4] test/gem_lmem_swapping: fix physical engine usage Matthew Auld
2022-03-24 14:46 ` Tvrtko Ursulin
2022-03-24 17:39 ` [Intel-gfx] [igt-dev] " Dixit, Ashutosh
2022-03-24 14:26 ` [Intel-gfx] [PATCH i-g-t 3/4] tests/gem_lmem_swapping: limit lmem to 4G Matthew Auld
2022-03-24 14:33 ` Thomas Hellström
2022-03-24 17:47 ` [Intel-gfx] [igt-dev] " Dixit, Ashutosh
2022-03-25 8:40 ` Matthew Auld
2022-03-25 10:02 ` Petri Latvala [this message]
2022-03-25 10:13 ` [Intel-gfx] " Das, Nirmoy
2022-03-25 10:18 ` [Intel-gfx] [igt-dev] " Petri Latvala
2022-03-25 10:20 ` Matthew Auld
2022-03-24 14:26 ` [Intel-gfx] [PATCH i-g-t 4/4] tests/gem_lmem_swapping: reduce the timeout Matthew Auld
2022-03-25 7:21 ` Thomas Hellström
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=Yj2TPQE3p16uIFLP@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=cq.tang@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@linux.intel.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