From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D154DC433F5 for ; Wed, 19 Jan 2022 11:53:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1354359AbiASLxG (ORCPT ); Wed, 19 Jan 2022 06:53:06 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]:44064 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1354363AbiASLxD (ORCPT ); Wed, 19 Jan 2022 06:53:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1642593183; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=J9Mk8x6h3+3pv2pI2IYU/SKL9nrxKC/9/vUTNplQZ3o=; b=H1ff2Q8x3eJKRfsW7cLCwPjgLenuFrFsgXf1bbGZS+BB18o9znPW/XqAaIlHD1dLjIumEM 7GFdj5PBlXfU67kNnZ3n0XFczLWlH8Fj5rbfkV/tWHDaJv6HhYJYpLGHv/f9shkoteX20n F7DemMhGOut4CdMVCsK0W2m1Y5LZ33s= Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-653-sxYvnRCGNiaSanIxcqnD5A-1; Wed, 19 Jan 2022 06:53:02 -0500 X-MC-Unique: sxYvnRCGNiaSanIxcqnD5A-1 Received: by mail-wm1-f71.google.com with SMTP id s190-20020a1ca9c7000000b00347c6c39d9aso1741594wme.5 for ; Wed, 19 Jan 2022 03:53:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=J9Mk8x6h3+3pv2pI2IYU/SKL9nrxKC/9/vUTNplQZ3o=; b=O0N80jOOCWACjM4D4pkLxoC7ccqSbinAhRfY1OE54efqYV8OB4K8ng3ih4HrebBTZ4 +JDHhhTKR6xuPqlF5ZuXWiY4iK0ry/SW90i5UZIvuSB5tvNZKnHMUQ+A8KrmSDlnBIYO VUJt99vTKIWwom2dWE3+kjR5o3ajHMLK//GLCpnf3T9lbKv8eS4edPB5aVK1Kt1AccwH GQA5DyG5Yvb8xrq+UsluTfQ3yV1OL3epsxsyRTMJs902FujpMDLAtbepaf2jKpGkeDBz WUOpxJ9poRksrTUyONxoHxkmZrvmSverN3yh+oOeewU0Zl0I4PJuTCECB6wtiUZEBE6e b4Vw== X-Gm-Message-State: AOAM5318Cv8gaF6YHyNV8S96wl93lvYxKaKBWxurnlLJdqGSvtcnsmd5 Bi1XqZCS9JH7K1xdp8a4uFt3xqBSaO0sG00B7QLBpD+ocY7MiSxcMztVWDua82z/Cp7Sz6gtQQB 2NbK9hf4mLBi0juO+rCvu/g== X-Received: by 2002:a5d:690c:: with SMTP id t12mr29073773wru.536.1642593180966; Wed, 19 Jan 2022 03:53:00 -0800 (PST) X-Google-Smtp-Source: ABdhPJz+coOAxfk7/pEhrWiTHo6300RiSHyo2Xld6RFO2DMG3eym1SZ8ER4ToceMXeLTZvGpp1oxBA== X-Received: by 2002:a5d:690c:: with SMTP id t12mr29073761wru.536.1642593180763; Wed, 19 Jan 2022 03:53:00 -0800 (PST) Received: from [192.168.8.100] (tmo-096-151.customers.d1-online.com. [80.187.96.151]) by smtp.gmail.com with ESMTPSA id l13sm5267757wmq.22.2022.01.19.03.52.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 19 Jan 2022 03:53:00 -0800 (PST) Message-ID: Date: Wed, 19 Jan 2022 12:52:58 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: [RFC PATCH v1 06/10] KVM: s390: Add vm IOCTL for key checked guest absolute memory access Content-Language: en-US To: Janis Schoetterl-Glausch , Christian Borntraeger , Janosch Frank , Heiko Carstens , Vasily Gorbik Cc: David Hildenbrand , Claudio Imbrenda , Alexander Gordeev , kvm@vger.kernel.org, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org References: <20220118095210.1651483-1-scgl@linux.ibm.com> <20220118095210.1651483-7-scgl@linux.ibm.com> From: Thomas Huth In-Reply-To: <20220118095210.1651483-7-scgl@linux.ibm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-s390@vger.kernel.org On 18/01/2022 10.52, Janis Schoetterl-Glausch wrote: > Channel I/O honors storage keys and is performed on absolute memory. > For I/O emulation user space therefore needs to be able to do key > checked accesses. Can't we do the checking in userspace? We already have functions for handling the storage keys there (see hw/s390x/s390-skeys-kvm.c), so why can't we do the checking in QEMU? Thomas