From: Borislav Petkov <bp@alien8.de>
To: Zack Rusin <zack.rusin@broadcom.com>
Cc: Ajay Kaher <ajay.kaher@broadcom.com>,
Alexey Makhalov <alexey.makhalov@broadcom.com>,
x86@kernel.org, Thomas Gleixner <tglx@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H . Peter Anvin" <hpa@zytor.com>,
virtualization@lists.linux.dev,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
llvm@lists.linux.dev
Subject: Re: [PATCH v1] x86/vmware: Fix i386 high-bandwidth hypercall arguments
Date: Tue, 27 Oct 2026 23:00:42 -0700 [thread overview]
Message-ID: <20261028060042.GCauGPirK7ePNeTGF0@fat_crate.local> (raw)
In-Reply-To: <CABQX2QMNetg9iYRRsQmeM3+1tnC94ccWM=450wMZL_sUbqAJtA@mail.gmail.com>
On Tue, Oct 20, 2026 at 11:34:23PM -0400, Zack Rusin wrote:
> Gentle ping on this one. It's a stable fix for the i386 high-bandwidth
> hypercalls (vmwgfx uses them), Maaz reviewed it, and it still applies
> cleanly to v7.3. The hypercall cleanup series I'm about to post moves
> this assembly out of line and is based on it, so it would help to know
> whether it's queued or needs changes.
Sashiko complains about some pre-existing issues:
https://sashiko.dev/#/patchset/4ab10678a8f50053934b62b56af81f881c1d3798.1788414669.git.zack.rusin%40broadcom.com
Please address them: if valid, you should see about fixing them, if not,
explain why they don't need to be fixed.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-10-28 6:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 16:07 Zack Rusin
2026-09-03 23:33 ` Maaz Mombasawala
2026-10-21 3:34 ` Zack Rusin
2026-10-28 6:00 ` Borislav Petkov [this message]
2026-10-28 12:02 ` Zack Rusin
2026-10-28 15:12 ` Borislav Petkov
2026-10-28 8:27 ` Peter Zijlstra
2026-10-28 12:41 ` Zack Rusin
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=20261028060042.GCauGPirK7ePNeTGF0@fat_crate.local \
--to=bp@alien8.de \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=x86@kernel.org \
--cc=zack.rusin@broadcom.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®