All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>,
	Vijay Kilari <vijay.kilari@gmail.com>
Cc: xen-devel@lists.xenproject.org,
	Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>,
	Tim Deegan <tim@xen.org>, Chen Baozi <baozich@gmail.com>,
	Stefano Stabellini <stefano.stabellini@citrix.com>
Subject: Re: [PATCH v3 00/15] xen/arm: Bug fixes for the vGIC
Date: Fri, 20 Feb 2015 11:15:52 +0000	[thread overview]
Message-ID: <54E71768.8050806@linaro.org> (raw)
In-Reply-To: <1424429053.30924.184.camel@citrix.com>

On 20/02/15 10:44, Ian Campbell wrote:
> On Fri, 2015-02-20 at 15:56 +0530, Vijay Kilari wrote:
>> On Fri, Feb 20, 2015 at 3:44 PM, Ian Campbell <ian.campbell@citrix.com> wrote:
>>> On Thu, 2015-02-19 at 18:01 +0000, Julien Grall wrote:
>>>> Based on the discussion, what about waiting until someone complain about
>>>> GICv3 support on Xen 4.5?
>>>
>>> That sounds like a reasonable compromise.
>>
>> If Xen 4.5 claims GICv3 support, then it is better to backport vgic-v3 patches.
>> May be ThunderX is the only platform out there with GICv3 support.
>> At some point of time we might require ThunderX support on 4.5 release.
>> If you are going to backport only on-demand then it should be for now.
> 
> Is ThunderX going to be available to purchase before the 4.6 release in
> the summer?

Even if the GICv3 patches backported, there is no GICv3 ITS, SMMUv2 and
48 cores supports in Xen 4.5. That would mean that there is no MSI
neither PCI-passthrough working.

Given that, there is not much interest to have Xen 4.5 running on
ThunderX. You won't be able to use the full capacity of the board.

I think we should focus on upstreaming all the features required in Xen
4.6 as soon as possible.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-02-20 11:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 14:50 [PATCH v3 00/15] xen/arm: Bug fixes for the vGIC Julien Grall
2015-02-16 14:50 ` [PATCH v3 01/15] xen/arm: vgic-v3: Correctly set GICD_TYPER.IDbits Julien Grall
2015-02-16 14:50 ` [PATCH v3 02/15] xen/arm: vgic-v3: Correctly set GICD_TYPER.CPUNumber Julien Grall
2015-02-16 14:50 ` [PATCH v3 03/15] xen/arm: vgic-v3: Correctly handle GICD_CTLR Julien Grall
2015-02-16 14:50 ` [PATCH v3 04/15] xen/arm: vgic-v3: Correctly handle RAZ/WI registers Julien Grall
2015-02-19 15:55   ` Ian Campbell
2015-02-16 14:50 ` [PATCH v3 05/15] xen/arm: vgic-v3: Correctly implement read into GICR_NSACR Julien Grall
2015-02-16 14:50 ` [PATCH v3 06/15] xen/arm: vgic-v3: Set stride during domain initialization Julien Grall
2015-02-19 15:58   ` Ian Campbell
2015-02-19 16:06     ` Julien Grall
2015-02-16 14:50 ` [PATCH v3 07/15] xen/arm: vgic-v3: Use a struct to describe contiguous rdist regions Julien Grall
2015-02-16 14:50 ` [PATCH v3 08/15] xen/arm: vgic-v3: Emulate correctly the re-distributor Julien Grall
2015-02-19 16:06   ` Ian Campbell
2015-02-16 14:50 ` [PATCH v3 09/15] xen/arm: vgic-v3: Clarify which distributor is used in the common emulation Julien Grall
2015-02-16 14:50 ` [PATCH v3 10/15] xen/arm: vgic-v2: Correctly set GICD_TYPER.CPUNumber Julien Grall
2015-02-16 14:50 ` [PATCH v3 11/15] xen/arm: vgic-v2: Correctly handle RAZ/WI registers Julien Grall
2015-02-19 16:07   ` Ian Campbell
2015-02-16 14:50 ` [PATCH v3 12/15] xen/arm: vgic-v2: Take the lock when writing into GICD_CTLR Julien Grall
2015-02-16 14:50 ` [PATCH v3 13/15] xen/arm: vgic-v2: GICD_I{S, C}PENDR* are only word-accessible Julien Grall
2015-02-16 14:50 ` [PATCH v3 14/15] xen/arm: vgic: Drop iactive, ipend, pendsgi field Julien Grall
2015-02-19 16:09   ` Ian Campbell
2015-02-19 16:15     ` Julien Grall
2015-02-16 14:50 ` [PATCH v3 15/15] xen/arm: gic-v3: Update some comments in the code Julien Grall
2015-02-19 16:09   ` Ian Campbell
2015-02-19 17:21 ` [PATCH v3 00/15] xen/arm: Bug fixes for the vGIC Ian Campbell
2015-02-19 17:34   ` Julien Grall
2015-02-19 17:48     ` Ian Campbell
2015-02-19 18:01       ` Julien Grall
2015-02-20 10:14         ` Ian Campbell
2015-02-20 10:26           ` Vijay Kilari
2015-02-20 10:44             ` Ian Campbell
2015-02-20 11:15               ` Julien Grall [this message]
2015-02-21  5:36                 ` Vijay Kilari
2015-02-20 11:22           ` 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=54E71768.8050806@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Vijaya.Kumar@caviumnetworks.com \
    --cc=baozich@gmail.com \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --cc=vijay.kilari@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.