All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Yeoh <cyeoh@au1.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-man@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: Cross Memory Attach v3
Date: Mon, 25 Jul 2011 16:32:07 +0930	[thread overview]
Message-ID: <20110725163207.27336094@lilo> (raw)
In-Reply-To: <20110721145433.a77818b2.akpm@linux-foundation.org>

On Thu, 21 Jul 2011 14:54:33 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> > 
> > The following patch attempts to achieve this by allowing a
> > destination process, given an address and size from a source
> > process, to copy memory directly from the source process into its
> > own address space via a system call. There is also a symmetrical
> > ability to copy from the current process's address space into a
> > destination process's address space.
> >
> > ...
> >
> >  arch/powerpc/include/asm/systbl.h  |    2 
> >  arch/powerpc/include/asm/unistd.h  |    4 
> >  arch/x86/include/asm/unistd_32.h   |    4 
> >  arch/x86/kernel/syscall_table_32.S |    2 
> >  fs/aio.c                           |    4 
> >  fs/compat.c                        |    7 
> >  fs/read_write.c                    |    8 
> >  include/linux/compat.h             |    3 
> >  include/linux/fs.h                 |    7 
> >  include/linux/syscalls.h           |   13 +
> >  mm/Makefile                        |    3 
> >  mm/process_vm_access.c             |  446
> > +++++++++++++++++++++++++++++++++++++
> > security/keys/compat.c             |    2
> > security/keys/keyctl.c             |    2 14 files changed, 490
> > insertions(+), 17 deletions(-)
> 
> Confused.  Why no arch/x86/include/asm/unistd_64.h wire-up?

I forgot. Have done this now as well as the 32-bit compat and am
retesting....

Chris
-- 
cyeoh@au.ibm.com

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Christopher Yeoh <cyeoh@au1.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-man@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: Cross Memory Attach v3
Date: Mon, 25 Jul 2011 16:32:07 +0930	[thread overview]
Message-ID: <20110725163207.27336094@lilo> (raw)
Message-ID: <20110725070207.QYYbOdbt9pzjEdZkPs_42HupGQmeALtTOtoO8W1n1Ig@z> (raw)
In-Reply-To: <20110721145433.a77818b2.akpm@linux-foundation.org>

On Thu, 21 Jul 2011 14:54:33 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> > 
> > The following patch attempts to achieve this by allowing a
> > destination process, given an address and size from a source
> > process, to copy memory directly from the source process into its
> > own address space via a system call. There is also a symmetrical
> > ability to copy from the current process's address space into a
> > destination process's address space.
> >
> > ...
> >
> >  arch/powerpc/include/asm/systbl.h  |    2 
> >  arch/powerpc/include/asm/unistd.h  |    4 
> >  arch/x86/include/asm/unistd_32.h   |    4 
> >  arch/x86/kernel/syscall_table_32.S |    2 
> >  fs/aio.c                           |    4 
> >  fs/compat.c                        |    7 
> >  fs/read_write.c                    |    8 
> >  include/linux/compat.h             |    3 
> >  include/linux/fs.h                 |    7 
> >  include/linux/syscalls.h           |   13 +
> >  mm/Makefile                        |    3 
> >  mm/process_vm_access.c             |  446
> > +++++++++++++++++++++++++++++++++++++
> > security/keys/compat.c             |    2
> > security/keys/keyctl.c             |    2 14 files changed, 490
> > insertions(+), 17 deletions(-)
> 
> Confused.  Why no arch/x86/include/asm/unistd_64.h wire-up?

I forgot. Have done this now as well as the 32-bit compat and am
retesting....

Chris
-- 
cyeoh@au.ibm.com

  reply	other threads:[~2011-07-25  7:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 15:05 Cross Memory Attach v3 Christopher Yeoh
2011-07-18 15:05 ` Christopher Yeoh
2011-07-21 21:54 ` Andrew Morton
2011-07-21 21:54   ` Andrew Morton
2011-07-21 21:54   ` Andrew Morton
2011-07-25  7:02   ` Christopher Yeoh [this message]
2011-07-25  7:02     ` Christopher Yeoh
2011-07-21 22:09 ` Andrew Morton
2011-07-21 22:09   ` Andrew Morton
2011-07-25  7:11   ` Christopher Yeoh
2011-07-25  7:11     ` Christopher Yeoh
2011-08-04  3:54   ` Cross Memory Attach v3 (includes updated patch based on v4) Christopher Yeoh
2011-08-04  3:54     ` Christopher Yeoh
2011-11-20 10:16 ` Cross Memory Attach v3 Geert Uytterhoeven
2011-11-20 10:16   ` Geert Uytterhoeven
2011-11-21  0:13   ` Christopher Yeoh
2011-11-21  0:13     ` Christopher Yeoh
2011-12-04 14:19     ` Geert Uytterhoeven
2011-12-04 14:19       ` Geert Uytterhoeven
2011-12-04 14:37       ` Thorsten Glaser
2011-12-04 16:28         ` Geert Uytterhoeven
2011-12-04 18:34         ` Andreas Schwab
2011-12-11 22:11           ` Thorsten Glaser
2011-12-13 10:59             ` Aurelien Jarno
2011-12-17  3:18               ` Thorsten Glaser

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=20110725163207.27336094@lilo \
    --to=cyeoh@au1.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.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.