From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Sergiy Kibrik <Sergiy_Kibrik@epam.com>, xen-devel@lists.xenproject.org
Cc: "Xenia Ragiadakou" <burzalodowa@gmail.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Xenia Ragiadakou" <xenia.ragiadakou@amd.com>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: [XEN PATCH v1 15/15] x86/hvm: make AMD-V and Intel VT-x support configurable
Date: Tue, 16 Apr 2024 10:36:37 +0100 [thread overview]
Message-ID: <bbae1c9d-4c86-415a-963b-a17ff4f3fa4b@citrix.com> (raw)
In-Reply-To: <20240416065012.3470263-1-Sergiy_Kibrik@epam.com>
On 16/04/2024 7:50 am, Sergiy Kibrik wrote:
> From: Xenia Ragiadakou <burzalodowa@gmail.com>
>
> Provide the user with configuration control over the cpu virtualization support
> in Xen by making SVM and VMX options user selectable.
>
> To preserve the current default behavior, both options depend on HVM and
> default to Y.
>
> To prevent users from unknowingly disabling virtualization support, make the
> controls user selectable only if EXPERT is enabled.
> Also make INTEL_IOMMU/AMD_IOMMU options dependant on VMX/SVM options.
Everything else seems ok, but there's no inherent dependency between
VMX/SVM and IOMMUs. There are certain features (HAP/IOMMU pagetable
sharing, posted interrupts) which do depend on both, but the vast
majority of functionality is independent.
It would be a legitimate config (although getting less plausible, these
days) to have PV && IOMMU && !HVM.
Furthermore, randconfig will do a better job without such restrictions
in place.
~Andrew
next prev parent reply other threads:[~2024-04-16 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 6:50 [XEN PATCH v1 15/15] x86/hvm: make AMD-V and Intel VT-x support configurable Sergiy Kibrik
2024-04-16 8:40 ` Teddy Astie
2024-04-16 10:12 ` Sergiy Kibrik
2024-04-16 9:36 ` Andrew Cooper [this message]
2024-04-16 10:16 ` Sergiy Kibrik
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=bbae1c9d-4c86-415a-963b-a17ff4f3fa4b@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Sergiy_Kibrik@epam.com \
--cc=burzalodowa@gmail.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xenia.ragiadakou@amd.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 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.