From: Florian Fainelli <f.fainelli@gmail.com>
To: Julien Grall <julien@xen.org>, Christoph Hellwig <hch@lst.de>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org,
osstest service owner <osstest-admin@xenproject.org>,
iommu@lists.linux-foundation.org,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: Regression when booting 5.15 as dom0 on arm64 (WAS: Re: [linux-linus test] 161829: regressions - FAIL)
Date: Mon, 10 May 2021 12:04:01 -0700 [thread overview]
Message-ID: <2c19af0b-e4c1-4f57-19cd-a86b4dc18c35@gmail.com> (raw)
In-Reply-To: <8b851596-acf7-9d3b-b08a-848cae5adada@xen.org>
On 5/10/2021 11:15 AM, Julien Grall wrote:
> Hi Christoph,
>
> On 10/05/2021 09:40, Christoph Hellwig wrote:
>> On Sat, May 08, 2021 at 12:32:37AM +0100, Julien Grall wrote:
>>> The pointer dereferenced seems to suggest that the swiotlb hasn't been
>>> allocated. From what I can tell, this may be because swiotlb_force is
>>> set
>>> to SWIOTLB_NO_FORCE, we will still enable the swiotlb when running on
>>> top
>>> of Xen.
>>>
>>> I am not entirely sure what would be the correct fix. Any opinions?
>>
>> Can you try something like the patch below (not even compile tested, but
>> the intent should be obvious?
>>
>>
>> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
>> index 16a2b2b1c54d..7671bc153fb1 100644
>> --- a/arch/arm64/mm/init.c
>> +++ b/arch/arm64/mm/init.c
>> @@ -44,6 +44,8 @@
>> #include <asm/tlb.h>
>> #include <asm/alternative.h>
>> +#include <xen/arm/swiotlb-xen.h>
>> +
>> /*
>> * We need to be able to catch inadvertent references to memstart_addr
>> * that occur (potentially in generic code) before
>> arm64_memblock_init()
>> @@ -482,7 +484,7 @@ void __init mem_init(void)
>> if (swiotlb_force == SWIOTLB_FORCE ||
>> max_pfn > PFN_DOWN(arm64_dma_phys_limit))
>> swiotlb_init(1);
>> - else
>> + else if (!IS_ENABLED(CONFIG_XEN) || !xen_swiotlb_detect())
>> swiotlb_force = SWIOTLB_NO_FORCE;
>> set_max_mapnr(max_pfn - PHYS_PFN_OFFSET);
>
> I have applied the patch on top of 5.13-rc1 and can confirm I am able to
> boot dom0. Are you going to submit the patch?
Sorry about that Julien and thanks Christoph!
--
Florian
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: Julien Grall <julien@xen.org>, Christoph Hellwig <hch@lst.de>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
linux-kernel@vger.kernel.org,
osstest service owner <osstest-admin@xenproject.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
iommu@lists.linux-foundation.org
Subject: Re: Regression when booting 5.15 as dom0 on arm64 (WAS: Re: [linux-linus test] 161829: regressions - FAIL)
Date: Mon, 10 May 2021 12:04:01 -0700 [thread overview]
Message-ID: <2c19af0b-e4c1-4f57-19cd-a86b4dc18c35@gmail.com> (raw)
In-Reply-To: <8b851596-acf7-9d3b-b08a-848cae5adada@xen.org>
On 5/10/2021 11:15 AM, Julien Grall wrote:
> Hi Christoph,
>
> On 10/05/2021 09:40, Christoph Hellwig wrote:
>> On Sat, May 08, 2021 at 12:32:37AM +0100, Julien Grall wrote:
>>> The pointer dereferenced seems to suggest that the swiotlb hasn't been
>>> allocated. From what I can tell, this may be because swiotlb_force is
>>> set
>>> to SWIOTLB_NO_FORCE, we will still enable the swiotlb when running on
>>> top
>>> of Xen.
>>>
>>> I am not entirely sure what would be the correct fix. Any opinions?
>>
>> Can you try something like the patch below (not even compile tested, but
>> the intent should be obvious?
>>
>>
>> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
>> index 16a2b2b1c54d..7671bc153fb1 100644
>> --- a/arch/arm64/mm/init.c
>> +++ b/arch/arm64/mm/init.c
>> @@ -44,6 +44,8 @@
>> #include <asm/tlb.h>
>> #include <asm/alternative.h>
>> +#include <xen/arm/swiotlb-xen.h>
>> +
>> /*
>> * We need to be able to catch inadvertent references to memstart_addr
>> * that occur (potentially in generic code) before
>> arm64_memblock_init()
>> @@ -482,7 +484,7 @@ void __init mem_init(void)
>> if (swiotlb_force == SWIOTLB_FORCE ||
>> max_pfn > PFN_DOWN(arm64_dma_phys_limit))
>> swiotlb_init(1);
>> - else
>> + else if (!IS_ENABLED(CONFIG_XEN) || !xen_swiotlb_detect())
>> swiotlb_force = SWIOTLB_NO_FORCE;
>> set_max_mapnr(max_pfn - PHYS_PFN_OFFSET);
>
> I have applied the patch on top of 5.13-rc1 and can confirm I am able to
> boot dom0. Are you going to submit the patch?
Sorry about that Julien and thanks Christoph!
--
Florian
next prev parent reply other threads:[~2021-05-10 19:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 21:00 [linux-linus test] 161829: regressions - FAIL osstest service owner
2021-05-07 23:32 ` Regression when booting 5.15 as dom0 on arm64 (WAS: Re: [linux-linus test] 161829: regressions - FAIL) Julien Grall
2021-05-07 23:32 ` Julien Grall
2021-05-10 8:40 ` Christoph Hellwig
2021-05-10 8:40 ` Christoph Hellwig
2021-05-10 18:15 ` Julien Grall
2021-05-10 18:15 ` Julien Grall
2021-05-10 19:04 ` Florian Fainelli [this message]
2021-05-10 19:04 ` Florian Fainelli
2021-05-11 1:46 ` Stefano Stabellini
2021-05-11 1:46 ` Stefano Stabellini
2021-05-11 6:35 ` Christoph Hellwig
2021-05-11 6:35 ` Christoph Hellwig
2021-05-11 16:47 ` Regression when booting 5.15 as dom0 on arm64 (WAS: Re: [linux-linus test] 161829: regressions - FAIL)] Stefano Stabellini
2021-05-11 16:47 ` Stefano Stabellini
2021-05-11 16:49 ` Christoph Hellwig
2021-05-11 16:49 ` Christoph Hellwig
2021-05-11 16:51 ` Stefano Stabellini
2021-05-11 16:51 ` Stefano Stabellini
2021-05-11 17:01 ` Christoph Hellwig
2021-05-11 17:01 ` Christoph Hellwig
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=2c19af0b-e4c1-4f57-19cd-a86b4dc18c35@gmail.com \
--to=f.fainelli@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=julien@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=osstest-admin@xenproject.org \
--cc=sstabellini@kernel.org \
--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.