[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xen on rk3399


  • To: Brad Churchwell <brad@xxxxxxxxxxxx>
  • From: Bertrand Marquis <Bertrand.Marquis@xxxxxxx>
  • Date: Thu, 14 Jul 2022 09:44:27 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 63.35.35.123) smtp.rcpttodomain=lists.xen.org smtp.mailfrom=arm.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=arm.com; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=arm.com] dkim=[1,1,header.d=arm.com] dmarc=[1,1,header.from=arm.com])
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
  • Arc-message-signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=S36hyEWjsytbeUC8SKEf+oYA+nwYUEcZ7pFbvyOdqgs=; b=oHP1hXGyML4U3AMRh/oVIt/1wte8wPPIfJr3xJbsNUbNZwJBp96yCI60ZgQnaKmHZfcvaJl/F8D0y4cstpk42te8vurnXAtQBGAfo3892FfXWTHkUWigTE/6dLzRzUJFgxm9G4R2KTVXq/nBiP5MaA4mXBkQe4jXtmNhMuw5q8FylpppszpFwZ/zeLdXjkT/JZZx3qYamxw6TRjXy1bNuVAR6UxGkGmVbZr63z/xj78tLR+db/VEdFUjOeqsARW1ipzFxi6ky8M7IOHan9ZJpHYtZuZq52cgMSDnSgR4MD3TEAigS3HLap+bsqAt+zxM6JMMnmOIc8HIELeJXu/dVA==
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=S36hyEWjsytbeUC8SKEf+oYA+nwYUEcZ7pFbvyOdqgs=; b=E5CFFXBpAo9Fc3SS2h2QEdpRTeBut/JqAdTDMwB0rSF8quyOERGJx+fP7R9+BN/pCb+ns6DzQh3/RifZrD1NiRJwR1CespWXStq/10A8pNiXaS48GVdGbkCCO91C4P8zrmVCLYE/gyUODFlaprOI4/FEdV1vsEr3Epeglln3+aT7FH1s0Dhee3dHPNUXE6bFsPqIXqop1LJKlMYCaaDDSHMjAW/WY3tY4rI/R+W7LFR2xL+dq4VqHhJFUGpCjqIGynyRmLT/XvWs0CkOkyKkdrpTy0mxIlcIj4+wFKlS0o/ByLC6hk0/jSnZ1FwU7OGo9uapfnI3UbmDCXyQOTXUWw==
  • Arc-seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; b=AQHD6kAe3dRlH8ApfSR83BtEx/yUG3FZYmhNLUFFbUUAW6Ch5aLjh3dZMt2AnPUm4j9ELdE+PTlbuH4DAbdyHkHNtfphXHGx38UeB4vmLowIJD/BCOTpJyASRc5vmLuLjPztDEJJMC+WZDQGJy2LCGJJFejuiGpY8usTyqp+wRBy4UPn13u/Vs83cF6Z7tSeR8gzYeuhe4jJK4UdC2YsH4PRrYR7XGDV2TYDf3Ei1wnm7wk+8LDSGR8CNccw2wZ/uHunic+DyvgZMqtSR+oTSN1pdmY2bhv9KLoy3981DQgdYvpiA4xnO4SXX5vT7voOfeuz4LjqP08OSsOrr+aCjQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KoBnZ/aVVfbwSCALut2qQN5PwJq2o/MORRySJ5kEuhd6PgYkAMzqpUl8KkGhqtEUCVM479KjhhKaRJjTHDN9EWa777v0+Z1AvD1zQZWytRfWp9l/1uzbonNiBPFmePh2SqEzRzJ1hBjmtlbbpaE7wMHMAJNDmCVMlVe6ShFdcTTekQ6VV0zS7BZgnJ017tvMaoeRPTG+QCa3TwQJ+qXuScLv9wNCk3Dt04rmxUsvVlIwI/MEhMAT03/SnNaQyRw5rcI/rglxDWKHGAJ5Akc81wdRFEh+sGiX7j/ENHTCF5T8SZeLiR6YmO1fmuBW959ZGlUBxvLDtsVUhYyaZwj5hA==
  • Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
  • Cc: "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • Delivery-date: Thu, 14 Jul 2022 09:44:52 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Nodisclaimer: true
  • Original-authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
  • Thread-index: AQHYlaRzw0VI/DSwq0Ot3R+564rcea161i+AgAAPUoCAAANZAIAAA34AgAFZWwCAAAjiAIABUr+A
  • Thread-topic: Xen on rk3399

Hi Brad

> On 13 Jul 2022, at 14:32, Brad Churchwell <brad@xxxxxxxxxxxx> wrote:
>
> Hi Bertrand,
>
> I did this yesterday and it does indeed silence the warnings saying to 
> disable those cores, however the IRQ errors still remain.

Can you check to which domain it belongs ? If it belongs to the domain with 
little cores this might explain it.

>
> I think I made some progress by changing "interrupts = <GIC_PPI 9 
> IRQ_TYPE_LEVEL_HIGH 0>;" to "interrupts = <GIC_SPI 9 IRQ_TYPE_LEVEL_HIGH 
> 0>;". I noticed when trying to use XEN-4.10 that it said "IRQ only through 
> SPI" and failed to boot XEN where 4.17 unstable boots without this error. Now 
> that I changed GIC_PPI to GIC_SPI, I get the following output:

You cannot change a Per Processor Interrupt into an SPI those are different 
kind of interrupts (please check the GIC reference manual for more explanations 
on those principles).

You have a board specific PCI controller and it could be that the ITS/MSI 
implementation has some specific parts which are not supported by Xen.
It will be hard for me to provide more support here and I would suggest to try 
to explain your problem in Xen-user mailing list instead of xen-devel, maybe 
someone did try xen on this board.


Cheers
Bertrand

IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.