From patchwork Tue Jun 28 19:12:40 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Riku Voipio X-Patchwork-Id: 641713 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from lists.gnu.org (lists.gnu.org [IPv6:2001:4830:134:3::11]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 3rfG5V2ZV2z9s1h for ; Wed, 29 Jun 2016 05:26:54 +1000 (AEST) Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=linaro.org header.i=@linaro.org header.b=G3hupUwt; dkim-atps=neutral Received: from localhost ([::1]:39055 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bHyeq-0001vv-6n for incoming@patchwork.ozlabs.org; Tue, 28 Jun 2016 15:26:52 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38345) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bHyRb-0001ql-QP for qemu-devel@nongnu.org; Tue, 28 Jun 2016 15:13:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bHyRa-0006qJ-LU for qemu-devel@nongnu.org; Tue, 28 Jun 2016 15:13:11 -0400 Received: from mail-lf0-x236.google.com ([2a00:1450:4010:c07::236]:33245) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bHyRa-0006q9-EL for qemu-devel@nongnu.org; Tue, 28 Jun 2016 15:13:10 -0400 Received: by mail-lf0-x236.google.com with SMTP id f6so18200311lfg.0 for ; Tue, 28 Jun 2016 12:13:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=G2UkHt6hWyZmDgGDHGovwFAR3gLwd0vEO7gy80O2cr0=; b=G3hupUwt5nm29Na9D8699zDwNvRXUuvBodG7M7u94W7wbpjfSk8f14MKnjzpftMM5h g1Ho0GJ9Wc4WI01G2H2al0QXb0ix08SezhXebXD85AI3awkRSr4m8yBWn8T616AR8GiL LlaQPai7GDJLOBx+MjySOnE9mDi8boA12gfG4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=G2UkHt6hWyZmDgGDHGovwFAR3gLwd0vEO7gy80O2cr0=; b=CPYydwR9wZgYTG+xIBsQaXKhwWRWEnIhucU79rsL6qlFOMRtEosJfjij9HytUjjo+4 Or4jzeyKLtTK9fmSuR2eZmK4fimxtTB7YhwTMP7ktXw9diMl6H6oJ/fV3S7jRMRYPsr5 8bN1/mKxjWd+Cx6PLgZuflkX3wLYfdqbb6eKbvY6vH+YgIBmF4qx/ewxz+vYlfrxU2Fk T7NlU1s1bNjBFLqO+GxyLKF48oAjZVjRcPaFNePc3Gd9lFI7qHdP/0yFdUSEARilb+f9 BE/z3LZ65oUUfvU9zg7vtxNYts4s18HyQqzJU2y3peTofJm90ucMDhNIgTLUTT+yd7Th w2qQ== X-Gm-Message-State: ALyK8tLiBldXBS+lWvNFkc2Xvj356mu8n+f4WrWXZqibE0iFLOUbOuMj9pEMpSVPDUpDr/Yi X-Received: by 10.25.20.23 with SMTP id k23mr1530289lfi.35.1467141189779; Tue, 28 Jun 2016 12:13:09 -0700 (PDT) Received: from beaming.home (91-157-170-157.elisa-laajakaista.fi. [91.157.170.157]) by smtp.gmail.com with ESMTPSA id h10sm4262823ljh.38.2016.06.28.12.13.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 28 Jun 2016 12:13:08 -0700 (PDT) From: riku.voipio@linaro.org To: qemu-devel@nongnu.org Date: Tue, 28 Jun 2016 22:12:40 +0300 Message-Id: X-Mailer: git-send-email 2.1.4 In-Reply-To: References: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:4010:c07::236 Subject: [Qemu-devel] [PULL v2 06/24] configure: Don't allow user-only targets for unknown CPU architectures X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Peter Maydell Errors-To: qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org Sender: "Qemu-devel" From: Peter Maydell For the user-only targets, we need to know something about the host CPU architecture even if we are using the TCI interpreter rather than TCG. (In particular user-exec.c has code for handling signals that needs to know about that host's context structures.) Specifically forbid building the user-only targets on unknown CPU architectures, rather than allowing them to configure but then fail when building user-exec.c. This change drops supports for two configurations which were theoretically possible before: * linux-user targets on M68K hosts using TCI * linux-user targets on HPPA hosts using TCI We don't think anybody is actually trying to use these in practice, though: * interpreted TCG on a slow host CPU would be unusably slow * the m68k user-exec.c support is missing is_write detection so guest code which writes to the same page it is executing from was broken (will include any guest program using signals) * HPPA TCG backend support was dropped two and a half years ago with no complaints Signed-off-by: Peter Maydell Reviewed-by: Laurent Vivier Reviewed-by: Richard Henderson Signed-off-by: Riku Voipio --- configure | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/configure b/configure index 6696316..dce20f0 100755 --- a/configure +++ b/configure @@ -1216,6 +1216,13 @@ esac QEMU_CFLAGS="$CPU_CFLAGS $QEMU_CFLAGS" EXTRA_CFLAGS="$CPU_CFLAGS $EXTRA_CFLAGS" +# For user-mode emulation the host arch has to be one we explicitly +# support, even if we're using TCI. +if [ "$ARCH" = "unknown" ]; then + bsd_user="no" + linux_user="no" +fi + default_target_list="" mak_wilds=""