From: Hollis Blanchard <hollisb@us.ibm.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com,
Keir Fraser <keir.fraser@xensource.com>,
xen-ppc-devel@lists.xensource.com
Subject: Re: Re: [Xen-devel] [PATCH 6 of 6] [XEN][LINUX] Add 32-bit privcmd ioctlconversion for 64-b
Date: Fri, 06 Jul 2007 13:17:03 -0500 [thread overview]
Message-ID: <1183745823.3008.18.camel@basalt> (raw)
In-Reply-To: <468E854E.76E4.0078.0@novell.com>
On Fri, 2007-07-06 at 17:09 +0100, Jan Beulich wrote:
> >>> Hollis Blanchard <hollisb@us.ibm.com> 06.07.07 17:44 >>>
> >> Where does the hypercall argument translation happen?
> >
> >It happens inside privcmd_hypercall(). See
> >http://xenbits.xensource.com/ext/linux-ppc-2.6.hg?file/04f6ad5d9232/arch/powerpc/platforms/xen/hcall.c
> >
> >(In that tree, the function is named "arch_privcmd_hypercall".) IA64 and
> >PPC both implement this function now; only x86 is left with #ifdefs in
> >drivers/xen/privcmd/privcmd.c .
> >
> >COMPATIBLE_IOCTL is just about the ioctl itself, not the sub-structures.
>
> Hmm, I can't really see any structures being translated there, all I see is
> guest handles getting dereferenced. So I'm still unclear where you do the
> 32-bit layout to 64-bit layout conversion, but obviously I must be missing
> something.
Which structures do you think need further conversion?
We've already fixed all the shared structures (e.g. sysctl) to use
explicitly-sized types, so the PowerPC port has always had proper
interfaces. For example, look at the definition of xen_ulong_t on the
different architectures. The x86 interfaces were frozen too early,
cementing this problem for you.
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2007-07-06 18:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 22:27 [PATCH 0 of 6] PowerPC Linux patches, rev 2 Hollis Blanchard
2007-07-05 22:27 ` [PATCH 1 of 6] [XEN][LINUX] Add Kconfig option for the balloon driver Hollis Blanchard
2007-07-05 22:27 ` [PATCH 2 of 6] [XEN][LINUX] Create Xen-specific interface for xlate_dev_mem_* Hollis Blanchard
2007-07-06 8:01 ` [PATCH 2 of 6] [XEN][LINUX] Create Xen-specificinterface " Jan Beulich
2007-07-05 22:27 ` [PATCH 3 of 6] [XEN][LINUX] Add architecture-generic xencomm infrastructure Hollis Blanchard
2007-07-05 22:27 ` [PATCH 4 of 6] [XEN][LINUX] Invert #ifdef for x86-specific *_vm_area() Hollis Blanchard
2007-07-05 22:27 ` [PATCH 5 of 6] [XEN][LINUX] Refactor grant table allocation into arch-specific code Hollis Blanchard
2007-07-06 8:04 ` [PATCH 5 of 6] [XEN][LINUX] Refactor grant tableallocation " Jan Beulich
2007-07-06 13:16 ` [PATCH 5 of 6] [XEN][LINUX] Refactor grant table allocation " Keir Fraser
2007-07-05 22:27 ` [PATCH 6 of 6] [XEN][LINUX] Add 32-bit privcmd ioctl conversion for 64-bit kernels Hollis Blanchard
2007-07-06 8:09 ` [PATCH 6 of 6] [XEN][LINUX] Add 32-bit privcmd ioctlconversion " Jan Beulich
2007-07-06 9:29 ` Keir Fraser
2007-07-06 15:44 ` [XenPPC] " Hollis Blanchard
2007-07-06 16:09 ` [XenPPC] Re: [PATCH 6 of 6] [XEN][LINUX] Add 32-bit privcmd ioctlconversion for 64-b Jan Beulich
2007-07-06 18:17 ` Hollis Blanchard [this message]
2007-07-09 9:03 ` Jan Beulich
2007-07-09 9:11 ` Keir Fraser
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=1183745823.3008.18.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=jbeulich@novell.com \
--cc=keir.fraser@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ppc-devel@lists.xensource.com \
/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.