mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Nam Cao <namcao@linutronix.de>
Cc: linux-riscv@lists.infradead.org, rostedt@goodmis.org,
	john.ogness@linutronix.de, mhiramat@kernel.org,
	mathieu.desnoyers@efficios.com, gmonaco@redhat.com,
	linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	pmladek@suse.com, senozhatsky@chromium.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr
Subject: Re: [PATCH v13 00/12] RV: Linear temporal logic monitors for RT application
Date: Sun, 10 Aug 2025 21:12:42 +0000	[thread overview]
Message-ID: <175486036223.1221929.9747032102829878365.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1752088709.git.namcao@linutronix.de>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Steven Rostedt (Google) <rostedt@goodmis.org>:

On Wed,  9 Jul 2025 21:21:11 +0200 you wrote:
> Real-time applications may have design flaws causing them to have
> unexpected latency. For example, the applications may raise page faults, or
> may be blocked trying to take a mutex without priority inheritance.
> 
> However, while attempting to implement DA monitors for these real-time
> rules, deterministic automaton is found to be inappropriate as the
> specification language. The automaton is complicated, hard to understand,
> and error-prone.
> 
> [...]

Here is the summary with links:
  - [v13,08/12] riscv: mm: Add page fault trace points
    https://git.kernel.org/riscv/c/a37c71ca412d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-08-10 21:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 19:21 Nam Cao
2025-07-09 19:21 ` [PATCH v13 01/12] rv: Add #undef TRACE_INCLUDE_FILE Nam Cao
2025-07-09 19:21 ` [PATCH v13 02/12] printk: Make vprintk_deferred() public Nam Cao
2025-07-09 19:21 ` [PATCH v13 03/12] panic: Add vpanic() Nam Cao
2025-07-09 19:21 ` [PATCH v13 04/12] rv: Let the reactors take care of buffers Nam Cao
2025-07-09 19:21 ` [PATCH v13 05/12] rv: rename CONFIG_DA_MON_EVENTS to CONFIG_RV_MON_EVENTS Nam Cao
2025-07-09 19:21 ` [PATCH v13 06/12] rv: Add support for LTL monitors Nam Cao
2025-07-09 19:21 ` [PATCH v13 07/12] rv: Add rtapp container monitor Nam Cao
2025-07-09 19:21 ` [PATCH v13 08/12] riscv: mm: Add page fault trace points Nam Cao
2025-07-09 19:21 ` [PATCH v13 09/12] rv: Add rtapp_pagefault monitor Nam Cao
2025-07-09 19:21 ` [PATCH v13 10/12] rv: Add rtapp_sleep monitor Nam Cao
2025-07-09 19:21 ` [PATCH v13 11/12] rv: Add documentation for rtapp monitor Nam Cao
2025-07-09 19:21 ` [PATCH v13 12/12] rv: Allow to configure the number of per-task monitor Nam Cao
2025-08-10 21:12 ` patchwork-bot+linux-riscv [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=175486036223.1221929.9747032102829878365.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=gmonaco@redhat.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=namcao@linutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    /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

all inboxes | Powered by JetHome®