From: Julien Grall <julien.grall@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>
Cc: "Prasun.kapoor@cavium.com" <Prasun.kapoor@cavium.com>,
Ian Campbell <ian.campbell@citrix.com>,
Manish Jaggi <mjaggi@caviumnetworks.com>,
Vijaya Kumar <Vijaya.Kumar@caviumnetworks.com>,
JulienGrall <julien.grall@linaro.org>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: PCI Pass-through in Xen ARM: Draft 4
Date: Fri, 14 Aug 2015 15:45:33 +0100 [thread overview]
Message-ID: <55CDFF0D.4010101@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1508141534110.2672@kaball.uk.xensource.com>
On 14/08/15 15:37, Stefano Stabellini wrote:
> On Fri, 14 Aug 2015, Jan Beulich wrote:
>>>>> On 14.08.15 at 16:03, <stefano.stabellini@eu.citrix.com> wrote:
>>> On Fri, 14 Aug 2015, Jan Beulich wrote:
>>>>>>> On 14.08.15 at 15:21, <stefano.stabellini@eu.citrix.com> wrote:
>>>>> On Fri, 14 Aug 2015, Jan Beulich wrote:
>>>>>> it's even less clear how you'd expect to suppress this in other guest
>>>>>> OSes (Windows - afaik - being able to run on ARM certainly makes it
>>>>>> a candidate guest, even if maybe this doesn't work today), namely
>>>>>> such not having any pcifront. And I hope this design discussion isn't
>>>>>> limiting itself to Linux guests.
>>>>>
>>>>> We'll write down in the ABI documentation that BARs reassignments are
>>>>> not supported.
>>>>
>>>> I.e. guests doing so Will Not Work (TM), with users (usually not reading
>>>> ABI docs) learning it the hard way. Not nice, but a way to handle it.
>>>
>>> The target of the ABI docs is not users, but kernel developers, who
>>> should most definitely read them and fix their kernels.
>>
>> ??? (We're talking of unmodified, closed source OSes here.)
>
> If you are thinking of Windows for ARM64, there isn't one yet. When/if
> it will become available, there are going to be a number of issues to
> address before we can run it as a guest on Xen on ARM with the current
> architecture which doesn't do emulation. I am hopeful that we'll be able
> to have a discussion on ABI issues such as this one.
It may be worth to read [1] where the Xen ARM architecture is explained.
Regards,
[1]
http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions_whitepaper
--
Julien Grall
next prev parent reply other threads:[~2015-08-14 14:45 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 9:42 PCI Pass-through in Xen ARM: Draft 4 Manish Jaggi
2015-08-13 10:37 ` Julien Grall
2015-09-02 15:19 ` Ian Campbell
2015-09-02 15:40 ` Julien Grall
2015-08-13 15:29 ` Jan Beulich
2015-08-13 17:01 ` Ian Campbell
2015-08-14 9:26 ` Jan Beulich
2015-08-14 13:21 ` Stefano Stabellini
2015-08-14 13:58 ` Jan Beulich
2015-08-14 14:03 ` Stefano Stabellini
2015-08-14 14:34 ` Jan Beulich
2015-08-14 14:37 ` Stefano Stabellini
2015-08-14 14:45 ` Julien Grall [this message]
2015-08-14 15:15 ` Jan Beulich
2015-08-14 15:24 ` Stefano Stabellini
2015-09-02 14:45 ` Ian Campbell
2015-09-02 14:52 ` Jan Beulich
2015-09-02 15:07 ` Ian Campbell
2015-09-02 14:47 ` Ian Campbell
2015-08-14 15:38 ` Stefano Stabellini
2015-08-14 18:58 ` Jaggi, Manish
2015-08-16 23:59 ` Stefano Stabellini
2015-09-02 14:57 ` Ian Campbell
2015-09-02 15:06 ` Jan Beulich
2015-08-31 12:36 ` Manish Jaggi
2015-09-01 7:32 ` Jan Beulich
2015-09-02 12:08 ` Manish Jaggi
2015-09-02 12:59 ` Julien Grall
2015-09-02 13:46 ` Ian Campbell
2015-09-02 15:03 ` Ian Campbell
2015-09-02 15:03 ` Ian Campbell
2015-09-01 16:15 ` Stefano Stabellini
2015-09-10 1:12 ` Julien Grall
2015-09-15 18:58 ` Jaggi, Manish
2015-09-15 21:18 ` David Daney
2015-09-16 12:58 ` Julien Grall
2015-09-19 20:24 ` Manish Jaggi
2015-09-19 20:48 ` Julien Grall
2015-09-19 21:51 ` Daney, David
2015-09-21 10:17 ` Julien Grall
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=55CDFF0D.4010101@citrix.com \
--to=julien.grall@citrix.com \
--cc=JBeulich@suse.com \
--cc=Prasun.kapoor@cavium.com \
--cc=Vijaya.Kumar@caviumnetworks.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=mjaggi@caviumnetworks.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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.