From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.2 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,FORGED_GMAIL_RCVD, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 9E2A61F463 for ; Thu, 12 Sep 2019 01:13:34 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:in-reply-to; q=dns; s=default; b=ix9M WkZA1aatJv45J2Vo8pXDci1kY5DrO/s3kAUdTMbg5AbUfa4wNdrOjX/D753VliYV rMbx4N7BpXZ4fAko48yYUUCvxNnsk+lASyHJE8bZuUeMadCnDgb7XXQnumby72xv dTB4m6bwGI+L1h3UDvVDqilAwqhCU7PJHdXCN+M= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:in-reply-to; s=default; bh=ZbrlVehn/f r7IdQ36N/PUtecteA=; b=vHsHEZ2yYMBWcATESGpva2RWr5FvXfmtuSiD3hj3Ox 1y3iwBDG+0QXpqUrtprNf1A7pqYQ8ELvknrWMeCQeds2bqKwvEEQdufANlMOt/M7 AL3GuJWMH423tOmZgIFCi6UZbT6JyU6/EVJxNLVWZuzYvVH4poXMs8qAJQDkfuLa 8= Received: (qmail 38225 invoked by alias); 12 Sep 2019 01:13:32 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 38215 invoked by uid 89); 12 Sep 2019 01:13:31 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: mail-pg1-f196.google.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=kL9poB0F9LfGsHEOqT2tY+mscmEQR6GYKEJ0z/D5+jY=; b=lrEuN+CDf3PMddCLF89St3pwrhxaV8/QAEEjrXVU+3bmyEidhiB0Qoc0VJrk6bWwwu Q2M4dF3OIjHzLVnDVfKoKNo6w4om8pAmCH+W9Ymnk3TsBX7Hq1kcDS7SvYlRYAEns7hd nODoaKf0H71u7borIi5xU1+bORNt0gKFYx9sDzHBZfP+RKLNLjXZhIbE42Rz2CE2oIz2 +2P0wZ6FyOrP5dX/Yf4N/Xd4bnmMtZyHJ9pi0/g9nhAbZCMBP14vFKSOiP/fHHjuZf/w Irz5BcHgT2LXhwGNtPFBVunlXFBQW6NHPlFJcA11D2q7fQmzkOHEwm8wY/HE2rWOM7qj Oyiw== Date: Wed, 11 Sep 2019 18:13:26 -0700 From: Isaku Yamahata To: Joseph Myers Cc: Isaku Yamahata , libc-alpha@sourceware.org, isaku.yamahata@intel.com Subject: Re: [RFC PATCH 00/11] Library OS support Message-ID: <20190912011326.GA28254@private.email.ne.jp> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Thanks for feedback. On Thu, Sep 12, 2019 at 12:10:32AM +0000, Joseph Myers wrote: > On Wed, 11 Sep 2019, Isaku Yamahata wrote: > > > This patch is to add Library OS(LibOS in short) to glibc. > > This is the first version of patch series to support LibOS. > > I don't see anything here about host triplets being used. I'd expect > x86_64-*-libos or similar (with consequent config.sub changes being > submitted to GNU config.git) but there's nothing to indicate that, and the > patch series is lacking documentation (NEWS, install.texi / regeneration > of INSTALL, other .texi files if applicable). I'd also expect any new OS > to have appropriate additions to build-many-glibcs.py. There are a great > many complications specific to existing GNU/Linux ABIs that ought to be > irrelevant in this case (compat support for old symbol versions, > enable-kernel support for different minimum kernel versions, etc.). Let me clarify my scope. Multiple LibOSes (typically) emulate Linux system call (with some change). LibOSes can run unmodified (dynamically linked) Linux executables (with modified libc as shared library). For example, its invocation looks like as follows. native case: $ linux-executable LibOS case: $ libos_loader linux-executable I'd like to have x86_64-*-linux support both native linux and multiple LibOSes with single version of binary. If we have multiple versions, for example, x86_64-*-linux x86_64-*-linux_libosX x86_64-*-linux_libosY ... it doesn't scale. It will cause maintenance hell. > Given the modification of generic files, you should verify that installed > stripped shared libraries for e.g. x86_64-linux-gnu are byte-for-byte > identical before and after the patch (or justify them not being so if they > aren't identical - I'd expect justifications of the form "this file has > line numbers in assertions that change"). > > There should not be any __x86_64__ conditionals in generic files; the > sysdeps structure should be used as appropriate instead. Sure. Let me address it with next respin. Thanks, -- Isaku Yamahata