From: Markus Elfring <Markus.Elfring@web.de>
To: Alexey Makhalov <alexey.makhalov@broadcom.com>,
linux-graphics-maintainer@vmware.com, pv-drivers@vmware.com,
virtualization@lists.linux.dev, dri-devel@lists.freedesktop.org,
linux-input@vger.kernel.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org, x86@kernel.org,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ajay Kaher <akaher@vmware.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Simon Horman <horms@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Tim Merrifield <timothym@vmware.com>,
Zack Rusin <zackr@vmware.com>
Subject: Re: [PATCH v10 6/8] x86/vmware: Correct macro names
Date: Sat, 25 May 2024 17:53:05 +0200 [thread overview]
Message-ID: <448230a6-1afd-416f-a430-3fc83d81908f@web.de> (raw)
In-Reply-To: <20240523191446.54695-7-alexey.makhalov@broadcom.com>
> VCPU_RESERVED and LEGACY_X2APIC are not VMware hypercall commands.
> These are bits in return value of VMWARE_CMD_GETVCPU_INFO command.
> Change VMWARE_CMD_ prefix to GETVCPU_INFO_ one. …
Can such information be relevant for the addition of the tag “Fixes”?
Regards,
Markus
next prev parent reply other threads:[~2024-05-25 15:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 19:14 [PATCH v10 0/8] VMware hypercalls enhancements Alexey Makhalov
2024-05-23 19:14 ` [PATCH v10 1/8] x86/vmware: Introduce VMware hypercall API Alexey Makhalov
2024-05-27 17:07 ` Borislav Petkov
2024-05-30 0:44 ` Alexey Makhalov
2024-06-03 17:58 ` Borislav Petkov
2024-06-06 23:18 ` Alexey Makhalov
2024-06-06 23:23 ` [PATCH v11 " Alexey Makhalov
2024-06-12 22:11 ` Alexey Makhalov
2024-06-13 8:03 ` Borislav Petkov
2024-05-23 19:14 ` [PATCH v10 2/8] ptp/vmware: Use " Alexey Makhalov
2024-05-23 19:14 ` [PATCH v10 3/8] input/vmmouse: " Alexey Makhalov
2024-05-23 19:14 ` [PATCH v10 4/8] drm/vmwgfx: " Alexey Makhalov
2024-05-23 19:14 ` [PATCH v10 5/8] x86/vmware: " Alexey Makhalov
2024-05-23 19:14 ` [PATCH v10 6/8] x86/vmware: Correct macro names Alexey Makhalov
2024-05-25 15:53 ` Markus Elfring [this message]
2024-05-30 0:45 ` Alexey Makhalov
2024-05-23 19:14 ` [PATCH v10 7/8] x86/vmware: Remove legacy VMWARE_HYPERCALL* macros Alexey Makhalov
2024-05-23 19:14 ` [PATCH v10 8/8] x86/vmware: Add TDX hypercall support Alexey Makhalov
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=448230a6-1afd-416f-a430-3fc83d81908f@web.de \
--to=markus.elfring@web.de \
--cc=airlied@gmail.com \
--cc=akaher@vmware.com \
--cc=alexey.makhalov@broadcom.com \
--cc=bp@alien8.de \
--cc=daniel@ffwll.ch \
--cc=dave.hansen@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=horms@kernel.org \
--cc=hpa@zytor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mingo@redhat.com \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=tglx@linutronix.de \
--cc=timothym@vmware.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
--cc=x86@kernel.org \
--cc=zackr@vmware.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;
as well as URLs for NNTP newsgroup(s).