From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: akpm <akpm@osdl.org>, virtualization@lists.osdl.org, sam@ravnborg.org
Subject: Re: Section mismatch in parainstructions
Date: Sun, 10 Dec 2006 16:40:53 -0800 [thread overview]
Message-ID: <457CA915.1040109@goop.org> (raw)
In-Reply-To: <20061210155821.d2c5dfa5.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> Is it OK for section .parainstructions to reference
> exit.text?
>
> I'm seeing:
>
> WARNING: drivers/net/hamradio/scc.o - Section mismatch: reference to .exit.text: from .parainstructions after '' (at offset 0x0)
> WARNING: drivers/net/hamradio/scc.o - Section mismatch: reference to .exit.text: from .parainstructions after '' (at offset 0x8)
>
> If that's OK, we need a small patch to modpost, as below.
>
What are the semantics of .exit.text? In principle a paravirtualized
instruction can appear anywhere, so I think these warnings are bogus.
The only concern is if one of these sections disappears before the
paravirt_ops instruction substitution happens.
J
next prev parent reply other threads:[~2006-12-11 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 23:58 Section mismatch in parainstructions Randy Dunlap
2006-12-11 0:40 ` Jeremy Fitzhardinge [this message]
2006-12-11 2:34 ` Randy Dunlap
2006-12-11 9:34 ` Jeremy Fitzhardinge
2006-12-12 0:14 ` Rusty Russell
2006-12-12 3:21 ` Andi Kleen
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=457CA915.1040109@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=randy.dunlap@oracle.com \
--cc=sam@ravnborg.org \
--cc=virtualization@lists.osdl.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.