From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>,
<xen-devel@lists.xenproject.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Paul Durrant <pdurrant@gmail.com>,
Jan Beulich <jbeulich@suse.com>, Wei Liu <wl@xen.org>
Subject: Re: [Xen-devel] [XEN PATCH for-4.13 v2 9/9] libxl/xl: Overhaul passthrough setting logic
Date: Fri, 11 Oct 2019 10:47:58 +0100 [thread overview]
Message-ID: <17defd97-e6b8-761e-0bd8-0aa0a2de7bed@citrix.com> (raw)
In-Reply-To: <20191010151111.22125-10-ian.jackson@eu.citrix.com>
On 10/10/2019 16:11, Ian Jackson wrote:
> diff --git a/tools/libxl/libxl_create.c b/tools/libxl/libxl_create.c
> index 69971c97b6..fccb6a6271 100644
> --- a/tools/libxl/libxl_create.c
> +++ b/tools/libxl/libxl_create.c
> @@ -968,6 +957,50 @@ int libxl__domain_config_setdefault(libxl__gc *gc,
> goto error_out;
> }
>
> + bool need_pt = d_config->num_pcidevs || d_config->num_dtdevs;
> + if (c_info->passthrough == LIBXL_PASSTHROUGH_UNKNOWN) {
> + c_info->passthrough = need_pt
> + ? LIBXL_PASSTHROUGH_ENABLED : LIBXL_PASSTHROUGH_DISABLED;
> + }
> +
> + bool iommu_enabled = physinfo.cap_hvm_directio;
> + if (c_info->passthrough != LIBXL_PASSTHROUGH_DISABLED && !iommu_enabled) {
> + LOGD(ERROR, domid,
> + "ERROR: passthrough not supported on this platform\n");
> + ret = ERROR_INVAL;
> + goto error_out;
> + }
> +
> + if (c_info->passthrough == LIBXL_PASSTHROUGH_DISABLED && need_pt) {
> + LOGD(ERROR, domid,
> + "passthrough disabled but devices are specified");
This is the only log message which isn't prefixed with ERROR:
> + ret = ERROR_INVAL;
> + goto error_out;
> + }
> +
> + const char *whynot_pt_share =
> + c_info->type == LIBXL_DOMAIN_TYPE_PV ? "not valid for PV domain" :
> + !physinfo.cap_iommu_hap_pt_share ? "not supported on this platform" :
> + NULL;
This is a little more complicated.
For ARM, doesn't libxl treat guests as PV, or has that been fixed now?
ARM's only passthrough mode is PT_SHARE.
On x86 for PVH, passthrough doesn't work yet. This may not be an
argument against constructing the guest suitably, but we should check
that things don't explode in new and interesting ways from this change.
For x86 HVM, PT_SHARE is only available for HAP guests, so shadow guests
must use PT_SYNC.
> +
> + if (c_info->passthrough == LIBXL_PASSTHROUGH_ENABLED) {
> + assert(iommu_enabled);
> + c_info->passthrough = whynot_pt_share
> + ? LIBXL_PASSTHROUGH_SYNC_PT : LIBXL_PASSTHROUGH_SHARE_PT;
> + }
> +
> + if (c_info->passthrough == LIBXL_PASSTHROUGH_SHARE_PT && whynot_pt_share) {
> + LOGD(ERROR, domid,
> + "ERROR: passthrough=\"share_pt\" %s\n",
> + whynot_pt_share);
> + ret = ERROR_INVAL;
> + goto error_out;
> + }
> +
> + /* An explicit setting should now have been chosen */
> + assert(c_info->passthrough != LIBXL_PASSTHROUGH_UNKNOWN);
> + assert(c_info->passthrough != LIBXL_PASSTHROUGH_ENABLED);
This is confusing. I think it would help if ...
> +
> /* If target_memkb is smaller than max_memkb, the subsequent call
> * to libxc when building HVM domain will enable PoD mode.
> */
> diff --git a/tools/libxl/libxl_types.idl b/tools/libxl/libxl_types.idl
> index 3ac9494b80..2441c0c233 100644
> --- a/tools/libxl/libxl_types.idl
> +++ b/tools/libxl/libxl_types.idl
> @@ -266,8 +266,9 @@ libxl_vkb_backend = Enumeration("vkb_backend", [
> libxl_passthrough = Enumeration("passthrough", [
> (0, "unknown"),
> (1, "disabled"),
> - (2, "sync_pt"),
> - (3, "share_pt"),
> + (2, "enabled"),
> + (3, "sync_pt"),
> + (4, "share_pt"),
... this had a comment explaining enabled is just interim value.
(2, "enabled"), # becomes {sync,share}_pt once defaults are evaluated
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-10-11 9:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 15:11 [Xen-devel] [XEN PATCH for-4.13 v2 0/9] libxl memkb & pt defaulting Ian Jackson
2019-10-10 15:11 ` [Xen-devel] [XEN PATCH for-4.13 v2 1/9] libxl: Offer API versions 0x040700 and 0x040800 Ian Jackson
2019-11-25 18:44 ` Jim Fehlig
2019-10-10 15:11 ` [Xen-devel] [XEN PATCH for-4.13 v2 2/9] xl: Pass libxl_domain_config to freemem(), instead of b_info Ian Jackson
2019-10-10 15:11 ` [Xen-devel] [XEN PATCH for-4.13 v2 3/9] libxl: libxl__domain_config_setdefault: New function Ian Jackson
2019-10-10 15:11 ` [Xen-devel] [XEN PATCH for-4.13 v2 4/9] libxl: libxl_domain_need_memory: Make it take a domain_config Ian Jackson
2019-10-10 15:11 ` [Xen-devel] [XEN PATCH for-4.13 v2 5/9] libxl: Move shadow_memkb and iommu_memkb defaulting into libxl Ian Jackson
2019-10-10 15:11 ` [Xen-devel] [XEN PATCH for-4.13 v2 6/9] libxl: Remove/deprecate libxl_get_required_*_memory from the API Ian Jackson
2019-10-10 15:11 ` [Xen-devel] [XEN PATCH for-4.13 v2 7/9] libxl: create: setdefault: Make libxl_physinfo info[1] Ian Jackson
2019-10-11 9:26 ` Wei Liu
2019-10-10 15:11 ` [Xen-devel] [XEN PATCH for-4.13 v2 8/9] libxl: create: setdefault: Move physinfo into config_setdefault Ian Jackson
2019-10-11 9:26 ` Wei Liu
2019-10-10 15:11 ` [Xen-devel] [XEN PATCH for-4.13 v2 9/9] libxl/xl: Overhaul passthrough setting logic Ian Jackson
2019-10-11 9:26 ` Wei Liu
2019-10-11 9:47 ` Andrew Cooper [this message]
2019-10-11 10:10 ` Ian Jackson
2019-10-11 11:00 ` Julien Grall
2019-10-11 13:33 ` Ian Jackson
2019-10-11 12:23 ` George Dunlap
2019-10-11 13:31 ` Ian Jackson
2019-10-11 13:55 ` Jürgen Groß
2019-10-11 16:34 ` Ian Jackson
2019-10-14 7:59 ` Paul Durrant
2019-10-14 16:09 ` Ian Jackson
2019-10-14 16:44 ` Wei Liu
2019-10-14 16:48 ` Ian Jackson
2019-10-14 16:51 ` [Xen-devel] [XEN PATCH v4 for-4.13 10/10] libxl/xl: Overhaul passthrough setting logic " Ian Jackson
2019-10-14 17:06 ` Anthony PERARD
2019-10-14 16:59 ` [Xen-devel] [XEN PATCH for-4.13 v2 9/9] libxl/xl: Overhaul " Anthony PERARD
2019-10-15 11:13 ` Wei Liu
2019-10-10 15:18 ` [Xen-devel] [XEN PATCH for-4.13 v2 0/9] libxl memkb & pt defaulting Ian Jackson
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=17defd97-e6b8-761e-0bd8-0aa0a2de7bed@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=pdurrant@gmail.com \
--cc=wl@xen.org \
--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 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).