All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Andi Kleen <ak@muc.de>, Chris Wright <chrisw@sous-sol.org>,
	virtualization <virtualization@lists.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] x86 paravirt_ops: binary patching infrastructure
Date: Mon, 07 Aug 2006 15:14:59 +1000	[thread overview]
Message-ID: <1154927700.7642.1.camel@localhost.localdomain> (raw)
In-Reply-To: <1154926114.21647.38.camel@localhost.localdomain>

And a trivial warning fix on that last one when !CONFIG_PARAVIRT.

struct paravirt_patch is only defined for CONFIG_PARAVIRT, so we
declare the (unused) __start and __stop section markers as char, which
causes a warning when we pass them to the dummy apply_paravirt.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

--- working-2.6.18-rc3-mm2/arch/i386/kernel/alternative.c.~1~	2006-08-07 14:33:13.000000000 +1000
+++ working-2.6.18-rc3-mm2/arch/i386/kernel/alternative.c	2006-08-07 15:08:21.000000000 +1000
@@ -369,7 +369,7 @@
 extern struct paravirt_patch __start_parainstructions[],
 	__stop_parainstructions[];
 #else
-void apply_paravirt(struct paravirt_patch *start, struct paravirt_patch *end)
+void apply_paravirt(void *start, void *end)
 {
 }
 extern char __start_parainstructions[], __stop_parainstructions[];


-- 
Help! Save Australia from the worst of the DMCA: http://linux.org.au/law

  reply	other threads:[~2006-08-07  5:14 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07  4:43 [PATCH 1/4] x86 paravirt_ops: create no_paravirt.h for native ops Rusty Russell
2006-08-07  4:45 ` [PATCH 2/4] x86 paravirt_ops: paravirt_desc.h for native descriptor ops Rusty Russell
2006-08-07  4:45   ` Rusty Russell
2006-08-07  4:47   ` [PATCH 3/4] x86 paravirt_ops: implementation of paravirt_ops Rusty Russell
2006-08-07  4:47     ` Rusty Russell
2006-08-07  4:48     ` [PATCH 4/4] x86 paravirt_ops: binary patching infrastructure Rusty Russell
2006-08-07  4:48       ` Rusty Russell
2006-08-07  5:14       ` Rusty Russell [this message]
2006-08-07  5:38       ` Andi Kleen
2006-08-07  5:56         ` Jeremy Fitzhardinge
2006-08-07  5:56           ` Jeremy Fitzhardinge
2006-08-07  5:39     ` [PATCH 3/4] x86 paravirt_ops: implementation of paravirt_ops Andi Kleen
2006-08-07  5:56       ` Jeremy Fitzhardinge
2006-08-07  5:56         ` Jeremy Fitzhardinge
2006-08-07  6:13       ` Rusty Russell
2006-08-07  6:20         ` Andi Kleen
2006-08-07  6:20           ` Andi Kleen
2006-08-07  7:27           ` Rusty Russell
2006-08-07  5:40   ` [PATCH 2/4] x86 paravirt_ops: paravirt_desc.h for native descriptor ops Andi Kleen
2006-08-07  5:40     ` Andi Kleen
2006-08-07  7:50     ` Rusty Russell
2006-08-07  7:50       ` Rusty Russell
2006-08-07  8:53       ` Andi Kleen
2006-08-07 17:19         ` Dave Jones
2006-08-07 17:19           ` Dave Jones
2006-08-07  5:22 ` [PATCH 1/4] x86 paravirt_ops: create no_paravirt.h for native ops Jeremy Fitzhardinge
2006-08-07  5:30 ` Andi Kleen
2006-08-07  5:43   ` Jeremy Fitzhardinge
2006-08-07  6:02     ` Andi Kleen
2006-08-07  6:23       ` Jeremy Fitzhardinge
2006-08-07  6:03     ` Rusty Russell
2006-08-07  6:16       ` Andi Kleen
2006-08-07  6:04   ` Rusty Russell
2006-08-07  6:04     ` Rusty Russell
2006-08-07  6:17     ` Andi Kleen
2006-08-07  6:17       ` Andi Kleen
2006-08-07  6:27       ` Muli Ben-Yehuda
2006-08-07  6:27         ` Muli Ben-Yehuda
2006-08-07  7:34         ` Jan Engelhardt
2006-08-07  8:40           ` Muli Ben-Yehuda
2006-08-07  8:40             ` Muli Ben-Yehuda
2006-08-07 17:54             ` Jan Engelhardt
2006-08-07 17:54               ` Jan Engelhardt
2006-08-07 20:51     ` Zachary Amsden
2006-08-07 20:51       ` Zachary Amsden
2006-08-08  1:59       ` Andi Kleen
2006-08-08  1:59         ` 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=1154927700.7642.1.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.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.