All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kubaj, Piotr" <piotr.kubaj@intel.com>
To: "chrubis@suse.cz" <chrubis@suse.cz>
Cc: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
	"Ossowski, Tomasz" <tomasz.ossowski@intel.com>,
	"Dubel, Helena Anna" <helena.anna.dubel@intel.com>,
	"Niestepski, Daniel" <daniel.niestepski@intel.com>,
	"ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v3] pmc_core: add test for pkgc_blocker_residency_show
Date: Fri, 4 Sep 2026 12:42:04 +0000	[thread overview]
Message-ID: <41a0da4371dea1aa8d2a37936ecd6d799a055f4e.camel@intel.com> (raw)
In-Reply-To: <apGAei1EG3ioALnL@yuki.lan>

2026-08-28 (金) の 14:35 +0200 に Cyril Hrubis さんは書きました:
> Hi!
> > One question: there doesn't seem to be a way to check whether
> > debugfs
> > is mounted, apart from implementing it myself. I have another test
> > in
> > the queue for LTR counters that also uses debugfs. Does it make
> > sense
> > to put that debugfs check somewhere in the framework, or do you
> > prefer
> > it to be put directly in the tests? It's about 25 LOC.
> 
> If more than one test would use it makes sense to add a library
> support
> for mounting debugfs.
> 
> Also generally distributions are moving into not mounting debugfs by
> default, since there have been security implications of exporting
> internal kernel state by default. So it would make sense to add
> .needs_debugfs flag to the tst_test struct that would cause the
> library
> mount (and later umount) debugfs at .mntpoint unconditionally.
OK, patch succeeded by a new series adding those two tests that need
debugfs and the commit adding debugfs handling to the framework.
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.
Spolka oswiadcza, ze posiada status duzego przedsiebiorcy w rozumieniu ustawy z dnia 8 marca 2013 r. o przeciwdzialaniu nadmiernym opoznieniom w transakcjach handlowych.

Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek przegladanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.

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

      reply	other threads:[~2026-09-04 12:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  6:40 [LTP] [PATCH v3] pmc_core: add test for pkgc_blocker_residency_show Piotr Kubaj
2026-08-17  6:57 ` [LTP] " linuxtestproject.agent
2026-08-18  8:15 ` [LTP] [PATCH v3] " Kubaj, Piotr
2026-08-28 12:35   ` Cyril Hrubis
2026-09-04 12:42     ` Kubaj, Piotr [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=41a0da4371dea1aa8d2a37936ecd6d799a055f4e.camel@intel.com \
    --to=piotr.kubaj@intel.com \
    --cc=chrubis@suse.cz \
    --cc=daniel.niestepski@intel.com \
    --cc=helena.anna.dubel@intel.com \
    --cc=ltp@lists.linux.it \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tomasz.ossowski@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 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.