From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] configure: Check for KVM linker script support
Date: Mon, 13 Jun 2022 13:59:54 +0200 [thread overview]
Message-ID: <Yqcmuv8dwtU+tntL@pevik> (raw)
In-Reply-To: <YqbyFKN999MTr6Xf@yuki>
> Hi!
> > > Skipping the whole directory will actually cause problems too, since the
> > > runltp files does include the kvm_pagefault01 now which will obvious
> > > fail because the binary would be missing.
> > > I'm not sure what the best solution would be, maybe install dummy
> > > libraries that just print TCONF in a case that linker does now work?
> > KVM tests have their own runfile which can be simply skipped. These
> > tests should not be included in any other runfiles because they should
> > only be run on baremetal. That's the solution: Don't run the KVM runfile
> > if the KVM tests were not built.
> > Also, the KVM Makefile already builds nothing on non-x86 archs so the
> > problem was there from the beginning.
I thought we're using TST_TEST_TCONF() for non-x86 archs.
> Looks like these are not in default scenario either, then this is not a
> reson to block the patch. However we should really figure out how to
> deal with cases like this at least for the new testrunner.
Yes, not having to use TST_TEST_TCONF() would be nice.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-06-13 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 13:14 [LTP] [PATCH] configure: Check for KVM linker script support Martin Doucha
2022-06-10 13:33 ` Cyril Hrubis
2022-06-10 13:39 ` Cyril Hrubis
2022-06-10 14:42 ` Martin Doucha
2022-06-13 8:15 ` Cyril Hrubis
2022-06-13 11:59 ` Petr Vorel [this message]
2022-06-13 12:54 ` Martin Doucha
2022-06-13 13:49 ` Petr Vorel
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=Yqcmuv8dwtU+tntL@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.