2008/226: mmapfd(2) - mmap file descriptor

2008-04-06 Thread Roland Mainz
Michael Corcoran wrote: On Mon, 2008-03-31 at 13:37 +0200, Roland Mainz wrote: Rod Evans wrote: I'm sponsoring the following case for Mike Corcoran. Time out 04/07/08. The case introduces a new system call, mmapfd(2). This call is primarily targeted for use by ld.so.1(1), and

2008/226: mmapfd(2) - mmap file descriptor

2008-04-06 Thread Roland Mainz
Blake Jones wrote: [snip] To elaborate on this: part of the idea behind mmapfd() is that it gives the kernel the flexibility to make global-scope decisions about where and how a file should be mapped. This includes the appropriate page size to use (which might vary depending on what platform

2008/226: mmapfd(2) - mmap file descriptor

2008-04-06 Thread Roland Mainz
Edward Pilatowicz wrote: On Mon, Mar 31, 2008 at 11:46:34AM -0700, Michael Corcoran wrote: On Mon, 2008-03-31 at 10:30 +0100, Darren J Moffat wrote: I find the function name a bit strange. So strange in fact it made me look at the mmap(2) man page to check that it wasn't taking a char*

2008/226: mmapfd(2) - mmap file descriptor

2008-04-06 Thread Roland Mainz
Nicolas Williams wrote: On Mon, Mar 31, 2008 at 01:37:42PM +0200, Roland Mainz wrote: Rod Evans wrote: mmapfd(int fd, uint_t flags, mmapfd_result_t *storage, uint_t *elements, void *arg) Uhm... how do I unmap the mapping done by |mmapfd()| ? I thought that was clear (each

2008/226 mmapfd and 2008/195 validated execution

2008-04-06 Thread Roland Mainz
Bart Smaalders wrote: John Zolnowsky x69422/408-404-5064 wrote: The general nature of mmapfd() mapping represents a possible solution to a concern being discussed in 2008/195. The issue is that interpreters other than rtld often have the equivalent of libraries, for example, perl's .pm

PSARC 2008/212 Integrate Unison into Solaris

2008-04-06 Thread Roland Mainz
Yan Xue Yang wrote: Roland Mainz: Yan Xue Yang wrote: Roland Mainz : Yan Xue Yang wrote: Roland Mainz : Yan Xue Yang wrote: Roland Mainz : Which locale did you use (my main interest is whether non-UTF-8 multibyte encodings as used for zh_CN.GB18030 will work or not...) ? I used

PSARC/2008/237 Libvirt for LDoms support

2008-04-06 Thread John Levon
On Fri, Apr 04, 2008 at 02:55:33PM -0700, Dan Hain wrote: virsh is included in libvirt. virsh is built on top of libvirt and allows a user to interact with the hypervisor and guest domains. With the LDoms support, a user can run virsh to interact with the LDoms hypervisor as below: