From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <JGross@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: PCI-passthrough for 32 bit guests and high MMIO addresses
Date: Fri, 21 Nov 2014 16:01:50 +0000 [thread overview]
Message-ID: <546F61EE.90108@citrix.com> (raw)
In-Reply-To: <546F6FA30200007800049E00@mail.emea.novell.com>
On 21/11/14 16:00, Jan Beulich wrote:
>>>> On 21.11.14 at 16:48, <david.vrabel@citrix.com> wrote:
>> On 21/11/14 15:38, Jan Beulich wrote:
>>>>>> On 21.11.14 at 16:01, <andrew.cooper3@citrix.com> wrote:
>>>> On 21/11/14 14:54, Jan Beulich wrote:
>>>>>>>> On 21.11.14 at 15:39, <JGross@suse.com> wrote:
>>>>>> Trying to do PCI-passthrough with a 32-bit pv-domain I passed the
>>>>>> wrong device to the domain. The MMIO address was too large for a
>>>>>> MFN of a 32-bit system (it was 380003200000-3800036fffff).
>>>>>>
>>>>>> Instead of rejecting the operation Xen tried to perform it resulting
>>>>>> in a (quite understandable) failure in the domU.
>>>>>>
>>>>>> I think either the hypervisor or the tools should refuse to do
>>>>>> PCI-passthrough in this case.
>>>>> What's wrong with this large an address?
>>>>
>>>> It is wider than 44 bits, so doesn't fit in a 32bit pfn for p2m/m2p
>>>> update operations.
>>>
>>> MMIO regions don't go into these tables.
>>
>> They do in upstream kernels.
>
> Which still is no reason to make the hypervisor or tools refuse
> anything here. A check like the one Jürgen is asking for should
> be added only if something in the public interface prevents this
> from working; everything beyond should be dealt with by the
> respective kernel.
I agree.
David
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-11-21 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 14:39 PCI-passthrough for 32 bit guests and high MMIO addresses Juergen Gross
2014-11-21 14:45 ` Andrew Cooper
2014-11-21 15:04 ` Juergen Gross
2014-11-21 15:29 ` Andrew Cooper
2014-11-21 14:54 ` Jan Beulich
2014-11-21 15:01 ` Andrew Cooper
2014-11-21 15:38 ` Jan Beulich
2014-11-21 15:48 ` David Vrabel
2014-11-21 16:00 ` Jan Beulich
2014-11-21 16:01 ` David Vrabel [this message]
[not found] ` <546F60470200007800049D06@suse.com>
2014-11-21 15:17 ` Juergen Gross
2014-11-21 15:40 ` 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=546F61EE.90108@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=andrew.cooper3@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.