From: Bertrand Marquis <Bertrand.Marquis@arm.com>
To: tosher 1 <akm2tosher@yahoo.com>
Cc: Jan Beulich <jbeulich@suse.com>,
"roger.pau@citrix.com" <roger.pau@citrix.com>,
"xadimgnik@gmail.com" <xadimgnik@gmail.com>,
"oleksandr_andrushchenko@epam.com"
<oleksandr_andrushchenko@epam.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: PCI passthrough support for PVH mode
Date: Thu, 10 Feb 2022 08:32:06 +0000 [thread overview]
Message-ID: <2CDAD7A1-A628-4491-9DE0-1F4D5D9FF1A7@arm.com> (raw)
In-Reply-To: <303292590.682317.1644477758255@mail.yahoo.com>
Hi Mihrab,
> On 10 Feb 2022, at 07:22, tosher 1 <akm2tosher@yahoo.com> wrote:
>
> Hi Jan,
>
> Thanks for letting me know this status.
>
> I am wondering if PCI passthrough is at least available in Arm for other virtualization modes like PV, HVM, or PVHVM. For example, is it possible for someone to attach a PCI device to a guest domain on an Arm machine and use that domain as a driver domain, like we can do with the Xen on x86?
On arm there is only one virtualization mode which is equivalent to x86 HVM.
Regarding PCI passthrough on arm, this is currently a work in progress that is being upstream so it is not available for now.
Once it will be merged in Xen, it will be possible to assign a PCI device to a guest so you could then make a “driver domain” using the functionality.
Regards
Bertrand
>
> Please let me know.
>
> Regards,
> Mehrab
>
>
>
>
> On Monday, February 7, 2022, 02:57:45 AM EST, Jan Beulich <jbeulich@suse.com> wrote:
>
>
>
>
>
> On 06.02.2022 06:59, tosher 1 wrote:
>
>> Back in the year 2020, I was inquiring into the status of PCI passthrough support for PVH guests. At that time, Arm people were working on using vPCI for guest VMs. The expectation was to port that implementation to x86 once ready.
>>
>> I was wondering if there is any update on this. Does Xen support PCI passthrough for PVH mode yet? Please let me know.
>
>
> The Arm work is still WIP, and in how far it's going to be straightforward to
> re-use that code for x86 is still unclear (afaict at least).
>
> Jan
>
>
>
next prev parent reply other threads:[~2022-02-10 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <709142925.628001.1644127197288.ref@mail.yahoo.com>
2022-02-06 5:59 ` PCI passthrough support for PVH mode tosher 1
2022-02-07 7:57 ` Jan Beulich
2022-02-10 7:22 ` tosher 1
2022-02-10 7:29 ` Jan Beulich
2022-02-10 8:32 ` Bertrand Marquis [this message]
2022-02-10 18:02 ` tosher 1
2022-02-10 23:12 ` Julien Grall
2022-02-11 5:45 ` tosher 1
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=2CDAD7A1-A628-4491-9DE0-1F4D5D9FF1A7@arm.com \
--to=bertrand.marquis@arm.com \
--cc=akm2tosher@yahoo.com \
--cc=jbeulich@suse.com \
--cc=oleksandr_andrushchenko@epam.com \
--cc=roger.pau@citrix.com \
--cc=xadimgnik@gmail.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.