From: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
To: Jan Beulich <jbeulich@suse.com>,
Grygorii Strashko <grygorii_strashko@epam.com>
Cc: "Sergiy Kibrik" <Sergiy_Kibrik@epam.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Paul Durrant" <paul@xen.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v5] x86: make Viridian support optional
Date: Mon, 13 Oct 2025 12:01:48 +0200 [thread overview]
Message-ID: <DDH3W3VM2ZDJ.PMFSGBWBTS0S@amd.com> (raw)
In-Reply-To: <3e4e4bc5-aa47-4357-9327-df2a9b9c9a1b@suse.com>
On Wed Oct 8, 2025 at 6:04 PM CEST, Jan Beulich wrote:
> On 30.09.2025 14:52, Grygorii Strashko wrote:
>> --- a/xen/arch/x86/hvm/Kconfig
>> +++ b/xen/arch/x86/hvm/Kconfig
>> @@ -62,6 +62,16 @@ config ALTP2M
>>
>> If unsure, stay with defaults.
>>
>> +config VIRIDIAN
>> + bool "Hyper-V enlightenments for guests" if EXPERT
>> + default y
>> + help
>> + Support optimizations for Hyper-V guests such as faster hypercalls,
>> + efficient timer and interrupt handling, and enhanced paravirtualized
>> + I/O. This is to improve performance and compatibility of Windows VMs.
>
> What is "paravirtualized I/O" about in this context?
Hypervisor-assisted IPIs, TLB flushes, etc. Or so I understood back when I said
that looked ok. I see there could be confusion with Xen PV device protocols,
but as far as the user of the help message is concerned it makes no difference.
One could even remove the examples and leave it as "... for Hyper-V guests. This
is to...". They are truly inconsequential.
All that matters is that (modern) Windows won't run without it, and that it
provides some indeterminate hypervisor-provided assists to try to reduce some
virtualization overheads.
Cheers,
Alejandro
next prev parent reply other threads:[~2025-10-13 10:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 12:52 [PATCH v5] x86: make Viridian support optional Grygorii Strashko
2025-10-08 16:04 ` Jan Beulich
2025-10-09 16:33 ` Grygorii Strashko
2025-10-10 5:22 ` Jan Beulich
2025-10-13 10:01 ` Alejandro Vallejo [this message]
2025-10-13 11:06 ` Jan Beulich
2025-10-15 5:58 ` Demi Marie Obenour
2025-10-17 15:52 ` Alejandro Vallejo
2025-10-19 1:21 ` Demi Marie Obenour
2025-10-20 8:44 ` Roger Pau Monné
2025-10-20 9:57 ` Marek Marczykowski-Górecki
2025-10-13 12:17 ` Roger Pau Monné
2025-10-14 13:24 ` Grygorii Strashko
2025-10-14 14:38 ` Roger Pau Monné
2025-10-14 15:48 ` Grygorii Strashko
2025-10-15 8:00 ` Roger Pau Monné
2025-10-15 8:03 ` Jan Beulich
2025-10-16 21:40 ` Grygorii Strashko
2025-10-16 22:38 ` Marek Marczykowski-Górecki
2025-10-17 6:01 ` Jan Beulich
2025-10-17 6:51 ` Marek Marczykowski-Górecki
2025-10-17 7:38 ` Roger Pau Monné
2025-10-21 11:04 ` Grygorii Strashko
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=DDH3W3VM2ZDJ.PMFSGBWBTS0S@amd.com \
--to=alejandro.garciavallejo@amd.com \
--cc=Sergiy_Kibrik@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=grygorii_strashko@epam.com \
--cc=jbeulich@suse.com \
--cc=paul@xen.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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.