From: Richard Weinberger <richard@nod.at> To: Andrew Morton <akpm@linux-foundation.org> Cc: linux-kernel@vger.kernel.org, user-mode-linux-devel@lists.sourceforge.net Subject: Re: [PATCH 07/10] um: Set __HAVE_ARCH_GATE_AREA for x86_64 Date: Sat, 23 Jul 2011 14:15:08 +0200 [thread overview] Message-ID: <201107231415.08718.richard@nod.at> (raw) In-Reply-To: <20110722160127.ec061ab6.akpm@linux-foundation.org> Am Samstag 23 Juli 2011, 01:01:27 schrieb Andrew Morton: > On Thu, 21 Jul 2011 11:18:31 +0200 > > Richard Weinberger <richard@nod.at> wrote: > > Implement arch_vma_name() and make get_gate_vma(), > > in_gate_area() and in_gate_area_no_mm() a nop. > > > > We need arch_vma_name() to support vDSO. > > Well this is awkward. Why? Without it UML's vDSO will have no name. E.g. when reading /proc/<pid>/maps > > arch/um/sys-x86_64/asm/elf.h | 1 + > > arch/um/sys-x86_64/mem.c | 22 ++++++++++++++++++++++ > > 2 files changed, 23 insertions(+), 0 deletions(-) > > Your um-clean-up-vm-flagsh.patch deleted arch/um/sys-x86_64/mem.c. > > There's not really any appropriate .c file in arch/um/sys-x86_64 for > these functions so I changed the patch to reinstate mem.c. > > Then I changed my maind and dropped it ;) Hopefully none of the other > patches depended on this one. > > Then I looked at um-implement-a-x86_64-vdso.patch, got nervous and > undropped um-set-__have_arch_gate_area-for-x86_64.patch. I see, you've had some fun with this patch. ;-) Sorry for that, I completely forgot rebasing my patches to mmotm. Thanks, //richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard@nod.at> To: Andrew Morton <akpm@linux-foundation.org> Cc: linux-kernel@vger.kernel.org, user-mode-linux-devel@lists.sourceforge.net Subject: Re: [uml-devel] [PATCH 07/10] um: Set __HAVE_ARCH_GATE_AREA for x86_64 Date: Sat, 23 Jul 2011 14:15:08 +0200 [thread overview] Message-ID: <201107231415.08718.richard@nod.at> (raw) In-Reply-To: <20110722160127.ec061ab6.akpm@linux-foundation.org> Am Samstag 23 Juli 2011, 01:01:27 schrieb Andrew Morton: > On Thu, 21 Jul 2011 11:18:31 +0200 > > Richard Weinberger <richard@nod.at> wrote: > > Implement arch_vma_name() and make get_gate_vma(), > > in_gate_area() and in_gate_area_no_mm() a nop. > > > > We need arch_vma_name() to support vDSO. > > Well this is awkward. Why? Without it UML's vDSO will have no name. E.g. when reading /proc/<pid>/maps > > arch/um/sys-x86_64/asm/elf.h | 1 + > > arch/um/sys-x86_64/mem.c | 22 ++++++++++++++++++++++ > > 2 files changed, 23 insertions(+), 0 deletions(-) > > Your um-clean-up-vm-flagsh.patch deleted arch/um/sys-x86_64/mem.c. > > There's not really any appropriate .c file in arch/um/sys-x86_64 for > these functions so I changed the patch to reinstate mem.c. > > Then I changed my maind and dropped it ;) Hopefully none of the other > patches depended on this one. > > Then I looked at um-implement-a-x86_64-vdso.patch, got nervous and > undropped um-set-__have_arch_gate_area-for-x86_64.patch. I see, you've had some fun with this patch. ;-) Sorry for that, I completely forgot rebasing my patches to mmotm. Thanks, //richard ------------------------------------------------------------------------------ Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2011-07-23 12:15 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-21 9:18 [PATCH 01/10] uml: cow_user.c warning corrections Richard Weinberger 2011-07-21 9:18 ` [uml-devel] " Richard Weinberger 2011-07-21 9:18 ` [PATCH 02/10] uml: helper.c " Richard Weinberger 2011-07-21 9:18 ` [uml-devel] " Richard Weinberger 2011-07-21 9:18 ` [PATCH 03/10] uml: drivers/slip_user.c memory leak fix Richard Weinberger 2011-07-21 9:18 ` [uml-devel] " Richard Weinberger 2011-07-21 9:18 ` [PATCH 04/10] uml: free resources Richard Weinberger 2011-07-21 9:18 ` [uml-devel] " Richard Weinberger 2011-07-21 9:18 ` [PATCH 05/10] um: Disable scan_elf_aux() on x86_64 Richard Weinberger 2011-07-21 9:18 ` [uml-devel] " Richard Weinberger 2011-07-21 9:18 ` [PATCH 06/10] um: Set __HAVE_ARCH_GATE_AREA for i386 Richard Weinberger 2011-07-21 9:18 ` [uml-devel] " Richard Weinberger 2011-07-21 9:18 ` [PATCH 07/10] um: Set __HAVE_ARCH_GATE_AREA for x86_64 Richard Weinberger 2011-07-21 9:18 ` [uml-devel] " Richard Weinberger 2011-07-22 23:01 ` Andrew Morton 2011-07-23 12:15 ` Richard Weinberger [this message] 2011-07-23 12:15 ` [uml-devel] " Richard Weinberger 2011-07-21 9:18 ` [PATCH 08/10] um: Implement a x86_64 vDSO Richard Weinberger 2011-07-21 9:18 ` [PATCH 09/10] um: Ajdust size of pid_buf Richard Weinberger 2011-07-21 9:18 ` [uml-devel] " Richard Weinberger 2011-07-21 9:38 ` Geert Uytterhoeven 2011-07-21 9:48 ` Richard Weinberger 2011-07-21 9:18 ` [PATCH 10/10] um: Remove dead code Richard Weinberger 2011-07-21 9:18 ` [uml-devel] " Richard Weinberger
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=201107231415.08718.richard@nod.at \ --to=richard@nod.at \ --cc=akpm@linux-foundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=user-mode-linux-devel@lists.sourceforge.net \ /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: linkBe 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.