From: Julien Grall <julien.grall@arm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
iommu@lists.linux-foundation.org, leo.yan@linaro.org,
xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
m.szyprowski@samsung.com
Subject: Re: Fail to boot Dom0 on Xen Arm64 after "dma-mapping: bypass indirect calls for dma-direct"
Date: Thu, 17 Jan 2019 11:43:49 +0000 [thread overview]
Message-ID: <1855c743-becd-fd52-50b9-86398f6cb985@arm.com> (raw)
In-Reply-To: <20190116181904.GA6228@infradead.org>
(+ Leo Yan who reported a similar issues on xen-devel)
Hi Christoph,
On 16/01/2019 18:19, Christoph Hellwig wrote:
> Does this fix your problem?
Thank you for the patch. This allows me to boot Dom0 on Juno r2.
My knowledge of DMA is quite limited, so I may have missed something.
Looking at the change for arm64, you will always call dma-direct API. In
previous Linux version, xen-swiotlb will call dev->archdata.dev_dma_ops (a copy
of dev->dma_ops before setting Xen DMA ops) if not NULL. Does it mean we expect
dev->dma_ops to always be NULL and hence using dma-direct API?
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-01-17 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 17:25 Fail to boot Dom0 on Xen Arm64 after "dma-mapping: bypass indirect calls for dma-direct" Julien Grall
2019-01-16 18:19 ` Christoph Hellwig
2019-01-17 11:43 ` Julien Grall [this message]
2019-01-17 14:11 ` Christoph Hellwig
[not found] ` <20190117141157.GA5184-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2019-01-19 0:43 ` Stefano Stabellini
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=1855c743-becd-fd52-50b9-86398f6cb985@arm.com \
--to=julien.grall@arm.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jgross@suse.com \
--cc=leo.yan@linaro.org \
--cc=m.szyprowski@samsung.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox