From: Thomas Gleixner <tglx@linutronix.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Greg KH <gregkh@suse.de>, Jens Axboe <jens.axboe@oracle.com>,
Chris Wright <chrisw@redhat.com>,
kurt.hackel@oracle.com, Andrew Morton <akpm@linux-foundation.org>,
Ky Srinivasan <ksrinivasan@novell.com>,
Beulich <jbeulich@novell.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Avi Kivity <avi@redhat.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: Re: [PATCH 01/17] xen/dom0: handle acpi lapic parsing in Xen dom0
Date: Tue, 2 Jun 2009 18:58:35 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0906021826430.3419@localhost.localdomain> (raw)
In-Reply-To: <1243409850-21577-2-git-send-email-jeremy@goop.org>
On Wed, 27 May 2009, Jeremy Fitzhardinge wrote:
> When running in Xen dom0, we still want to parse the ACPI tables to
> find out about local and IO apics, but we don't want to actually use
> the lapics.
Hmm, we parse the tables and discard the information. What's the point
of this exercise ? Some nice dmesg lines ?
> Put a couple of tests for Xen to prevent lapics from being mapped or
> accessed. This is very Xen-specific behaviour, so there didn't seem to
> be any point in adding more indirection.
I hate these "if (xen_...)" extra cases even more than the paravirt
misery. They stick Xen dependencies into random places and enforce the
people who want to modify that code to find out why the heck this
needs to be there.
That's the fundamental design problem with the Dom0 model that you
want just certain parts of Linux and those parts which are in your way
are just hacked out. But this is designed to be a nightmare for
maintainence and development. Are you going to stick more and more of
those "if (xen..)" constructs into places which provide functionality
which is only partially useful to Xen ?
Thanks,
tglx
> [ Impact: ignore local apics, which are not usable under Xen ]
>
> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> Reviewed-by: "H. Peter Anvin" <hpa@zytor.com>
> ---
> arch/x86/kernel/acpi/boot.c | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
> index 723989d..4147e0c 100644
> --- a/arch/x86/kernel/acpi/boot.c
> +++ b/arch/x86/kernel/acpi/boot.c
> @@ -41,6 +41,8 @@
> #include <asm/mpspec.h>
> #include <asm/smp.h>
>
> +#include <asm/xen/hypervisor.h>
> +
> static int __initdata acpi_force = 0;
> u32 acpi_rsdt_forced;
> #ifdef CONFIG_ACPI
> @@ -218,6 +220,10 @@ static void __cpuinit acpi_register_lapic(int id, u8 enabled)
> {
> unsigned int ver = 0;
>
> + /* We don't want to register lapics when in Xen dom0 */
> + if (xen_initial_domain())
> + return;
> +
> if (!enabled) {
> ++disabled_cpus;
> return;
> @@ -802,6 +808,10 @@ static int __init acpi_parse_fadt(struct acpi_table_header *table)
>
> static void __init acpi_register_lapic_address(unsigned long address)
> {
> + /* Xen dom0 doesn't have usable lapics */
> + if (xen_initial_domain())
> + return;
> +
> mp_lapic_addr = address;
>
> set_fixmap_nocache(FIX_APIC_BASE, address);
> --
> 1.6.0.6
>
next prev parent reply other threads:[~2009-06-02 17:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 7:37 [GIT PULL REPOST] xen/dom0/apic-ops: Xen dom0 APIC changes Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 01/17] xen/dom0: handle acpi lapic parsing in Xen dom0 Jeremy Fitzhardinge
2009-06-02 16:58 ` Thomas Gleixner [this message]
2009-06-03 6:38 ` Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 02/17] x86: add io_apic_ops to allow interception Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 03/17] xen: implement io_apic_ops Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 04/17] xen: create dummy ioapic mapping Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 05/17] xen: implement pirq type event channels Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 06/17] x86/io_apic: add get_nr_irqs_gsi() Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 07/17] xen/apic: identity map gsi->irqs Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 08/17] xen: direct irq registration to pirq event channels Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 09/17] xen: bind pirq to vector and event channel Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 10/17] xen: pre-initialize legacy irqs early Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 11/17] xen: don't setup acpi interrupt unless there is one Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 12/17] xen: use acpi_get_override_irq() to get triggering for legacy irqs Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 13/17] xen: initialize irq 0 too Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 14/17] xen: dynamically allocate irq & event structures Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 15/17] xen: set pirq name to something useful Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 16/17] xen: fix legacy irq setup, make ioapic-less machines work Jeremy Fitzhardinge
2009-05-27 7:37 ` [PATCH 17/17] xen: disable MSI Jeremy Fitzhardinge
2009-05-27 15:34 ` Linus Torvalds
2009-05-27 20:40 ` David Miller
2009-05-27 22:25 ` Ingo Molnar
2009-05-27 21:18 ` Ingo Molnar
2009-05-27 21:46 ` Linus Torvalds
2009-05-27 22:01 ` Ingo Molnar
2009-05-27 22:03 ` Roland Dreier
2009-05-27 22:13 ` Linus Torvalds
2009-05-27 22:20 ` Roland Dreier
2009-05-27 22:26 ` Ingo Molnar
2009-05-28 6:28 ` Alan Cox
2009-05-28 6:38 ` Andrew Morton
2009-05-28 22:21 ` Roland Dreier
2009-06-01 2:09 ` Jon Masters
2009-05-28 19:51 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2009-05-12 23:25 [GIT PULL] Xen APIC hooks (with io_apic_ops) Jeremy Fitzhardinge
2009-05-12 23:25 ` [PATCH 01/17] xen/dom0: handle acpi lapic parsing in Xen dom0 Jeremy Fitzhardinge
2009-03-13 16:42 [GIT PULL] Xen dom0 apic changes Jeremy Fitzhardinge
2009-03-13 16:42 ` [PATCH 01/17] xen/dom0: handle acpi lapic parsing in Xen dom0 Jeremy Fitzhardinge
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=alpine.LFD.2.00.0906021826430.3419@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=gregkh@suse.de \
--cc=jbeulich@novell.com \
--cc=jens.axboe@oracle.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=jeremy@goop.org \
--cc=ksrinivasan@novell.com \
--cc=kurt.hackel@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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
Powered by JetHome