From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Tamas K Lengyel <tamas.k.lengyel@gmail.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Connor Davis <davisc@ainfosec.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH v3 0/4] x86/iommu: PVH Dom0 workarounds for missing RMRR entries
Date: Fri, 17 Aug 2018 10:53:23 +0200 [thread overview]
Message-ID: <20180817085323.hglub4jq2lqer2rf@mac> (raw)
In-Reply-To: <CABfawhmP2z66b7eamaZ-Kc_D=kGEc-0OFRo6EjVUo2Oc0ePCZg@mail.gmail.com>
On Thu, Aug 16, 2018 at 10:43:54AM -0600, Tamas K Lengyel wrote:
> I double checked and the option is set properly but I'm still getting
> the same non-present entry faults as before. At the moment I don't
> have serial access so not sure how to verify that the option took
> effect. This is my boot info:
>
> [pvh]
> options=loglvl=all guest_loglvl=all dom0_mem=4096M,max:4096M
> dom0_max_vcpus=2 sched=null dom0=pvh iommu=required,debug
> dom0-iommu=relaxed console=vga
> rmrr=0x5f48385=0:0:2.0,0x216183=0:0:2.0,0x70b6d19=0:0:2.0
This is not the correct format. It's:
rmrr=0x5f48385=0:0:2.0;0x216183=0:0:2.0;0x70b6d19=0:0:2.0
Note the ';' between rmrr entries.
Roger.
_______________________________________________
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-17 8:53 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 ` [PATCH v3 3/4] dom0/pvh: change the order of the MMCFG initialization Roger Pau Monne
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é [this message]
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=20180817085323.hglub4jq2lqer2rf@mac \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=davisc@ainfosec.com \
--cc=tamas.k.lengyel@gmail.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).