From: Juergen Gross <jgross@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>, boris.ostrovsky@oracle.com
Cc: linux-kernel@vger.kernel.org, david.vrabel@citrix.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen/x86: actually allocate legacy interrupts on PV guests
Date: Thu, 21 Apr 2016 11:08:16 +0200 [thread overview]
Message-ID: <57189880.6030102@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1604201413070.23110@sstabellini-ThinkPad-X260>
On 20/04/16 15:15, 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.
Would you mind describing the resulting problem? With this commit
message I'm absolutely not capable to decide whether e.g. the other
use of nr_legacy_irqs() in pci_xen_initial_domain() is correct or
not.
Juergen
>
> Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
>
> diff --git a/arch/x86/pci/xen.c b/arch/x86/pci/xen.c
> index beac4df..349b8ce 100644
> --- a/arch/x86/pci/xen.c
> +++ b/arch/x86/pci/xen.c
> @@ -491,8 +491,11 @@ int __init pci_xen_initial_domain(void)
> #endif
> __acpi_register_gsi = acpi_register_gsi_xen;
> __acpi_unregister_gsi = NULL;
> - /* Pre-allocate legacy irqs */
> - for (irq = 0; irq < nr_legacy_irqs(); irq++) {
> + /*
> + * Pre-allocate the legacy IRQs. Use NR_LEGACY_IRQS here
> + * because we don't have a PIC and thus nr_legacy_irqs() is zero.
> + */
> + for (irq = 0; irq < NR_IRQS_LEGACY; irq++) {
> int trigger, polarity;
>
> if (acpi_get_override_irq(irq, &trigger, &polarity) == -1)
>
next prev parent reply other threads:[~2016-04-21 9:08 UTC|newest]
Thread overview: 24+ 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 [this message]
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 ` [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 13:57 ` [Xen-devel] " Boris Ostrovsky
2016-05-16 15:21 ` Stefano Stabellini
2016-05-16 15:21 ` Stefano Stabellini
2016-05-16 11:23 ` Stefano Stabellini
2016-04-27 13:40 ` David Vrabel
2016-04-27 9:35 ` David Vrabel
2016-04-27 5:02 ` Juergen Gross
2016-04-21 9:08 ` Juergen Gross
2016-04-21 11:02 ` Olaf Hering
2016-04-21 11:02 ` [Xen-devel] " Olaf Hering
-- strict thread matches above, loose matches on Subject: below --
2016-04-20 13:15 Stefano Stabellini
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=57189880.6030102@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.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.