From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86/IO-APIC: fix setting of destinations
Date: Thu, 19 Nov 2015 09:19:34 -0500 [thread overview]
Message-ID: <564DDA76.90001@oracle.com> (raw)
In-Reply-To: <564DA86A02000078000B6A96@prv-mh.provo.novell.com>
On 11/19/2015 04:46 AM, Jan Beulich wrote:
> In commit a85da715cf ("x86/IO-APIC: adjust setting of destinations") I
> made a pretty blatant mistake: get_apic_id() can be used there only
> when running APICs in physical mode. For both flat and clustered modes
> the change was wrong, causing different kinds of boot problems on
> affected systems. Don't revert that change though, but use TARGET_CPUS
> (equaling cpu_online_map, and with there only being a single online CPU
> fulfilling the original commits intention).
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/xen/arch/x86/io_apic.c
> +++ b/xen/arch/x86/io_apic.c
> @@ -1039,7 +1039,7 @@ static void __init setup_IO_APIC_irqs(vo
> disable_8259A_irq(irq_to_desc(irq));
>
> desc = irq_to_desc(irq);
> - SET_DEST(entry, logical, get_apic_id());
> + SET_DEST(entry, logical, cpu_mask_to_apicid(TARGET_CPUS));
> spin_lock_irqsave(&ioapic_lock, flags);
> __ioapic_write_entry(apic, pin, 0, entry);
> set_native_irq_info(irq, TARGET_CPUS);
Tested-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
(One of our systems started failing and I bisected it yesterday to
a85da715c but didn't get to actually debug it. Now I don't need to).
-boris
next prev parent reply other threads:[~2015-11-19 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 9:46 [PATCH] x86/IO-APIC: fix setting of destinations Jan Beulich
2015-11-19 14:19 ` Boris Ostrovsky [this message]
2015-11-19 14:39 ` Andrew Cooper
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=564DDA76.90001@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.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.