From: "Chris Mason" <mason@kernel.org>
To: "Sean Christopherson" <seanjc@google.com>,
"Amirmohammad Eftekhar" <amirmohammad.eftekhar@cispa.de>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Josef Bacik" <josef@toxicpanda.com>
Subject: Re: [PATCH] KVM: x86: Ratelimit guest-triggerable IOAPIC/LAPIC log messages
Date: Sat, 17 Oct 2026 11:34:07 -0400 [thread overview]
Message-ID: <ea8975d7-8e3e-41c7-b44d-708f2194438e@app.fastmail.com> (raw)
In-Reply-To: <atOCbna3qAQZ1wLn@google.com>
On Sat, Oct 17, 2026, at 10:13 AM, Sean Christopherson wrote:
> +Josef and Chris
Thanks!
>
> On Sat, Oct 17, 2026, Amirmohammad Eftekhar wrote:
>
> This, and more flaws of this nature, were also sent along off-list by Josef and
> Chris. For this specific case, I think what I'll do is combine all of the
> APIC ratelimited conversions into a single patch, flip a coin for the Author,
> and list the other person as Co-Author. Any objections to that approach?
I know everyone is cranking hard to clear the bugs out, so we're good with
literally anything. The LLM generated commits might need changes and
might only fix part of the problem, or might have been found independently
by others etc. We'll be happy just crossing issues off the list regardless of
how those patches are credited in git.
-chris
next prev parent reply other threads:[~2026-10-17 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 9:30 Amirmohammad Eftekhar
2026-10-17 14:13 ` Sean Christopherson
2026-10-17 15:34 ` Chris Mason [this message]
2026-10-17 16:34 ` Amirmohammad Eftekhar
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=ea8975d7-8e3e-41c7-b44d-708f2194438e@app.fastmail.com \
--to=mason@kernel.org \
--cc=amirmohammad.eftekhar@cispa.de \
--cc=josef@toxicpanda.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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
all inboxes | Powered by JetHome®