From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Elena Ufimtseva <elena.ufimtseva@oracle.com>
Cc: kevin.tian@intel.com, tim@xen.org, xen-devel@lists.xen.org,
yang.z.zhang@intel.com, boris.ostrovsky@oracle.com,
roger.pau@citrix.com
Subject: Re: [PATCH RFC 5/5] pvh: dom0 boot option to specify iommu rw ranges
Date: Tue, 17 Feb 2015 13:32:10 +0000 [thread overview]
Message-ID: <54E342DA.4090600@citrix.com> (raw)
In-Reply-To: <54E343D4020000780006095C@mail.emea.novell.com>
On 17/02/15 12:36, Jan Beulich wrote:
>>>> On 14.02.15 at 00:21, <elena.ufimtseva@oracle.com> wrote:
>> On Fri, Feb 13, 2015 at 10:09:39PM +0000, Andrew Cooper wrote:
>>> If I understand the problem correctly, I believe that the correct
>>> solution would be to add a dmar_rmrr[ command line parameter along the
>>> same lines as ivrs_hpet[ and ivrs_ioapic[ which allows the user to
>>> inject corrections to the ACPI tables via the command line.
>> Yes, if we agree to classify those magic locations as being not reported
>> by ACPI machinery.
> One fundamental problem for someone to use this proposed option
> in practice is - how does(s)he learn which region(s) to specify?
Trial and improvement, or find a manual for the affected system.
~Andrew
next prev parent reply other threads:[~2015-02-17 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 18:52 [PATCH RFC 5/5] pvh: dom0 boot option to specify iommu rw ranges Elena Ufimtseva
2015-02-13 22:09 ` Andrew Cooper
2015-02-13 23:21 ` Elena Ufimtseva
2015-02-17 12:36 ` Jan Beulich
2015-02-17 13:32 ` Andrew Cooper [this message]
2015-02-17 13:39 ` Jan Beulich
2015-02-17 14:14 ` Andrew Cooper
2015-02-18 18:15 ` Konrad Rzeszutek Wilk
2015-02-19 9:13 ` Jan Beulich
2015-02-20 20:03 ` Konrad Rzeszutek Wilk
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=54E342DA.4090600@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=elena.ufimtseva@oracle.com \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.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.