From: Olaf Hering <olaf@aepfle.de>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: boris.ostrovsky@oracle.com, jgross@suse.com,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
david.vrabel@citrix.com
Subject: Re: [Xen-devel] [PATCH] xen/x86: actually allocate legacy interrupts on PV guests
Date: Thu, 21 Apr 2016 13:02:20 +0200 [thread overview]
Message-ID: <20160421110220.GA21394@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1604201413070.23110@sstabellini-ThinkPad-X260>
On Wed, Apr 20, Stefano Stabellini wrote:
> b4ff8389ed14 is incomplete: relies on nr_legacy_irqs() to get the number
> of legacy interrupts when actually nr_legacy_irqs() returns 0 after
> probe_8259A(). Use NR_IRQS_LEGACY instead.
>
> Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
Tested-by: Olaf Hering <olaf@aepfle.de>
Fixes my M9400 laptop (and should go to stable as well):
http://lists.xenproject.org/archives/html/xen-devel/2016-04/msg02624.html
Olaf
prev parent reply other threads:[~2016-04-21 11:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 13:15 [PATCH] xen/x86: actually allocate legacy interrupts on PV guests Stefano Stabellini
2016-04-21 9:08 ` Juergen Gross
2016-04-21 9:08 ` Juergen Gross
2016-04-21 9:30 ` Stefano Stabellini
2016-04-21 9:30 ` Stefano Stabellini
2016-04-27 5:02 ` Juergen Gross
2016-04-27 9:35 ` David Vrabel
2016-04-27 9:35 ` [Xen-devel] " David Vrabel
2016-04-27 13:38 ` Boris Ostrovsky
2016-04-27 13:38 ` Boris Ostrovsky
2016-04-27 13:40 ` [Xen-devel] " David Vrabel
2016-04-27 14:03 ` Boris Ostrovsky
2016-04-27 14:03 ` [Xen-devel] " Boris Ostrovsky
2016-05-16 11:23 ` Stefano Stabellini
2016-05-16 13:57 ` Boris Ostrovsky
2016-05-16 15:21 ` Stefano Stabellini
2016-05-16 15:21 ` [Xen-devel] " Stefano Stabellini
2016-05-16 13:57 ` Boris Ostrovsky
2016-05-16 11:23 ` Stefano Stabellini
2016-04-27 13:40 ` David Vrabel
2016-04-27 5:02 ` Juergen Gross
2016-04-21 11:02 ` Olaf Hering
2016-04-21 11:02 ` Olaf Hering [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=20160421110220.GA21394@gmail.com \
--to=olaf@aepfle.de \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--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.