From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Andre Przywara <andre.przywara@calxeda.com>,
christoffer.dall@linaro.org,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [ARM] Bash often segfaults in Dom0 with the latest Xen
Date: Wed, 05 Jun 2013 11:39:58 +0100 [thread overview]
Message-ID: <51AF157E.5090307@linaro.org> (raw)
In-Reply-To: <1370425111.24512.165.camel@zakaz.uk.xensource.com>
On 06/05/2013 10:38 AM, Ian Campbell wrote:
> On Tue, 2013-06-04 at 23:45 +0100, Julien Grall wrote:
>> The patch below removes WFI trap and by consequence avoid a VCPU to move to
>> another physical CPU.
>
> FWIW the dom0_vcpus_pin command line parameter should have achieved the
> same thing without removing the WFI code paths. I very much doubt that
> code path is to blame but it might be worth ruling it out.
Thanks for this option.
--
Julien
prev parent reply other threads:[~2013-06-05 10:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 22:45 [ARM] Bash often segfaults in Dom0 with the latest Xen Julien Grall
2013-06-05 1:38 ` Christoffer Dall
2013-06-05 9:52 ` Ian Campbell
2013-06-05 11:48 ` Julien Grall
2013-06-05 14:30 ` Christoffer Dall
2013-06-05 15:18 ` Ian Campbell
2013-06-05 16:12 ` Julien Grall
2013-06-05 16:46 ` Stefano Stabellini
2013-06-05 17:36 ` Christoffer Dall
2013-06-05 17:53 ` Julien Grall
2013-06-05 17:57 ` Christoffer Dall
2013-06-05 18:01 ` Stefano Stabellini
2013-06-05 18:17 ` Christoffer Dall
2013-06-05 18:36 ` Julien Grall
2013-06-11 11:48 ` Julien Grall
2013-06-11 14:25 ` Christoffer Dall
2013-06-05 9:38 ` Ian Campbell
2013-06-05 10:39 ` 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=51AF157E.5090307@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=andre.przywara@calxeda.com \
--cc=christoffer.dall@linaro.org \
--cc=xen-devel@lists.xen.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).