[Patch]: adding physdev_op to hypercall.h

[Patch]: adding physdev_op to hypercall.h

[Tristan Gingold]

[-- Attachment #1: Type: text/plain, Size: 74 bytes --]

Hi,

very small patch to prepare comming soon patches on ia64.

Tristan.


[-- Attachment #2: xen-physdev.diffs --]
[-- Type: text/x-diff, Size: 596 bytes --]

# HG changeset patch
# User tristan.gingold@bull.net
# Node ID 51f2fb535796847337324cf6cad6a8d77b3bc014
# Parent  405f0f847c0f33381c69a04a168f34150a2bca7d
Declare do_physdev_op.

Signed-off-by: Tristan Gingold <tristan.gingold@bull.net>

diff -r 405f0f847c0f -r 51f2fb535796 xen/include/xen/hypercall.h
--- a/xen/include/xen/hypercall.h	Thu Mar  9 23:24:31 2006
+++ b/xen/include/xen/hypercall.h	Fri Mar 10 12:34:11 2006
@@ -83,4 +83,9 @@
     unsigned int cmd,
     void *arg);
 
+struct physdev_op;
+extern long
+do_physdev_op(
+    struct physdev_op *uop);
+
 #endif /* __XEN_HYPERCALL_H__ */

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: [Patch]: adding physdev_op to hypercall.h

[Keir Fraser]

On 10 Mar 2006, at 16:23, Tristan Gingold wrote:

> Hi,
>
> very small patch to prepare comming soon patches on ia64.

Firstly, it belongs on the ia64-devel list and in the ia64-devel tree.

Secondly, there's little point checking in the trivial patch alone -- 
may as well bundle it into the patch that actually defines and 
implements do_physdev_op().

  -- Keir

Re: [Patch]: adding physdev_op to hypercall.h

[Muli Ben-Yehuda]

On Fri, Mar 10, 2006 at 05:23:56PM +0100, Tristan Gingold wrote:

> Declare do_physdev_op.

What are the intended semantics of do_physdev_op?

Cheers,
Muli
-- 
Muli Ben-Yehuda
http://www.mulix.org | http://mulix.livejournal.com/

Re: [Patch]: adding physdev_op to hypercall.h

[Hollis Blanchard]

Keir Fraser wrote:
> 
> On 10 Mar 2006, at 16:23, Tristan Gingold wrote:
>> very small patch to prepare comming soon patches on ia64.
> 
> Firstly, it belongs on the ia64-devel list and in the ia64-devel tree.

I'm beginning to split out the arch-neutral changes we've made for PPC 
and intend to submit those individually to xen-devel so that each can be 
discussed as usual. Then once the changes we need are in, we can then 
drop in the whole xen/arch/ppc directory.

With Tristan's patch, which is to arch-neutral code, you seem to prefer 
it be part of the ia64 tree which you'll then pull later. What if you 
don't like some of their changes? Do you give them feedback only after 
they ask you to pull?

In general I assumed that patches that affect arch-neutral code should 
be submitted to xen-devel; is that not the case?

-- 
Hollis Blanchard
IBM Linux Technology Center

Re: [Patch]: adding physdev_op to hypercall.h

[Tristan Gingold]

Le Vendredi 10 Mars 2006 18:29, Muli Ben-Yehuda a écrit :
> On Fri, Mar 10, 2006 at 05:23:56PM +0100, Tristan Gingold wrote:
> > Declare do_physdev_op.
>
> What are the intended semantics of do_physdev_op?
See arch/x86/physdev.c.
It is mainly for interrupts.

Tristan.