From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] kvm_pagefault01: Do not write into tdp_mmu sysfile
Date: Tue, 28 May 2024 14:25:38 +0200 [thread overview]
Message-ID: <20240528122538.GB435237@pevik> (raw)
In-Reply-To: <CAASaF6yh-xaVZXK8yQkrHWN7sLcSSrpWrF1NBgrSR_h=Ye_NYg@mail.gmail.com>
Hi Martin, Jan,
> On Tue, May 28, 2024 at 11:38 AM Petr Vorel <pvorel@suse.cz> wrote:
> > > On 28. 05. 24 0:35, Petr Vorel wrote:
> > > > > +
> > > > > + if (read_bool_sys_param(TDP_MMU_SYSFILE) > 0)
> > > > > + tst_res(TINFO, "tdp_mmu is enabled, beware of false negatives");
> > > > Wouldn't it be better to add "WARNING:" to make it more visible?
> > > > tst_res(TINFO, "WARNING: tdp_mmu is enabled, beware of false negatives");
> > > > (if you agree, I can change it before merge)
> > > I thought about it for a while and I see good reasons for both TINFO and
> > > TWARN. It shouldn't matter for our tests because tdp_mmu defaults to off on
> > > SLE-15SP4 and SLE-15SP5. If other reviewers agree, feel free to change it to
> > > TWARN.
> > I slightly prefer tst_res(TINFO, "WARNING: ...", than TWARN. Although false
> > negative is serious, still failing the test based on suspicion of false
> > positives is not good.
> > @Li, @Jan, @Metan: any opinion on it?
> I'd go with TINFO here, as you suggested.
Thanks a lot both!
Patchset merged (Jan, I did not dare to add your RBT or ABT as you did not add
it), with added WARNING: (as Martin agreed).
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-05-28 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 13:57 [LTP] [PATCH] kvm_pagefault01: Do not write into tdp_mmu sysfile Martin Doucha
2024-05-27 22:35 ` Petr Vorel
2024-05-28 8:33 ` Martin Doucha
2024-05-28 9:37 ` Petr Vorel
2024-05-28 9:42 ` Martin Doucha
2024-05-28 9:56 ` Jan Stancek
2024-05-28 12:25 ` Petr Vorel [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=20240528122538.GB435237@pevik \
--to=pvorel@suse.cz \
--cc=jstancek@redhat.com \
--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.