From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [Xen-devel] [PATCH 2/2] swiotlb-xen: xen_swiotlb_map_page: do not error out if dma_capable fails
Date: Tue, 12 Nov 2013 14:22:47 -0600 [thread overview]
Message-ID: <52828E17.2040801@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1311121704590.26077@kaball.uk.xensource.com>
On 11/12/2013 11:27 AM, Stefano Stabellini wrote:
> Russell gave a great explanation of the issue so I am just going to
> limit myself to answering to:
>
> On Tue, 12 Nov 2013, Konrad Rzeszutek Wilk wrote:
>>> Considering that we know that the swiotlb buffer has a low address,
>>> skip the check.
>>
>> I am not following that sentence. Could you please explain to me
>> how the SWIOTLB buffer low address guarantees that we don't need
>> the check?
>
> xen_swiotlb_fixup makes sure that the swiotlb buffer is lower than 4GB,
> probably lower than 3GB, by passing dma_bits to
> xen_create_contiguous_region.
> This meets the requirements of most devices out there.
> In fact we are not even running this check under the same conditions in
> swiotlb_map_sg_attrs.
> I admit that it is possible to come up with a scenario where the check
> would be useful, but it is far easier to come up with scenarios where
> not only is unneeded but it is even harmful.
>
> Alternatively (without Rob's "of: set dma_mask to point to
> coherent_dma_mask") Linux 3.13 is going to fail to get the network
> running on Midway. It is going to avoid fs mounting failures just
> because we don't do the same check in swiotlb_map_sg_attrs.
>
> FYI given that Rob's patch is probably going upstream soon anyway, I
> don't feel so strongly about this.
It is in Linus' tree now.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robherring2@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: konrad@kernel.org, xen-devel@lists.xensource.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Xen-devel] [PATCH 2/2] swiotlb-xen: xen_swiotlb_map_page: do not error out if dma_capable fails
Date: Tue, 12 Nov 2013 14:22:47 -0600 [thread overview]
Message-ID: <52828E17.2040801@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1311121704590.26077@kaball.uk.xensource.com>
On 11/12/2013 11:27 AM, Stefano Stabellini wrote:
> Russell gave a great explanation of the issue so I am just going to
> limit myself to answering to:
>
> On Tue, 12 Nov 2013, Konrad Rzeszutek Wilk wrote:
>>> Considering that we know that the swiotlb buffer has a low address,
>>> skip the check.
>>
>> I am not following that sentence. Could you please explain to me
>> how the SWIOTLB buffer low address guarantees that we don't need
>> the check?
>
> xen_swiotlb_fixup makes sure that the swiotlb buffer is lower than 4GB,
> probably lower than 3GB, by passing dma_bits to
> xen_create_contiguous_region.
> This meets the requirements of most devices out there.
> In fact we are not even running this check under the same conditions in
> swiotlb_map_sg_attrs.
> I admit that it is possible to come up with a scenario where the check
> would be useful, but it is far easier to come up with scenarios where
> not only is unneeded but it is even harmful.
>
> Alternatively (without Rob's "of: set dma_mask to point to
> coherent_dma_mask") Linux 3.13 is going to fail to get the network
> running on Midway. It is going to avoid fs mounting failures just
> because we don't do the same check in swiotlb_map_sg_attrs.
>
> FYI given that Rob's patch is probably going upstream soon anyway, I
> don't feel so strongly about this.
It is in Linus' tree now.
Rob
next prev parent reply other threads:[~2013-11-12 20:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 14:11 [PATCH 0/2] swiotlb-xen fixes Stefano Stabellini
2013-11-12 14:11 ` Stefano Stabellini
2013-11-12 14:11 ` Stefano Stabellini
2013-11-12 14:11 ` [PATCH 1/2] swiotlb-xen: add missing xen_dma_map_page call Stefano Stabellini
2013-11-12 14:11 ` Stefano Stabellini
2013-11-12 14:11 ` Stefano Stabellini
2013-11-12 14:45 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-11-12 14:45 ` Konrad Rzeszutek Wilk
2013-11-12 14:45 ` Konrad Rzeszutek Wilk
2013-11-12 17:03 ` Stefano Stabellini
2013-11-12 17:03 ` Stefano Stabellini
2013-11-12 17:03 ` Stefano Stabellini
2013-11-12 14:12 ` [PATCH 2/2] swiotlb-xen: xen_swiotlb_map_page: do not error out if dma_capable fails Stefano Stabellini
2013-11-12 14:12 ` Stefano Stabellini
2013-11-12 14:12 ` Stefano Stabellini
2013-11-12 14:48 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-11-12 14:48 ` Konrad Rzeszutek Wilk
2013-11-12 14:48 ` Konrad Rzeszutek Wilk
2013-11-12 15:05 ` Russell King - ARM Linux
2013-11-12 15:05 ` Russell King - ARM Linux
2013-11-12 17:27 ` Stefano Stabellini
2013-11-12 17:27 ` Stefano Stabellini
2013-11-12 17:27 ` Stefano Stabellini
2013-11-12 20:22 ` Rob Herring [this message]
2013-11-12 20:22 ` Rob Herring
2013-11-13 11:35 ` Stefano Stabellini
2013-11-13 11:35 ` Stefano Stabellini
2013-11-13 11:35 ` 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=52828E17.2040801@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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.