All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Assmann <sassmann@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xen: fix section mismatch in reference from the function xen_hvm_init_shared_info()
Date: Wed, 01 Dec 2010 12:38:28 +0100	[thread overview]
Message-ID: <4CF633B4.3060305@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1012011124220.14723@kaball-desktop>

On 01.12.2010 12:26, Stefano Stabellini wrote:
> On Tue, 30 Nov 2010, Stefan Assmann wrote:
>> From: Stefan Assmann <sassmann@redhat.com>
>>
>> The following warning shows up when building the kernel with
>> make CONFIG_DEBUG_SECTION_MISMATCH=y.
>>
>> WARNING: arch/x86/built-in.o(.text+0x475): Section mismatch in reference from the function xen_hvm_init_shared_info() to the function .init.text:extend_brk()
>> The function xen_hvm_init_shared_info() references
>> the function __init extend_brk().
>> This is often because xen_hvm_init_shared_info lacks a __init
>> annotation or the annotation of extend_brk is wrong.
>>
>> The problem is that xen_hvm_init_shared_info() calls extend_brk() which is
>> an __init function. However xen_hvm_init_shared_info() cannot be an
>> __init function as it's called on system resume as well. Easy fix by
>> moving extend_brk() out of the function.
>>
>> Signed-off-by: Stefan Assmann <sassmann@redhat.com>
>> ---
>>  arch/x86/xen/enlighten.c |    8 ++++----
>>  1 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
>> index 02c710b..13b11fd 100644
>> --- a/arch/x86/xen/enlighten.c
>> +++ b/arch/x86/xen/enlighten.c
>> @@ -83,6 +83,7 @@ EXPORT_SYMBOL(machine_to_phys_order);
>>  struct start_info *xen_start_info;
>>  EXPORT_SYMBOL_GPL(xen_start_info);
>>
>> +struct shared_info *shared_info_page;
>>  struct shared_info xen_dummy_shared_info;
>>
>>  void *xen_initial_gdt;
> 
> why not static?

No particular reason, feel free to make it static. Thx for the review!

  Stefan
--
Stefan Assmann         | Red Hat GmbH
Software Engineer      | Otto-Hahn-Strasse 20, 85609 Dornach
                       | HR: Amtsgericht Muenchen HRB 153243
                       | GF: Brendan Lane, Charlie Peters,
sassmann at redhat.com |     Michael Cunningham, Charles Cachera

      reply	other threads:[~2010-12-01 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 16:28 [PATCH] xen: fix section mismatch in reference from the function xen_hvm_init_shared_info() Stefan Assmann
2010-12-01 11:26 ` Stefano Stabellini
2010-12-01 11:38   ` Stefan Assmann [this message]

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=4CF633B4.3060305@redhat.com \
    --to=sassmann@redhat.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 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.