From: Peter Maydell <peter.maydell@linaro.org>
To: Mohamed Mediouni <mohamed@unpredictable.fr>
Cc: qemu-devel@nongnu.org, Pedro Barbuda <pbarbuda@microsoft.com>,
Pierrick Bouvier <pierrick.bouvier@linaro.org>
Subject: Re: [PATCH] docs: add WHPX section with initial info
Date: Thu, 26 Mar 2026 14:08:20 +0000 [thread overview]
Message-ID: <CAFEAcA9c48xRmOXc7rVnSU4G0v=snP1_LUMZHKkDMYzVd_GfYw@mail.gmail.com> (raw)
In-Reply-To: <20260326135109.67394-1-mohamed@unpredictable.fr>
On Thu, 26 Mar 2026 at 13:52, Mohamed Mediouni <mohamed@unpredictable.fr> wrote:
>
> Signed-off-by: Mohamed Mediouni <mohamed@unpredictable.fr>
> ---
> MAINTAINERS | 1 +
> docs/system/index.rst | 1 +
> docs/system/whpx.rst | 83 +++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 85 insertions(+)
> create mode 100644 docs/system/whpx.rst
> diff --git a/docs/system/whpx.rst b/docs/system/whpx.rst
> new file mode 100644
> index 0000000000..a3a7ecd38f
> --- /dev/null
> +++ b/docs/system/whpx.rst
> @@ -0,0 +1,83 @@
> +Windows Hypervisor Platform
> +===========================
> +
> +Common
> +------
> +
> +Windows Hypervisor Platform is available for installation through
> +Windows Features (`optionalfeatures.exe`).
> +
> +VM state save/restore is not implemented.
Thanks for writing up this documentation. A suggestion
for the structure:
I think it would be helpful if we started the documentation
with some introductory text:
* what is Windows Hypervisor Platform?
* why might you want to use it?
* how do you tell QEMU to use it?
before we dive into the details of known issues with our
current support.
thanks
-- PMM
prev parent reply other threads:[~2026-03-26 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 13:51 [PATCH] docs: add WHPX section with initial info Mohamed Mediouni
2026-03-26 14:08 ` Peter Maydell [this message]
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='CAFEAcA9c48xRmOXc7rVnSU4G0v=snP1_LUMZHKkDMYzVd_GfYw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=mohamed@unpredictable.fr \
--cc=pbarbuda@microsoft.com \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox