From: Vijay Kilari <vijay.kilari@gmail.com>
To: Julien Grall <julien.grall@citrix.com>
Cc: Wei Liu <Wei.Liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>,
manish.jaggi@caviumnetworks.com,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Requesting for freeze exception for ARM/ITS patches
Date: Tue, 14 Jul 2015 14:54:21 +0530 [thread overview]
Message-ID: <CALicx6tUhcc+8tQMdBVZatGobDckqt5=uUextxi=uZPeCCfb6A@mail.gmail.com> (raw)
In-Reply-To: <55A0B96D.4030804@citrix.com>
Hi Ian,
On Sat, Jul 11, 2015 at 12:06 PM, Julien Grall <julien.grall@citrix.com> wrote:
> Hi,
>
> On 10/07/2015 17:52, Ian Campbell wrote:
>>
>> On Fri, 2015-07-10 at 12:01 +0100, Jan Beulich wrote:
>>>>>>
>>>>>> On 10.07.15 at 12:46, <vijay.kilari@gmail.com> wrote:
>>>>
>>>> I would like to have freeze exception for ITS feature on ARM64.
>>>> Design got freeze few weeks back and I have sent v4 version of patch
>>>> series
>>>> today.
>>>>
>>>> This patches will not impact any generic code of other platforms and
>>>> have
>>>> minor
>>>> changes generic arm related code. Also these patches are only for
>>>> ARM64 platform.
>>>>
>>>> These patches are pre-requisite for PCI support / Pass-through support
>>>> on ARM64 platforms.
>>>
>>>
>>> But what good will it do for the release when it's only a prereq for
>>> further work?
>>
>>
>> I think this may have been true of v3 but I think it is underselling v4.
>> AFAICT with the final patch in v4 Xen will actually be capable of
>> booting on a ThunderX platform and starting guests. It will simply lack
>> PCI passthrough capabilities (as do all ARM platforms today).
>
>
> I think you are overselling this patch series. PCI devices provide the
> support of both legacy interrupt and MSI.
>
> The former is handled by your PCI patch series [1] pushed upstreamed few
> days ago. This should be enough for booting ThunderX and creating guests.
>
> The ITS add the support of MSI which is useful for performance question and
> PCI passthrough.
>
>> I think that's a reasonable thing to try and get into 4.6.
>
>
> If we ever decide to get this into 4.6 we need some guarantee from Cavium to
> finish the work afterwards.
>
> Regards,
>
> [1] http://lists.xen.org/archives/html/xen-devel/2015-07/msg00656.html
I am trying to boot latest staging Xen branch on ThunderX with ITS patches.
I face below issues with above [1] patch series
1) If pcie support only MSI, then INT mapping is not specified in DT. However
the below code returns error if INT mapping is not found and does not map.
In ThunderX INT mapping is not specified for pcie nodes.
static int map_device_children(struct domain *d,
const struct dt_device_node *dev)
{
int ret;
if ( dt_device_type_is_equal(dev, "pci") )
{
DPRINT("Mapping children of %s to guest\n", dt_node_full_name(dev));
ret = dt_for_each_irq_map(dev, &map_dt_irq_to_domain, d);
if ( ret < 0 )
return ret; // Returns error here
...
}
2) Dom0 fails to boot with GICv3. It hangs just after GICv3 initialization.
To know which is last distributor/re-distributor registers read, I
have added debug prints
in GICD & GICR mmio handlers in Xen. But with your patches Linux driver never
traps to Xen to read/write GICD/GICR registers. If I revert back this
patch series,
I see the traps.
Regards
Vijay
next prev parent reply other threads:[~2015-07-14 9:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 10:46 Requesting for freeze exception for ARM/ITS patches Vijay Kilari
2015-07-10 11:01 ` Jan Beulich
2015-07-10 15:52 ` Ian Campbell
2015-07-11 6:36 ` Julien Grall
2015-07-14 9:24 ` Vijay Kilari [this message]
2015-07-14 9:50 ` Ian Campbell
2015-07-14 9:59 ` Vijay Kilari
2015-07-10 16:07 ` Ian Campbell
2015-07-11 7:18 ` Julien Grall
2015-07-11 9:21 ` Ian Campbell
2015-07-13 21:58 ` Julien Grall
2015-07-14 10:02 ` Vijay Kilari
2015-07-14 13:31 ` Ian Campbell
2015-07-13 13:55 ` Wei Liu
2015-07-13 13:56 ` Wei Liu
2015-07-13 17:24 ` Stefano Stabellini
2015-07-13 21:50 ` Julien Grall
2015-07-14 7:49 ` Ian Campbell
2015-07-14 10:51 ` Stefano Stabellini
2015-07-16 14:08 ` Wei Liu
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='CALicx6tUhcc+8tQMdBVZatGobDckqt5=uUextxi=uZPeCCfb6A@mail.gmail.com' \
--to=vijay.kilari@gmail.com \
--cc=JBeulich@suse.com \
--cc=Prasun.Kapoor@caviumnetworks.com \
--cc=Wei.Liu2@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=manish.jaggi@caviumnetworks.com \
--cc=stefano.stabellini@citrix.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.