From: David Vrabel <david.vrabel@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
"Mukesh Rathor" <mukesh.rathor@oracle.com>,
"Jan Beulich" <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3] docs: add PVH specification
Date: Mon, 29 Sep 2014 18:45:01 +0100 [thread overview]
Message-ID: <54299A9D.6030600@citrix.com> (raw)
In-Reply-To: <54299901.7060202@citrix.com>
On 29/09/14 18:38, Roger Pau Monné wrote:
> El 26/09/14 a les 2.00, Mukesh Rathor ha escrit:
>>
>> We map all non-ram regions for dom0 1:1 till the last e820 entry. If the
>> last entry ends below 4GB, then the remaining space is mapped 1:1 upto 4GB.
>> This implies that if there is any region beyond the last e820 entry above
>> 4GB, it is not mapped.
>> TODO: Map region beyond last e820 if it's above 4GB. Add support for domUs
>> with pci passthru.
>
> The document has already been committed, could you please send a patch
> against it to clarify this section?
I'd much rather see a patch documenting how PVH is going work with
devices with high MMIO regions...
Or to put it another way, a patch to the spec document is a good first
step in any PVH ABI changes.
David
prev parent reply other threads:[~2014-09-29 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 17:19 [PATCH v3] docs: add PVH specification Roger Pau Monne
2014-09-20 19:15 ` Konrad Rzeszutek Wilk
2014-09-22 11:16 ` Jan Beulich
2014-09-22 13:40 ` Konrad Rzeszutek Wilk
2014-09-22 11:36 ` Roger Pau Monné
2014-09-22 14:02 ` Konrad Rzeszutek Wilk
2014-09-22 14:08 ` Jan Beulich
2014-09-23 0:38 ` Mukesh Rathor
2014-09-23 13:16 ` Jan Beulich
2014-09-26 0:00 ` Mukesh Rathor
2014-09-26 6:32 ` Jan Beulich
2014-09-29 17:38 ` Roger Pau Monné
2014-09-29 17:45 ` David Vrabel [this message]
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=54299A9D.6030600@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=mukesh.rathor@oracle.com \
--cc=roger.pau@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.