From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86/IO-APIC: adjust setting of destinations
Date: Fri, 13 Nov 2015 16:26:04 +0000 [thread overview]
Message-ID: <56460F1C.2070305@citrix.com> (raw)
In-Reply-To: <5646136202000078000B4CDE@prv-mh.provo.novell.com>
On 13/11/15 15:44, Jan Beulich wrote:
> setup_IO_APIC_irqs() runs before APs get brought up, so using
> desc->arch.cpu_mask as best risks it being either empty or having bits
> for CPUs other than the BP set. Just use the APIC ID of the only
> online CPU directly. Replace a stray hard_smp_processor_id() at once.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Surely this stray hard_smp_processor_id() needs to be merged into your
previous patch to remove hard_smp_processor_id() ?
As for the setup_IO_APIC_irqs() change, Reviewed-by: Andrew Cooper
<andrew.cooper3@citrix.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, cpu_mask_to_apicid(desc->arch.cpu_mask));
> + SET_DEST(entry, logical, get_apic_id());
> spin_lock_irqsave(&ioapic_lock, flags);
> __ioapic_write_entry(apic, pin, 0, entry);
> set_native_irq_info(irq, TARGET_CPUS);
> @@ -1843,7 +1843,7 @@ static void __init unlock_ExtINT_logic(v
>
> entry1.dest_mode = 0; /* physical delivery */
> entry1.mask = 0; /* unmask IRQ now */
> - SET_DEST(entry1, physical, hard_smp_processor_id());
> + SET_DEST(entry1, physical, get_apic_id());
> entry1.delivery_mode = dest_ExtINT;
> entry1.polarity = entry0.polarity;
> entry1.trigger = 0;
>
>
>
next prev parent reply other threads:[~2015-11-13 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 15:44 [PATCH] x86/IO-APIC: adjust setting of destinations Jan Beulich
2015-11-13 16:26 ` Andrew Cooper [this message]
2015-11-13 17:41 ` Jan Beulich
2015-11-13 17:43 ` 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=56460F1C.2070305@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.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.