From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MGbYr-0004m5-QQ for qemu-devel@nongnu.org; Tue, 16 Jun 2009 12:31:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MGbYq-0004lN-8r for qemu-devel@nongnu.org; Tue, 16 Jun 2009 12:31:01 -0400 Received: from [199.232.76.173] (port=56353 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MGbYp-0004lG-Q8 for qemu-devel@nongnu.org; Tue, 16 Jun 2009 12:30:59 -0400 Received: from dd21438.kasserver.com ([85.13.141.110]:47742) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MGbYp-0002Ie-8D for qemu-devel@nongnu.org; Tue, 16 Jun 2009 12:30:59 -0400 Message-ID: <4A37C8BF.5010209@opensuse.org> Date: Tue, 16 Jun 2009 18:30:55 +0200 From: Martin Mohring MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 00/21] Pending linux-user patches References: <20090615151033.GA26401@kos.to> In-Reply-To: <20090615151033.GA26401@kos.to> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Riku Voipio Cc: Blue Swirl , qemu-devel@nongnu.org Riku Voipio wrote: > On Sun, Jun 14, 2009 at 06:12:06PM +0300, Blue Swirl wrote: > >> On 6/12/09, riku.voipio@iki.fi wrote: >> >>> From: Riku Voipio >>> >>> All the things in linux-user tree at the moment: >>> >>> https://git.maemo.org/projects/qemu/gitweb?p=qemu;a=shortlog;h=refs/heads/linux-user-for-upstream >>> >>> Since the maemo git hosting regrettably only provides https >>> transport, you can download the git tree faster if you already >>> have a git tree: >>> >>> git clone git://git.sv.gnu.org/qemu.git >>> cd qemu >>> git remote add maemo https://git.maemo.org/projects/qemu >>> git fetch maemo >>> git checkout -b linux-user maemo/linux-user-for-upstream >>> >>> This tree is constantly rebased against upstream git HEAD, so avoid basing your >>> work on this branch. >>> > > >> Constantly? It's already three days old. :-) >> > > More accurate would be "whenever there is updates in the upstream linux-user/ > subdir that require rebasing", but that might give some people the impression > that it is actually rabased quite rarely ;-) > > >> Anyway, I pulled the patches with the intention of possibly committing >> them. But it looks some of them are not ready yet. >> > > The "From:" fields were not intended as signed-off-by replacements, but rather > to ensure that the authorship info is not lost. With the current mailer setup > the email header "From:" on the patches sent to the mailing list shows my address, > and I don't want to take anyones credit away. > > I'll have the look at the compiler warning, I didn't see any warnings on my build > env(s) before mailing. > Is there any chance to accept the bunch of these changes or any reason to reject them? I was told by some maintainers that currently there is no maintainer for user mode anymore. Is this true, and is this the reason? Or is the user mode support "officially" dropped / running out? I am just a bit confused about the slow acceptance of the user mode patches. To sum it up: due to changes in the host linux systems, currently you cannot run binaries anymore - even for ARM (e.g. because address 0 is not mapped anymore in the host). Also, to run more recent glibc code, the pending updates are needed to run these binaries in user mode. Martin