From: Jonathan Daugherty <jtd@galois.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Thomas Leonard <talex5@gmail.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: Hypervisor crash setting up GIC (arm32)
Date: Wed, 23 Apr 2014 10:26:10 -0700 [thread overview]
Message-ID: <20140423172610.GA77424@galois.com> (raw)
In-Reply-To: <1398267356.18537.169.camel@kazak.uk.xensource.com>
> Stefano, weren't the Galois guys seeing something similar? You fixed
> it somewhere in a pending series IIRC?
(Hi from Galois.)
Yes, we were seeing this problem in a big way; I can testify that
Stefano's branch, which contains numerous patches to improve/expand ARM
interrupt handling, has helped us considerably:
Repo: git://xenbits.xen.org/people/sstabellini/xen-unstable.git
Branch: no_maintenance_interrupts-v6
--
Jonathan Daugherty
Software Engineer
Galois, Inc.
prev parent reply other threads:[~2014-04-23 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 14:11 Hypervisor crash setting up GIC (arm32) Thomas Leonard
2014-04-22 14:21 ` karim.allah.ahmed
2014-04-22 14:29 ` Thomas Leonard
2014-04-22 17:26 ` Thomas Leonard
2014-04-23 15:35 ` Ian Campbell
2014-04-23 17:26 ` Jonathan Daugherty [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=20140423172610.GA77424@galois.com \
--to=jtd@galois.com \
--cc=Ian.Campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=talex5@gmail.com \
--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).