From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Andrii Anisov <andrii_anisov@epam.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Julien Grall <julien.grall@arm.com>
Subject: Re: arm64: dma_to_phys/phys_to_dma need to be properly implemented
Date: Tue, 28 Mar 2017 16:04:32 +0300 [thread overview]
Message-ID: <0c7495ae-bbf0-9f39-6b28-e367e785b4d2@gmail.com> (raw)
In-Reply-To: <fb33e042-ae35-9dc4-d307-c26e77d2a624@epam.com>
indeed, this seems to be the case
So, in that mail thread we have the following statement:
"However, if that's not the case in any of the drivers, it
would lead to memory corruptions." with respect to get_sgtable
and pfn != mfn.
So, do you guys think I'll have to patch the offending driver?
Any other solution/workaround here?
Thank you,
Oleksandr
On 03/28/2017 03:40 PM, Andrii Anisov wrote:
> Hello,
>
> I guess Oleksandr stepped into the issue described here
> https://lists.xenproject.org/archives/html/xen-devel/2017-01/msg03454.html
> .
> He uses an old version of the patch but effectively calls
> __generic_dma_ops(dev)->get_sgtable() with foreign pages so faced
> troubles.
>
> Sincerely,
> Andrii Anisov
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-28 13:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 15:40 gnttab_map_refs and contiguous buffer Oleksandr Andrushchenko
2017-03-27 10:16 ` arm64: dma_to_phys/phys_to_dma need to be properly implemented Oleksandr Andrushchenko
2017-03-27 20:23 ` Stefano Stabellini
2017-03-28 6:42 ` Oleksandr Andrushchenko
2017-03-28 12:40 ` Andrii Anisov
2017-03-28 13:04 ` Oleksandr Andrushchenko [this message]
2017-03-28 19:20 ` Stefano Stabellini
2017-03-29 6:17 ` Oleksandr Andrushchenko
2017-03-29 22:36 ` Stefano Stabellini
2017-03-29 22:48 ` Julien Grall
2017-03-31 8:15 ` Oleksandr Andrushchenko
2017-03-31 17:56 ` 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=0c7495ae-bbf0-9f39-6b28-e367e785b4d2@gmail.com \
--to=andr2000@gmail.com \
--cc=andrii_anisov@epam.com \
--cc=julien.grall@arm.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;
as well as URLs for NNTP newsgroup(s).