| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: [patch 03/26] Xen-paravirt_ops: use paravirt_nop to cons
|
To: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
|
Subject: |
[Xen-devel] Re: [patch 03/26] Xen-paravirt_ops: use paravirt_nop to consistently mark no-op operations |
|
From: |
Ingo Molnar <mingo@xxxxxxx> |
|
Date: |
Fri, 16 Mar 2007 10:44:32 +0100 |
|
Cc: |
Zachary Amsden <zach@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxx, Rusty Russell <rusty@xxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Chris Wright <chrisw@xxxxxxxxxxxx>, Andi Kleen <ak@xxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> |
|
Delivery-date: |
Fri, 16 Mar 2007 02:43:46 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<20070301232526.261284776@xxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<20070301232443.195603797@xxxxxxxx> <20070301232526.261284776@xxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mutt/1.4.2.2i |
* Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> Add a _paravirt_nop function for use as a stub for no-op operations,
> and paravirt_nop #defined void * version to make using it easier
> (since all its uses are as a void *).
>
> This is useful to allow the patcher to automatically identify noop
> operations so it can simply nop out the callsite.
Acked-by: Ingo Molnar <mingo@xxxxxxx>
> +void _paravirt_nop(void);
> +#define paravirt_nop ((void *)_paravirt_nop)
but only as a cleanup of the current open-coded (void *) casts. My
problem with this is that it loses the types. Not that there is much to
check for, but still, this adds some assumptions about how function
calls look like.
Ingo
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home