From: Jiri Slaby <jslaby@suse.cz>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
david.vrabel@citrix.com, stable@vger.kernel.org,
Luis Henriques <luis.henriques@canonical.com>
Subject: Re: [Xen-devel] [PATCH 2/2] swiotlb-xen: pass dev_addr to swiotlb_tbl_unmap_single
Date: Mon, 26 Jan 2015 14:39:05 +0100 [thread overview]
Message-ID: <54C64379.7070001@suse.cz> (raw)
In-Reply-To: <1422269607.27469.5.camel@citrix.com>
On 01/26/2015, 11:53 AM, Ian Campbell wrote:
> On Fri, 2014-11-21 at 17:00 +0000, Stefano Stabellini wrote:
>> Need to pass the pointer within the swiotlb internal buffer to the
>> swiotlb library, that in the case of xen_unmap_single is dev_addr, not
>> paddr.
>>
>> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>> CC: konrad.wilk@oracle.com
>> CC: stable@vger.kernel.org
>
> This went into mainline as 2c3fc8d26dd0 "swiotlb-xen: pass dev_addr to
> swiotlb_tbl_unmap_single" but was reverted in dbdd74763f1f.
>
> However it seems that 2c3fc8d26dd0 has made it into at least some stable
> kernel trees:
> v3.18.3 as 2129c43d41e9
> v3.16.7-ckt4 as 94ab279b0c9a
> v3.14.29 as 3394691d34fc
> v3.10.65 as 81cb80b578c5
> so it should be reverted there too. This is causing issues in the field
> such as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776237.
>
> v3.17, v3.15, v3.13.11-ckt14, v3.12.x, v3.11.x appear clean, I stopped
Hi, dropped from the 3.12 queue.
thanks,
--
js
suse labs
prev parent reply other threads:[~2015-01-26 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.02.1411211657430.2675@kaball.uk.xensource.com>
2014-11-21 17:00 ` [PATCH 1/2] swiotlb-xen: call xen_dma_sync_single_for_device when appropriate Stefano Stabellini
2014-11-21 17:00 ` [PATCH 2/2] swiotlb-xen: pass dev_addr to swiotlb_tbl_unmap_single Stefano Stabellini
2015-01-26 10:53 ` [Xen-devel] " Ian Campbell
2015-01-26 11:10 ` Luis Henriques
2015-01-26 13:39 ` Jiri Slaby [this message]
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=54C64379.7070001@suse.cz \
--to=jslaby@suse.cz \
--cc=Ian.Campbell@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--cc=stable@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).