All of lore.kernel.org
 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,
	gmonaco@redhat.com, linux-trace-kernel@vger.kernel.org,
	linux-kernel@vger.kernel.org, john.ogness@linutronix.de,
	pmladek@suse.com, senozhatsky@chromium.org, mingo@redhat.com,
	tglx@linutronix.de, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, hpa@zytor.com, luto@kernel.org,
	peterz@infradead.org, catalin.marinas@arm.com,
	linux-arm-kernel@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr
Subject: Re: [PATCH v8 00/22] RV: Linear temporal logic monitors for RT application
Date: Sun, 10 Aug 2025 21:12:37 +0000	[thread overview]
Message-ID: <175486035774.1221929.10309183570543138134.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1747046848.git.namcao@linutronix.de>

Hello:

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

On Mon, 12 May 2025 12:50:43 +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:
  - [v8,18/22] 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




WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Nam Cao <namcao@linutronix.de>
Cc: linux-riscv@lists.infradead.org, rostedt@goodmis.org,
	gmonaco@redhat.com, linux-trace-kernel@vger.kernel.org,
	linux-kernel@vger.kernel.org, john.ogness@linutronix.de,
	pmladek@suse.com, senozhatsky@chromium.org, mingo@redhat.com,
	tglx@linutronix.de, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, hpa@zytor.com, luto@kernel.org,
	peterz@infradead.org, catalin.marinas@arm.com,
	linux-arm-kernel@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr
Subject: Re: [PATCH v8 00/22] RV: Linear temporal logic monitors for RT application
Date: Sun, 10 Aug 2025 21:12:37 +0000	[thread overview]
Message-ID: <175486035774.1221929.10309183570543138134.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1747046848.git.namcao@linutronix.de>

Hello:

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

On Mon, 12 May 2025 12:50:43 +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:
  - [v8,18/22] 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



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

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

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 10:50 [PATCH v8 00/22] RV: Linear temporal logic monitors for RT application Nam Cao
2025-05-12 10:50 ` Nam Cao
2025-05-12 10:50 ` [PATCH v8 01/22] rv: Add #undef TRACE_INCLUDE_FILE Nam Cao
2025-05-12 10:50 ` [PATCH v8 02/22] printk: Make vprintk_deferred() public Nam Cao
2025-05-12 10:50 ` [PATCH v8 03/22] panic: Add vpanic() Nam Cao
2025-05-12 10:50 ` [PATCH v8 04/22] rv: Let the reactors take care of buffers Nam Cao
2025-05-12 10:50 ` [PATCH v8 05/22] verification/dot2k: Make a separate dot2k_templates/Kconfig_container Nam Cao
2025-05-12 10:50 ` [PATCH v8 06/22] verification/dot2k: Remove __buff_to_string() Nam Cao
2025-05-12 10:50 ` [PATCH v8 07/22] verification/dot2k: Replace is_container() hack with subparsers Nam Cao
2025-05-12 10:50 ` [PATCH v8 08/22] rv: rename CONFIG_DA_MON_EVENTS to CONFIG_RV_MON_EVENTS Nam Cao
2025-05-12 10:50 ` [PATCH v8 09/22] verification/dot2k: Prepare the frontend for LTL inclusion Nam Cao
2025-05-12 10:50 ` [PATCH v8 10/22] Documentation/rv: Prepare monitor synthesis document " Nam Cao
2025-05-12 10:50 ` [PATCH v8 11/22] verification/rvgen: Restructure the templates files Nam Cao
2025-05-12 10:50 ` [PATCH v8 12/22] verification/rvgen: Restructure the classes to prepare for LTL inclusion Nam Cao
2025-05-12 10:50 ` [PATCH v8 13/22] rv: Add support for LTL monitors Nam Cao
2025-05-12 10:50 ` [PATCH v8 14/22] rv: Add rtapp container monitor Nam Cao
2025-05-12 10:50 ` [PATCH v8 15/22] x86/tracing: Remove redundant trace_pagefault_key Nam Cao
2025-05-12 10:50 ` [PATCH v8 16/22] x86/tracing: Move page fault trace points to generic Nam Cao
2025-05-12 10:51 ` [PATCH v8 17/22] arm64: mm: Add page fault trace points Nam Cao
2025-05-19 14:49   ` Catalin Marinas
2025-05-20 12:25     ` Nam Cao
2025-05-20 14:15       ` Catalin Marinas
2025-05-21  9:03         ` Nam Cao
2025-05-12 10:51 ` [PATCH v8 18/22] riscv: " Nam Cao
2025-05-12 10:51   ` Nam Cao
2025-05-12 10:51 ` [PATCH v8 19/22] rv: Add rtapp_pagefault monitor Nam Cao
2025-05-12 10:51 ` [PATCH v8 20/22] rv: Add rtapp_sleep monitor Nam Cao
2025-05-16 16:31   ` Gabriele Monaco
2025-05-19  7:04     ` Nam Cao
2025-05-19  7:54       ` Gabriele Monaco
2025-05-12 10:51 ` [PATCH v8 21/22] rv: Add documentation for rtapp monitor Nam Cao
2025-05-12 10:51 ` [PATCH v8 22/22] rv: Allow to configure the number of per-task monitor Nam Cao
2025-05-16  8:21 ` [PATCH v8 00/22] RV: Linear temporal logic monitors for RT application Ingo Molnar
2025-05-16  8:21   ` Ingo Molnar
2025-05-16  8:55   ` Nam Cao
2025-05-16  8:55     ` Nam Cao
2025-05-16  9:07     ` Nam Cao
2025-05-16  9:07       ` Nam Cao
2025-05-16  9:12     ` Ingo Molnar
2025-05-16  9:12       ` Ingo Molnar
2025-08-10 21:12 ` patchwork-bot+linux-riscv [this message]
2025-08-10 21:12   ` patchwork-bot+linux-riscv

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=175486035774.1221929.10309183570543138134.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=gmonaco@redhat.com \
    --cc=hpa@zytor.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namcao@linutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 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.