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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A2BD1C433EF for ; Fri, 5 Nov 2021 06:25:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 77DDE6113B for ; Fri, 5 Nov 2021 06:25:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231700AbhKEG2R (ORCPT ); Fri, 5 Nov 2021 02:28:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59566 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229456AbhKEG2R (ORCPT ); Fri, 5 Nov 2021 02:28:17 -0400 Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 29A5AC061714 for ; Thu, 4 Nov 2021 23:25:38 -0700 (PDT) Received: by mail-pf1-x42a.google.com with SMTP id x64so8057848pfd.6 for ; Thu, 04 Nov 2021 23:25:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=83I8KWJOKgy+kYsvOfvG78wBhuMiPl6vZLrWNC92y68=; b=f0zOuYJ0R/98fpq8DKHySf+sIvIHFTfBCgK4n/d1EoCYiWKyKR4aA9jyvDyhdxbmfr YHMxJQyuINQTM1ibyysDpCkDj4+38zSsX2BREDDSfg58sWjoxCBvGIz30WjMfr09FIAx qUoe6oDOD8Oo3CD6/eTDmaXtgyRP9SgtmzHX2pwZrY/K+2PJzt9HGdnYXg42zZ2nKvms q6HtKdspaQ14CR3pB6ICiUM7gOtLAjb6TUNmxUnX6kWrrDE5YPGoO4Dr0iPtg4EyQkoo l6+OfBra1fHrmBAWTk3hgQc6MY8RjVhsDu8IBTxpH/Tsc3unRhpAoM2z143bLz6nMVOk wD8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=83I8KWJOKgy+kYsvOfvG78wBhuMiPl6vZLrWNC92y68=; b=6B/Pfax8Yxj5GcSK0h6vlWkuUYyOuEtXjB3BlYupXqXwLmh/EOziONIwKK0MLqFKKG 8JrK6ReVC0To4xigQRmsHL304h5aqshGekRL9IxK+dfVA1d0wblfNfkfvgqKbLiNr3BL dlbk9P4TY5/vH9eUyE20u6iZIn8KbnKzJQQ//LeXjv54TRyIiNvi4Ubz8rKAOPLzdVYG 3FvXCxwV4NIDx7g0kC6fQVHwJBGw1Zy/6KhhhmD5meUfvMeP/P/VL5VAd1Zd8C5ORl32 5tcIBDsMwZFQrSO5TUvEN1PMeBaPXwzdGRjEpNCE44qh78TVNqlcFyQdrU46fGjfWzsT Sp2Q== X-Gm-Message-State: AOAM532N93spcFoPsNxXhaNW3Sf4ml+qd8ETPTkJlOotHvuzP7zSAbce w9d3a1K8g8HY/ulu9ClWP+5Yg1qtyvbIPZdNalpVhg== X-Google-Smtp-Source: ABdhPJxw9VnfnHe9u50el4lnxVAR9qUrlhodBzmSVS92D4DmQlKkuRP7Li6Zcj7Slw2kIxX2GwblXLsXIsFv3YBquzU= X-Received: by 2002:aa7:8246:0:b0:44b:4870:1b09 with SMTP id e6-20020aa78246000000b0044b48701b09mr58421337pfn.82.1636093537523; Thu, 04 Nov 2021 23:25:37 -0700 (PDT) MIME-Version: 1.0 References: <20211103062520.1445832-1-reijiw@google.com> <20211103062520.1445832-3-reijiw@google.com> In-Reply-To: From: Reiji Watanabe Date: Thu, 4 Nov 2021 23:25:21 -0700 Message-ID: Subject: Re: [RFC PATCH v2 02/28] KVM: arm64: Save ID registers' sanitized value per vCPU To: Oliver Upton Cc: Marc Zyngier , kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, James Morse , Alexandru Elisei , Suzuki K Poulose , Paolo Bonzini , Will Deacon , Andrew Jones , Peng Liang , Peter Shier , Ricardo Koller , Jing Zhang , Raghavendra Rao Anata Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Thu, Nov 4, 2021 at 2:39 PM Reiji Watanabe wrote: > > Hi Oliver, > > On Thu, Nov 4, 2021 at 9:14 AM Oliver Upton wrote: > > > > Hi Reiji, > > > > On Tue, Nov 02, 2021 at 11:24:54PM -0700, Reiji Watanabe wrote: > > > Extend sys_regs[] of kvm_cpu_context for ID registers and save ID > > > registers' sanitized value in the array for the vCPU at the first > > > vCPU reset. Use the saved ones when ID registers are read by > > > userspace (via KVM_GET_ONE_REG) or the guest. > > > > Based on my understanding of the series, it appears that we require the > > CPU identity to be the same amongst all vCPUs in a VM. Is there any > > value in keeping a single copy in kvm_arch? > > Yes, that's a good point. > It reminded me that the idea bothered me after we discussed a similar > case about your counter offset patches, but I didn't seriously > consider that. > > Thank you for bringing this up. > I will look into keeping it per VM in kvm_arch. I just remembered that I made the prototype that kept ID registers per VM as the option B (, which introduced per VM ID register configuration API though...). Anyway, I've noticed that requiring the consistency of ID registers amongst vCPUs in a VM affects KVM_ARM_VCPU_INIT API, with which userspace can currently configure different features for each vCPUs. I'm not sure if any existing userspace program practically does that though. Now, I think I should rather remove that consistency requirement... (at least for features that can be configured by KVM_ARM_VCPU_INIT) Thanks, Reiji 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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 05D06C433EF for ; Fri, 5 Nov 2021 06:25:43 +0000 (UTC) Received: from mm01.cs.columbia.edu (mm01.cs.columbia.edu [128.59.11.253]) by mail.kernel.org (Postfix) with ESMTP id 684F96124F for ; Fri, 5 Nov 2021 06:25:42 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 684F96124F Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.cs.columbia.edu Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id B3B7A4A49C; Fri, 5 Nov 2021 02:25:41 -0400 (EDT) X-Virus-Scanned: at lists.cs.columbia.edu Authentication-Results: mm01.cs.columbia.edu (amavisd-new); dkim=softfail (fail, message has been altered) header.i=@google.com Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Y4d8PV1VzGF; Fri, 5 Nov 2021 02:25:40 -0400 (EDT) Received: from mm01.cs.columbia.edu (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 86A5F4B0CE; Fri, 5 Nov 2021 02:25:40 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id F25224A49C for ; Fri, 5 Nov 2021 02:25:39 -0400 (EDT) X-Virus-Scanned: at lists.cs.columbia.edu Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5l+t46D2zoCe for ; Fri, 5 Nov 2021 02:25:38 -0400 (EDT) Received: from mail-pf1-f170.google.com (mail-pf1-f170.google.com [209.85.210.170]) by mm01.cs.columbia.edu (Postfix) with ESMTPS id 7BD7D4031F for ; Fri, 5 Nov 2021 02:25:38 -0400 (EDT) Received: by mail-pf1-f170.google.com with SMTP id g18so3271074pfk.5 for ; Thu, 04 Nov 2021 23:25:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=83I8KWJOKgy+kYsvOfvG78wBhuMiPl6vZLrWNC92y68=; b=f0zOuYJ0R/98fpq8DKHySf+sIvIHFTfBCgK4n/d1EoCYiWKyKR4aA9jyvDyhdxbmfr YHMxJQyuINQTM1ibyysDpCkDj4+38zSsX2BREDDSfg58sWjoxCBvGIz30WjMfr09FIAx qUoe6oDOD8Oo3CD6/eTDmaXtgyRP9SgtmzHX2pwZrY/K+2PJzt9HGdnYXg42zZ2nKvms q6HtKdspaQ14CR3pB6ICiUM7gOtLAjb6TUNmxUnX6kWrrDE5YPGoO4Dr0iPtg4EyQkoo l6+OfBra1fHrmBAWTk3hgQc6MY8RjVhsDu8IBTxpH/Tsc3unRhpAoM2z143bLz6nMVOk wD8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=83I8KWJOKgy+kYsvOfvG78wBhuMiPl6vZLrWNC92y68=; b=qweQOSrvA1RXxYojNBCu3271Vmlu7iYpea1ZnzVfJSeBJrV4n79wwgRNz24ZEL7pHU qTA2ghxZgQcvjPniYBT8k7NJ8qOJGZV7KsZuPJ6WHOOj+6Cwh+zjfvABThq8ThkjtfNE XHrWtfWC69Ngwv77PiB/2PW19VpH+YDrFOZUhDboELHiOOU1Pk38zI2NNXPC8wBqRp3z qazoAvxTbhixjgMWifDncbizvX57qdo7ZGxu0SKTtqxkRdT4vIIC6C2qvX1AnrVtZYbw YCSWSOXqkWLMN3T0clm6pVKI0MDWiMAHM78Tv1VQAip5RFYFy0qhrmzdp3akcGJbbhP/ kIrw== X-Gm-Message-State: AOAM5320Zqda5IvRcBftOyNE4UZtx0T6l9Kx8G2jAmYFbAaMFUVzRQon oJPd4lzqLT4956C5jyPYnmxHruXI71ZFxHNQm1s6Lg== X-Google-Smtp-Source: ABdhPJxw9VnfnHe9u50el4lnxVAR9qUrlhodBzmSVS92D4DmQlKkuRP7Li6Zcj7Slw2kIxX2GwblXLsXIsFv3YBquzU= X-Received: by 2002:aa7:8246:0:b0:44b:4870:1b09 with SMTP id e6-20020aa78246000000b0044b48701b09mr58421337pfn.82.1636093537523; Thu, 04 Nov 2021 23:25:37 -0700 (PDT) MIME-Version: 1.0 References: <20211103062520.1445832-1-reijiw@google.com> <20211103062520.1445832-3-reijiw@google.com> In-Reply-To: From: Reiji Watanabe Date: Thu, 4 Nov 2021 23:25:21 -0700 Message-ID: Subject: Re: [RFC PATCH v2 02/28] KVM: arm64: Save ID registers' sanitized value per vCPU To: Oliver Upton Cc: kvm@vger.kernel.org, Marc Zyngier , Peter Shier , Will Deacon , Paolo Bonzini , kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org X-BeenThere: kvmarm@lists.cs.columbia.edu X-Mailman-Version: 2.1.14 Precedence: list List-Id: Where KVM/ARM decisions are made List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu On Thu, Nov 4, 2021 at 2:39 PM Reiji Watanabe wrote: > > Hi Oliver, > > On Thu, Nov 4, 2021 at 9:14 AM Oliver Upton wrote: > > > > Hi Reiji, > > > > On Tue, Nov 02, 2021 at 11:24:54PM -0700, Reiji Watanabe wrote: > > > Extend sys_regs[] of kvm_cpu_context for ID registers and save ID > > > registers' sanitized value in the array for the vCPU at the first > > > vCPU reset. Use the saved ones when ID registers are read by > > > userspace (via KVM_GET_ONE_REG) or the guest. > > > > Based on my understanding of the series, it appears that we require the > > CPU identity to be the same amongst all vCPUs in a VM. Is there any > > value in keeping a single copy in kvm_arch? > > Yes, that's a good point. > It reminded me that the idea bothered me after we discussed a similar > case about your counter offset patches, but I didn't seriously > consider that. > > Thank you for bringing this up. > I will look into keeping it per VM in kvm_arch. I just remembered that I made the prototype that kept ID registers per VM as the option B (, which introduced per VM ID register configuration API though...). Anyway, I've noticed that requiring the consistency of ID registers amongst vCPUs in a VM affects KVM_ARM_VCPU_INIT API, with which userspace can currently configure different features for each vCPUs. I'm not sure if any existing userspace program practically does that though. Now, I think I should rather remove that consistency requirement... (at least for features that can be configured by KVM_ARM_VCPU_INIT) Thanks, Reiji _______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm 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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E72CFC433F5 for ; Fri, 5 Nov 2021 06:27:07 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A23CE61056 for ; Fri, 5 Nov 2021 06:27:07 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org A23CE61056 Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=upwt8E2bqXPFjpX1wGue5TMO/DsT4JFYnkMOv3oYedY=; b=20P+1eQTxp1HZo Wvcq1eh9P9M0aNcl1NHdFKu2BiSWfECBzgY0CN4svDlcgNY5P0avNEfEeHMt7/HUWaVAGrRgqMlEv ESqhZ0RcNKptXRjeiKoFmfspTqw/OxgioqjASu0l42RMk9/QPKgII3nfQWFhd17RlZo/yofTuQENt oCY3bs4FtbAREM51IO10dJxVZBNSbbnrzvtwJJgzX2vRbdEJtocBeRW9eGPLSaZH9sonqFy08fEYi GFWbrp34fGA8Pkk+N1T737cWfop1gJP9vqBUa6OgassEVlWbUqSwwh4Yk27umAqDx62g3CanHJPgh 6evs65OJYdsk7vAO2Lpg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1misfV-00AhbT-Km; Fri, 05 Nov 2021 06:25:41 +0000 Received: from mail-pf1-x435.google.com ([2607:f8b0:4864:20::435]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1misfS-00Ahav-J7 for linux-arm-kernel@lists.infradead.org; Fri, 05 Nov 2021 06:25:39 +0000 Received: by mail-pf1-x435.google.com with SMTP id n85so3547903pfd.10 for ; Thu, 04 Nov 2021 23:25:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=83I8KWJOKgy+kYsvOfvG78wBhuMiPl6vZLrWNC92y68=; b=f0zOuYJ0R/98fpq8DKHySf+sIvIHFTfBCgK4n/d1EoCYiWKyKR4aA9jyvDyhdxbmfr YHMxJQyuINQTM1ibyysDpCkDj4+38zSsX2BREDDSfg58sWjoxCBvGIz30WjMfr09FIAx qUoe6oDOD8Oo3CD6/eTDmaXtgyRP9SgtmzHX2pwZrY/K+2PJzt9HGdnYXg42zZ2nKvms q6HtKdspaQ14CR3pB6ICiUM7gOtLAjb6TUNmxUnX6kWrrDE5YPGoO4Dr0iPtg4EyQkoo l6+OfBra1fHrmBAWTk3hgQc6MY8RjVhsDu8IBTxpH/Tsc3unRhpAoM2z143bLz6nMVOk wD8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=83I8KWJOKgy+kYsvOfvG78wBhuMiPl6vZLrWNC92y68=; b=R/vLujaSOT9zmzSFNPsjvW0km06sPSkbuQA4GuUTUVNcI6/VL0SpF+EypzPuhRp+Zh uttml2jKoPBjOVzoib1M7db+cqiaNQYUEOIrbx6PRdFpbJToPGiq6GHeLPSmvqa96CTk 2wyPx7xKdmfZVDiEVRmbsYXXD63bbKXcsVaHbQpO6yfWsCw+G2uDkvJZCwQRKvFtRzxm WhrBMUgtAauWbJWBIilfH5JV5cD3Ty+1vH2dbXU20jDwkvHeUXGXC9+4p5V8Jt78nqIN 3AV7NtSKn5RcMGeIgyE9WqhezaoKiRx839qc2Jh28ynlLGsaxbFX2EGWINP/s5Fc9cez RHEw== X-Gm-Message-State: AOAM531UozlqZm73NL4ilLuCZI+RhYslqUHS7XvA/Mbe5vCqgDgIYGc+ yMPTkWEwe8Ia9fq0VJjyxJbOBIAQWKpT3pjqvjbXJg== X-Google-Smtp-Source: ABdhPJxw9VnfnHe9u50el4lnxVAR9qUrlhodBzmSVS92D4DmQlKkuRP7Li6Zcj7Slw2kIxX2GwblXLsXIsFv3YBquzU= X-Received: by 2002:aa7:8246:0:b0:44b:4870:1b09 with SMTP id e6-20020aa78246000000b0044b48701b09mr58421337pfn.82.1636093537523; Thu, 04 Nov 2021 23:25:37 -0700 (PDT) MIME-Version: 1.0 References: <20211103062520.1445832-1-reijiw@google.com> <20211103062520.1445832-3-reijiw@google.com> In-Reply-To: From: Reiji Watanabe Date: Thu, 4 Nov 2021 23:25:21 -0700 Message-ID: Subject: Re: [RFC PATCH v2 02/28] KVM: arm64: Save ID registers' sanitized value per vCPU To: Oliver Upton Cc: Marc Zyngier , kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, James Morse , Alexandru Elisei , Suzuki K Poulose , Paolo Bonzini , Will Deacon , Andrew Jones , Peng Liang , Peter Shier , Ricardo Koller , Jing Zhang , Raghavendra Rao Anata X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20211104_232538_678135_1F0B373F X-CRM114-Status: GOOD ( 21.24 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Nov 4, 2021 at 2:39 PM Reiji Watanabe wrote: > > Hi Oliver, > > On Thu, Nov 4, 2021 at 9:14 AM Oliver Upton wrote: > > > > Hi Reiji, > > > > On Tue, Nov 02, 2021 at 11:24:54PM -0700, Reiji Watanabe wrote: > > > Extend sys_regs[] of kvm_cpu_context for ID registers and save ID > > > registers' sanitized value in the array for the vCPU at the first > > > vCPU reset. Use the saved ones when ID registers are read by > > > userspace (via KVM_GET_ONE_REG) or the guest. > > > > Based on my understanding of the series, it appears that we require the > > CPU identity to be the same amongst all vCPUs in a VM. Is there any > > value in keeping a single copy in kvm_arch? > > Yes, that's a good point. > It reminded me that the idea bothered me after we discussed a similar > case about your counter offset patches, but I didn't seriously > consider that. > > Thank you for bringing this up. > I will look into keeping it per VM in kvm_arch. I just remembered that I made the prototype that kept ID registers per VM as the option B (, which introduced per VM ID register configuration API though...). Anyway, I've noticed that requiring the consistency of ID registers amongst vCPUs in a VM affects KVM_ARM_VCPU_INIT API, with which userspace can currently configure different features for each vCPUs. I'm not sure if any existing userspace program practically does that though. Now, I think I should rather remove that consistency requirement... (at least for features that can be configured by KVM_ARM_VCPU_INIT) Thanks, Reiji _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel