From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Xen Devel <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: [linux-linus test] 25478: regressions - FAIL [and 1 more messages]
Date: Wed, 16 Apr 2014 10:11:52 -0400 [thread overview]
Message-ID: <20140416141151.GA8403@phenom.dumpdata.com> (raw)
In-Reply-To: <21326.29230.302456.997315@mariner.uk.xensource.com>
On Wed, Apr 16, 2014 at 01:06:06PM +0100, Ian Jackson wrote:
> Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [linux-linus test] 25478: regressions - FAIL [and 1 more messages]"):
> > On Apr 16, 2014 6:12 AM, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
> > > Another week has gone by and Linux tip still fails this test.
> >
> > Did you try the recommendation that David offered - boot with 4GB to dom0?
>
> That would be a workaround. I can do that (as it happens these
> machines have 8G of RAM so it is actually possible), but:
Right.
>
> The purpose of running tests is to discover bugs (so that they can be
> fixed). It is not to generate a nice clean report by sweeping things
> under the carpet.
Right.
>
> Here the tests have discovered a bug in Linux. AIUI it's a bug which
> is visible when using this particular driver, but which is actually a
> problem with the Xen integration into the Linux VM system in general.
> So other it presumably affects other drivers too. It should be fixed,
> not worked around.
I concur.
>
> The downside of not working around this bug is that osstest's
> failing-host-stickiness will cause an increasing proportion of the
> tests to run on the affected hosts. This might mask other bugs.
>
> Conversely, working around this bug in the manner suggested will
> presumably just make the bug disappear off our radar.
There is a danger of that.
I am not going to be able to take a look at this bug in the next three
weeks. If anybody else wants to take a stab at this - here is my hand-waving
idea of how it could be done:
1). Cleanup the ia64 usage of same code 'ia64_dma_get_required_mask'
(it actually duplicates what the drivers/base has). Perhaps move it to
lib/iommu-helper.c
Call it 'generic_get_required_mask' or such.
2). Look at other platforms that use a similar (or the same) code
and see if they can re-use it now that it is in lib/iommu-helper.c.
3). Make the x86 dma_ops start using the extra "get_required_mask"
and point it to the generic_get_required_mask.
4). Make the xen-swiotlb use its own version.
>
> Ian.
next prev parent reply other threads:[~2014-04-16 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 11:49 [linux-linus test] 25478: regressions - FAIL [and 1 more messages] Konrad Rzeszutek Wilk
2014-04-16 12:06 ` Ian Jackson
2014-04-16 14:11 ` Konrad Rzeszutek Wilk [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-16 11:59 Konrad Rzeszutek Wilk
2014-03-14 16:42 [linux-linus test] 25478: regressions - FAIL xen.org
2014-03-14 17:07 ` Ian Campbell
2014-03-14 18:23 ` Konrad Rzeszutek Wilk
2014-03-17 11:08 ` Ian Campbell
2014-03-17 19:36 ` Konrad Rzeszutek Wilk
2014-03-18 9:29 ` Ian Campbell
2014-03-18 10:55 ` David Vrabel
2014-03-18 11:04 ` Ian Campbell
2014-03-18 11:10 ` Ian Campbell
2014-03-18 11:25 ` David Vrabel
2014-03-18 11:29 ` Ian Campbell
[not found] ` <53283118.5050706@citrix.com>
[not found] ` <1395143026.12847.47.camel@kazak.uk.xensource.com>
2014-03-27 18:00 ` [linux-linus test] 25677: " xen.org
2014-04-10 15:37 ` [linux-linus test] 25478: regressions - FAIL [and 1 more messages] Ian Jackson
2014-04-16 10:12 ` Ian Jackson
2014-04-16 10:53 ` David Vrabel
2014-04-16 11:47 ` Ian Jackson
2014-04-16 13:48 ` David Vrabel
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=20140416141151.GA8403@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@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 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.