From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Section mismatch in parainstructions Date: Sun, 10 Dec 2006 16:40:53 -0800 Message-ID: <457CA915.1040109@goop.org> References: <20061210155821.d2c5dfa5.randy.dunlap@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20061210155821.d2c5dfa5.randy.dunlap@oracle.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.osdl.org Errors-To: virtualization-bounces@lists.osdl.org To: Randy Dunlap Cc: akpm , virtualization@lists.osdl.org, sam@ravnborg.org List-Id: virtualization@lists.linuxfoundation.org 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 .exi= t.text: from .parainstructions after '' (at offset 0x0) > WARNING: drivers/net/hamradio/scc.o - Section mismatch: reference to .exi= t.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