From: Julien Grall <julien.grall@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Ian Campbell <ian.campbell@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
ian.jackson@eu.citrix.com, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen-unstable test] 56759: regressions - FAIL
Date: Thu, 11 Jun 2015 09:22:07 -0400 [thread overview]
Message-ID: <55798B7F.1060507@citrix.com> (raw)
In-Reply-To: <556DA1DF020000780008020B@mail.emea.novell.com>
Hi,
On 02/06/2015 06:30, Jan Beulich wrote:
>>>> On 29.05.15 at 18:32, <ian.campbell@citrix.com> wrote:
>> On Wed, 2015-05-27 at 17:04 +0100, Ian Campbell wrote:
>>> Looking at the netback side though it seems like netback_remove is
>>> switching to state=Closed _before_ it calls kobject_uevent(...,
>>> KOBJ_OFFLINE) and it is this which generates the call to netback_uevent
>>> which tries and fails to read script and produces the error message.
>>
>> I've just sent out a patch which fixes this issue, although I am still
>> at a loss to explain why we have only started seeing this now and only
>> under such specific circumstances.
>>
>>> I'm still slightly concerned that perhaps the new spinlock stuff has
>>> some sort of bad behaviour either on arndale specifically or more
>>> generally for ARM systems which has pushed this particular case over the
>>> edge.
>>
>> I did run some benchmarks (hackbench+fio on arndale domU and hackbench
>> on midway dom0) with and without the ticket locks and the results were
>> close enough that I'm basically not too worried that there is something
>> wrong with the ticket locks on ARM.
>>
>> It still niggles somewhat not to have a good theory about why this
>> change had this seemingly random effect, but I've not got any good ideas
>> for avenues to explore and I've got other things to do so I think I'll
>> leave it at that.
>
> So should we then re-instate the ticket lock patches?
Any update on this?
Regards,
--
Julien Grall
prev parent reply other threads:[~2015-06-11 13:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 9:34 [xen-unstable test] 56759: regressions - FAIL osstest service user
2015-05-20 9:56 ` Ian Campbell
2015-05-26 9:11 ` Julien Grall
2015-05-26 9:17 ` Ian Campbell
2015-05-26 9:22 ` Julien Grall
2015-05-26 13:29 ` Ian Campbell
2015-05-27 16:04 ` Ian Campbell
2015-05-28 8:50 ` Jan Beulich
2015-05-28 9:26 ` Ian Campbell
2015-05-28 10:10 ` Jan Beulich
2015-05-29 9:56 ` Andrew Cooper
2015-05-29 10:40 ` Jan Beulich
2015-05-29 10:50 ` Ian Campbell
2015-05-29 16:32 ` Ian Campbell
2015-06-02 10:30 ` Jan Beulich
2015-06-11 13:22 ` Julien Grall [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=55798B7F.1060507@citrix.com \
--to=julien.grall@citrix.com \
--cc=JBeulich@suse.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--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 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.