From: "Jan Beulich" <JBeulich@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Brian Woods <brian.woods@amd.com>
Subject: Re: [PATCH v4 1/4] iommu: introduce dom0-iommu option
Date: Thu, 09 Aug 2018 05:46:42 -0600 [thread overview]
Message-ID: <5B6C29A202000078001DC882@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <20180809105121.uts2ur4m7xpdmucm@mac>
>>> On 09.08.18 at 12:51, <roger.pau@citrix.com> wrote:
> On Thu, Aug 09, 2018 at 04:29:51AM -0600, Jan Beulich wrote:
>> >>> On 09.08.18 at 12:01, <roger.pau@citrix.com> wrote:
>> > In fact I think this would be clearer if something like:
>> >
>> > enum {
>> > NONE,
>> > RELAXED,
>> > STRICT,
>> > } iommu_hwdom = RELAXED;
>> >
>> > Was used instead of iommu_dom0_passthrough and iommu_dom0_strict.
>>
>> Fine with me.
>
> Switching to a single enum also means that the last dom0-iommu = [
> none | strict | relaxed ] will be the one enforced, so I could keep
> them as-is, and add:
>
> "Note that all the above options are mutually exclusive and the last
> one found on the command line will be the one to take effect."
Right. I don't think the second half of the sentence is needed -
that's what happens for most other options as well.
Jan
_______________________________________________
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-09 11:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 10:07 [PATCH v4 0/4] 86/iommu: PVH Dom0 workarounds for missing RMRR entries Roger Pau Monne
2018-08-08 10:07 ` [PATCH v4 1/4] iommu: introduce dom0-iommu option Roger Pau Monne
2018-08-08 12:10 ` Jan Beulich
2018-08-08 15:50 ` Roger Pau Monné
2018-08-09 7:00 ` Jan Beulich
2018-08-09 10:01 ` Roger Pau Monné
2018-08-09 10:29 ` Jan Beulich
2018-08-09 10:51 ` Roger Pau Monné
2018-08-09 11:46 ` Jan Beulich [this message]
2018-08-09 10:18 ` Paul Durrant
2018-08-08 10:07 ` [PATCH v4 2/4] iommu: make iommu_inclusive_mapping a suboption of dom0-iommu Roger Pau Monne
2018-08-08 12:32 ` Jan Beulich
2018-08-08 16:09 ` Roger Pau Monné
2018-08-09 7:17 ` Jan Beulich
2018-08-08 10:07 ` [PATCH v4 3/4] dom0/pvh: change the order of the MMCFG initialization Roger Pau Monne
2018-08-08 12:35 ` Jan Beulich
2018-08-10 10:04 ` Roger Pau Monné
2018-08-10 11:41 ` Jan Beulich
2018-08-08 10:07 ` [PATCH v4 4/4] x86/iommu: add reserved dom0-iommu option to map reserved memory ranges Roger Pau Monne
2018-08-08 13:15 ` Jan Beulich
2018-08-08 16:18 ` Roger Pau Monné
2018-08-09 7:36 ` Jan Beulich
2018-08-09 10:23 ` Roger Pau Monné
2018-08-09 10:33 ` Jan Beulich
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=5B6C29A202000078001DC882@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=brian.woods@amd.com \
--cc=julien.grall@arm.com \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.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 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.