From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: JGross@suse.com
Cc: xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
linux-kernel@vger.kernel.org, roger.pau@citrix.com
Subject: [PATCH v3 5/9] xen/pvh: Make sure we don't use ACPI_IRQ_MODEL_PIC for SCI
Date: Mon, 6 Feb 2017 12:00:21 -0500 [thread overview]
Message-ID: <1486400425-5356-6-git-send-email-boris.ostrovsky@oracle.com> (raw)
In-Reply-To: <1486400425-5356-1-git-send-email-boris.ostrovsky@oracle.com>
Since we are not using PIC and (at least currently) don't have IOAPIC
we want to make sure that acpi_irq_model doesn't stay set to
ACPI_IRQ_MODEL_PIC (which is the default value). If we allowed it to
stay then acpi_os_install_interrupt_handler() would try (and fail) to
request_irq() for PIC.
Instead we set the model to ACPI_IRQ_MODEL_PLATFORM which will prevent
this from happening.
Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
---
Changes in v3:
* Moved update of acpi_irq_model to x86_init.oem.arch_setup() (i.e.
after ACPI has been initialized so we know whether or not we have
IOAPICs). Clarified comit message.
* Moved xen_hvm_init_shared_info() into patch 4.
arch/x86/xen/enlighten.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
index d2144f7..6d406f3 100644
--- a/arch/x86/xen/enlighten.c
+++ b/arch/x86/xen/enlighten.c
@@ -1672,6 +1672,16 @@ asmlinkage __visible void __init xen_start_kernel(void)
}
#ifdef CONFIG_XEN_PVH
+
+static void xen_pvh_arch_setup(void)
+{
+#ifdef CONFIG_ACPI
+ /* Make sure we don't fall back to (default) ACPI_IRQ_MODEL_PIC. */
+ if (nr_ioapics == 0)
+ acpi_irq_model = ACPI_IRQ_MODEL_PLATFORM;
+#endif
+}
+
static void __init init_pvh_bootparams(void)
{
struct xen_memory_map memmap;
@@ -1752,6 +1762,8 @@ void __init xen_prepare_pvh(void)
wrmsr_safe(msr, (u32)pfn, (u32)(pfn >> 32));
init_pvh_bootparams();
+
+ x86_init.oem.arch_setup = xen_pvh_arch_setup;
}
#endif
--
2.7.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-06 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 17:00 [PATCH v3 0/9] PVH v2 support (domU) Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 1/9] x86/boot/32: Convert the 32-bit pgtable setup code from assembly to C Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 2/9] xen/x86: Remove PVH support Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 3/9] xen/pvh: Import PVH-related Xen public interfaces Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 4/9] xen/pvh: Bootstrap PVH guest Boris Ostrovsky
2017-02-06 19:29 ` kbuild test robot
2017-02-06 17:00 ` Boris Ostrovsky [this message]
2017-02-07 10:19 ` [PATCH v3 5/9] xen/pvh: Make sure we don't use ACPI_IRQ_MODEL_PIC for SCI Juergen Gross
2017-02-06 17:00 ` [PATCH v3 6/9] xen/pvh: Initialize grant table for PVH guests Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 7/9] xen/pvh: PVH guests always have PV devices Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 8/9] xen/pvh: Enable CPU hotplug Boris Ostrovsky
2017-02-06 17:00 ` [PATCH v3 9/9] xen/pvh: Use Xen's emergency_restart op for PVH guests Boris Ostrovsky
2017-02-07 17:48 ` [PATCH v3 0/9] PVH v2 support (domU) Boris Ostrovsky
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=1486400425-5356-6-git-send-email-boris.ostrovsky@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JGross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).