From: David Vrabel <david.vrabel@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>, xen-devel@lists.xenproject.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH 0/3] xen: FIFO-based event channel fixes
Date: Thu, 31 Jul 2014 18:23:48 +0100 [thread overview]
Message-ID: <53DA7BA4.9080507@citrix.com> (raw)
In-Reply-To: <E1XCsBf-0003nI-Fu@lists.xen.org>
On 31/07/14 16:22, David Vrabel wrote:
> Two fixes and one cleanup for the FIFO-based event channel ABI.
>
> The first fixes an early hang when resuming guests -- this often
> occured with PVHVM guests but PV guests for some reason got away with
> it...
>
> The second fixes a rare crash if 1023 event channels (or more) were
> used -- this would typically only affect dom0.
Applied to devel/for-linus-2.17 since they're not a 3.16 regression and
3.16 is nearly here.
David
next parent reply other threads:[~2014-07-31 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XCsBf-0003nI-Fu@lists.xen.org>
2014-07-31 17:23 ` David Vrabel [this message]
[not found] <E1XCsBf-0003nI-EP@lists.xen.org>
2014-07-31 16:16 ` [PATCH 0/3] xen: FIFO-based event channel fixes Boris Ostrovsky
2014-07-31 16:17 ` David Vrabel
2014-07-31 16:27 ` Boris Ostrovsky
2014-07-31 15:22 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=53DA7BA4.9080507@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.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.