public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Petr Tesarik <ptesarik@suse.com>, linux-rt-users@vger.kernel.org
Subject: Re: Lazy preemption on arm64
Date: Tue, 17 Dec 2024 13:56:30 +0100	[thread overview]
Message-ID: <20241217125630.EfJm0MX0@linutronix.de> (raw)
In-Reply-To: <Z2FtNgp_OVIy0D36@J2N7QTR9R3>

On 2024-12-17 12:23:18 [+0000], Mark Rutland wrote:
> Yep, I had that in my HACK patch:
> 
>   https://lore.kernel.org/linux-rt-users/20241217115931.wjw_HO2V@linutronix.de/T/#m12eece66786a3a207e4e952bdf58570ab75c6a89
> 
> ... so it sounds like we're on the same page. :)

That is great then. I somehow accounted this for the KVM bits but you
have KVM_XFER_TO_GUEST_WORK so it is all good.

> > I would appreciate it. However if there is reason to delay it I could
> > hold to it for some time…
> 
> I'll try to spin it as a proper patch later this week (and will Cc the
> folk here, along with Jinjie, etc); it'll be up to Will and Catalin as
> to whether they're happy to pick it up, but given it's small I suspect
> that'll be fine.
Okay.

> Mark.

Sebastian

  reply	other threads:[~2024-12-17 12:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 18:04 Lazy preemption on arm64 Petr Tesarik
2024-12-16 19:04 ` Mark Rutland
2024-12-17  0:40   ` gene heskett
2024-12-17  6:03   ` Petr Tesarik
2024-12-17  6:31   ` Petr Tesarik
2024-12-17  8:50     ` Sebastian Andrzej Siewior
2024-12-17 11:34       ` Mark Rutland
2024-12-17 11:59         ` Sebastian Andrzej Siewior
2024-12-17 12:23           ` Mark Rutland
2024-12-17 12:56             ` Sebastian Andrzej Siewior [this message]
2025-02-14  7:34             ` Mike Galbraith

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=20241217125630.EfJm0MX0@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=ptesarik@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox