xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: xen-devel@lists.xen.org, Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Tamas K Lengyel <tklengyel@sec.in.tum.de>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Status of ARM features (Was: Re: Xen 4.6 Development Update (four months reminder))
Date: Wed, 13 May 2015 09:54:25 +0100	[thread overview]
Message-ID: <55531141.1020606@citrix.com> (raw)
In-Reply-To: <E1YsOnt-0004pu-4g@ukmail1.uk.xensource.com>

(trimming the list of cc)

Hi Wei,


On 13/05/2015 06:01, wei.liu2@citrix.com wrote:
> === Hypervisor ARM ===
>
> *  Mem_access for ARM (good)
>     v15 posted
>    -  Tamas K Lengyel

I think all the patches for this patch series has been pushed. Tamas, 
Can you confirm?

>
> *  ITS support (fair )
>    -  Vijaya Kumar K
>
> *  Add ACPI support for arm64 on Xen (fair)
>     RFC posted
>    -  Parth Dixit
>
> *  ARM: reenable support 32-bit userspace running in 64-bit guest (good)
>     v2 posted
>    -  Ian Campbell

It has been pushed to Xen.

>
> *  ARM remote processor iommu module (GPUs + IPUs) (fair)
>     v3 posted
>    -  Andrii Tseglytskyi
>
> *  ARM VM save/restore/live migration (none)
>     Need to rebased against migrationv2 - no code posted.
>    -  None
>
> *  ARM GICv2m support (none)
>    -  Suravee Suthikulanit
>
> *  ARM  PCI passthrough (none)
>    -  Manish Jaggi
>    -  Vijay Kilari

   * ARM GICv2 on GICv3 support (fair)
      - Julien Grall

[..]
> == Deferred ==

[..]

> *  Linux ARM - Device assigment usage in Linux code (arch/arm) non-PCI (none)
>     Depends on Xen pieces which are on the Xen 4.6 list.
>    -  Julien Grall

I think you can drop this item. We don't expect to have code in Linux 
for non-PCI passthrough until we got a real need to do it .

[..]

> == Completed ==

> *  ARM - passthrough of non-PCI (ok)
>    -  Julien Grall

To be fair, this feature is not yet completed. There is some outstanding 
patches on the ML due to build issue.

Regards,

-- 
Julien Grall

  parent reply	other threads:[~2015-05-13  8:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  5:01 Xen 4.6 Development Update (four months reminder) wei.liu2
2015-05-13  5:17 ` Meng Xu
2015-05-13  5:56 ` Chun Yan Liu
2015-05-13  8:56   ` Tamas K Lengyel
2015-05-13  6:18 ` Status of VM event patches (Was: " Razvan Cojocaru
2015-05-13  7:04   ` Jan Beulich
2015-05-13  7:40     ` Razvan Cojocaru
2015-05-13  8:46 ` Yang Hongyang
2015-05-13  8:54 ` Julien Grall [this message]
2015-05-13  9:56 ` Status of soft reset for PVHVM (Was: Xen 4.6 Development Update (four months reminder)) Vitaly Kuznetsov
2015-05-13 11:06 ` Xen 4.6 Development Update (four months reminder) Hu, Robert
2015-05-13 13:49 ` Daniel Kiper
2015-05-14 23:48 ` Status of VMware tools support (Was: Xen 4.6 Development Update (four months reminder)) Don Slutz
2015-05-15 10:38 ` Xen 4.6 Development Update (four months reminder) Ian Campbell
2015-05-16  0:42 ` Status of 'Credit2: hard and soft affinity; [Re: Xen 4.6 Development Update (four months reminder)] Dario Faggioli
2015-05-18  7:07   ` Justin Weaver
2015-05-16  1:15 ` Status of Credit2 and Credit1 [was: " Dario Faggioli
2015-05-19 17:35   ` Wei Liu
2015-05-20 21:09     ` Dario Faggioli

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=55531141.1020606@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=tklengyel@sec.in.tum.de \
    --cc=wei.liu2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).