From: Roger Pau Monne <roger.pau@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: [PATCH v3 3/4] dom0/pvh: change the order of the MMCFG initialization
Date: Tue, 7 Aug 2018 16:02:42 +0200 [thread overview]
Message-ID: <20180807140243.11265-4-roger.pau@citrix.com> (raw)
In-Reply-To: <20180807140243.11265-1-roger.pau@citrix.com>
So it's done before the iommu is initialized. This is required in
order to be able to fetch the MMCFG regions from the domain struct.
No functional change.
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
---
Changes since v1:
- New in this version.
---
Cc: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
---
xen/arch/x86/hvm/dom0_build.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/xen/arch/x86/hvm/dom0_build.c b/xen/arch/x86/hvm/dom0_build.c
index f0cd63b1ec..5065729106 100644
--- a/xen/arch/x86/hvm/dom0_build.c
+++ b/xen/arch/x86/hvm/dom0_build.c
@@ -1100,6 +1100,13 @@ int __init dom0_construct_pvh(struct domain *d, const module_t *image,
return rc;
}
+ /*
+ * NB: MMCFG initialization needs to be performed before iommu
+ * initialization so the iommu code can fetch the MMCFG regions used by the
+ * domain.
+ */
+ pvh_setup_mmcfg(d);
+
iommu_hwdom_init(d);
rc = pvh_load_kernel(d, image, image_headroom, initrd, bootstrap_map(image),
@@ -1124,8 +1131,6 @@ int __init dom0_construct_pvh(struct domain *d, const module_t *image,
return rc;
}
- pvh_setup_mmcfg(d);
-
printk("WARNING: PVH is an experimental mode with limited functionality\n");
return 0;
}
--
2.18.0
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-08-07 14:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 14:02 [PATCH v3 0/4] x86/iommu: PVH Dom0 workarounds for missing RMRR entries Roger Pau Monne
2018-08-07 14:02 ` [PATCH v3 1/4] iommu: introduce dom0-iommu option Roger Pau Monne
2018-08-07 14:02 ` [PATCH v3 2/4] iommu: make iommu_inclusive_mapping a suboption of dom0-iommu Roger Pau Monne
2018-08-07 14:20 ` Paul Durrant
2018-08-07 14:02 ` Roger Pau Monne [this message]
2018-08-07 14:02 ` [PATCH v3 4/4] x86/iommu: add reserved dom0-iommu option to map reserved memory ranges Roger Pau Monne
2018-08-07 14:35 ` Paul Durrant
2018-08-08 9:53 ` Roger Pau Monné
2018-08-08 9:55 ` Jan Beulich
2018-08-07 14:29 ` [PATCH v3 0/4] x86/iommu: PVH Dom0 workarounds for missing RMRR entries Tamas K Lengyel
2018-08-07 14:37 ` Roger Pau Monné
2018-08-07 14:45 ` Tamas K Lengyel
2018-08-07 15:08 ` Roger Pau Monné
2018-08-07 16:04 ` Tamas K Lengyel
2018-08-07 16:14 ` Jan Beulich
2018-08-07 16:45 ` Tamas K Lengyel
2018-08-07 16:55 ` Tamas K Lengyel
2018-08-08 8:25 ` Roger Pau Monné
2018-08-08 9:54 ` Jan Beulich
2018-08-15 1:00 ` Tamas K Lengyel
2018-08-15 6:40 ` Jan Beulich
2018-08-16 16:43 ` Tamas K Lengyel
2018-08-17 8:10 ` Jan Beulich
2018-08-17 8:53 ` Roger Pau Monné
2018-08-07 15:20 ` Andrew Cooper
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=20180807140243.11265-4-roger.pau@citrix.com \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.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 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).