From: Ian Campbell <ijc@hellion.org.uk>
To: Raghavendra D Prabhu <rprabhu@wnohang.net>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org, jeremy.fitzhardinge@citrix.com,
xen-devel@lists.xensource.com,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] Modpost section mismatch fix
Date: Mon, 04 Jul 2011 09:49:48 +0100 [thread overview]
Message-ID: <1309769388.634.51.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20110703232508.GB4440@Xye>
On Mon, 2011-07-04 at 04:55 +0530, Raghavendra D Prabhu wrote:
> [Sorry if duplicate, one earlier was corrupt]
>
> Hi,
> I got section mismatches reported by modpost in latest build. It got
> reported for xen_register_pirq and xen_unplug_emulated_devices
> functions.
> xen_register_pirq makes reference to
> acpi_sci_override_gsi in init.data section; marking
> xen_register_pirq with __init is not feasible since calls are made
> to it from acpi_register_gsi in non-init contexts. So marking it
> __refdata based on assumption that when acpi_sci_override_gsi is
> referenced, it is in early stages where it is alive.
I don't think this assumption holds, since xen_register_pirq can be
called at any time and basically unconditionally references
acpi_sci_override_gsi.
If we don't want to remove the __init from acpi_sci_override_gsi then
perhaps xen_setup_acpi_sci needs to stash it somewhere?
Or maybe xen_register_pirq could take an "int force_irq" which, if not
-1, would force a particular IRQ. The callsite in xen_setup_acpi_sci
(actually via xen_register_gsi so the param would need to be propagated
there) would be the only actual user?
The xen_unplug_emulated_devices change looks correct to me since
xen_unplug_emulated_devices is called from xen_arch_hvm_post_suspend.
Ian.
>
>
> --------------------------
> Raghavendra Prabhu
> GPG Id : 0xD72BE977
> Fingerprint: B93F EBCB 8E05 7039 CD3C A4B8 A616 DCA1 D72B E977
> www: wnohang.net
> _______________________________________________
> Virtualization mailing list
> Virtualization@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/virtualization
--
Ian Campbell
Current Noise: Crowbar - Remember Tomorrow (A Tribute To Iron Maiden)
SANTA CLAUS comes down a FIRE ESCAPE wearing bright blue LEG WARMERS
... He scrubs the POPE with a mild soap or detergent for 15 minutes,
starring JANE FONDA!!
next prev parent reply other threads:[~2011-07-04 8:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 23:25 Raghavendra D Prabhu
2011-07-04 8:49 ` Ian Campbell [this message]
2011-07-04 22:16 ` Raghavendra D Prabhu
2011-07-05 14:13 ` Konrad Rzeszutek Wilk
2011-07-05 14:27 ` [TOME] " Raghavendra D Prabhu
2011-07-05 14:48 ` Konrad Rzeszutek Wilk
2011-07-05 21:32 ` Konrad Rzeszutek Wilk
2011-07-06 8:30 ` [Xen-devel] " Ian Campbell
2011-07-07 15:46 ` Raghavendra D Prabhu
2011-07-07 16:24 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-07-07 19:48 ` Raghavendra D Prabhu
2011-07-07 20:09 ` Konrad Rzeszutek Wilk
2011-07-07 21:04 ` Raghavendra D Prabhu
2011-07-08 20:26 ` [Xen-devel] Re: [PATCH] Modpost section mismatch fix (for platform-pci-unplug.c) Konrad Rzeszutek Wilk
2011-07-09 16:29 ` [TOME] " Raghavendra D Prabhu
2011-07-11 10:47 ` 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=1309769388.634.51.camel@zakaz.uk.xensource.com \
--to=ijc@hellion.org.uk \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rprabhu@wnohang.net \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®