All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Doucha <mdoucha@suse.cz>
To: "Ricardo B. Marlière" <rbm@suse.com>,
	"Linux Test Project" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] syscalls/getrusage04: Disable for VIRT_OTHER
Date: Tue, 25 Feb 2025 16:49:53 +0100	[thread overview]
Message-ID: <edfdbd78-16fc-484a-b02e-1c8492ae7b09@suse.cz> (raw)
In-Reply-To: <D81N53167CCA.10KD9DYLMQMMA@suse.com>

On 25. 02. 25 16:44, Ricardo B. Marlière wrote:
> On Tue Feb 25, 2025 at 12:09 PM -03, Martin Doucha wrote:
>> Hi,
>> I think it'd be better to change the condition to this:
>>
>> if (tst_is_virt(VIRT_ANY))
>>       tst_brkm(TCONF, ...);
>>
>> Otherwise we'll play endless whack-a-mole with future virt environments.
> 
> But if `systemd-detect-virt` outputs "amazon", wouldn't that translate
> to VIRT_OTHER [1]? i.e. The goal is to also skip on VIRT_OTHER, unless
> we invert the logic.

VIRT_ANY is a wildcard value that'll match any virtualized environment. 
If somebody decides to define separate VIRT_AMAZON env type in the LTP 
library in the future, getrusage04 would start to fail again if we only 
add check for VIRT_OTHER. With VIRT_ANY, the new env type will stay covered.

-- 
Martin Doucha   mdoucha@suse.cz
SW Quality Engineer
SUSE LINUX, s.r.o.
CORSO IIa
Krizikova 148/34
186 00 Prague 8
Czech Republic

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2025-02-25 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 16:26 [LTP] [PATCH] syscalls/getrusage04: Disable for VIRT_OTHER Ricardo B. Marlière via ltp
2025-02-25 15:09 ` Martin Doucha
2025-02-25 15:44   ` Ricardo B. Marlière via ltp
2025-02-25 15:49     ` Martin Doucha [this message]

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=edfdbd78-16fc-484a-b02e-1c8492ae7b09@suse.cz \
    --to=mdoucha@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=rbm@suse.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 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.