Received: by 2002:a17:505:a0c:b0:1be9:327d:8ee3 with SMTP id cg12csp4835140njb; Thu, 12 Dec 2024 06:46:37 -0800 (PST) X-Forwarded-Encrypted: i=2; AJvYcCUMdqCcpdXWvEJSxXO3T9i+qMmOjNlh97Y9HD4xovliBYYqzpUWiOGuwmvkA3SILo3ib8X5WTEIScw8XQ==@linaro.org X-Google-Smtp-Source: AGHT+IHWiLTOjH2gHzlqFa7S/woUzV7RIxLlFrdsOdYbeHRlAWmu/zLkxRmyR8PEkDhgLnoMA8pZ X-Received: by 2002:a05:620a:2855:b0:7b6:d089:2757 with SMTP id af79cd13be357-7b6f899fb58mr110056085a.35.1734014797597; Thu, 12 Dec 2024 06:46:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1734014797; cv=none; d=google.com; s=arc-20240605; b=YIXrGLoMFqsVNRflZSOdKmxCyRehZZGV87b0085Z/vNuDepq8t+UpCJ7ord2NRbw26 Bnud7HPqh9OwILnHALTejglCL9AGRbV3zsfhks7qcPD1J9+pkKKfZdcu+SCCD9JrVTk6 bcI2+EeKlVM8IypBxwEXWq/uUHqCmw4Wotxp43HF8cD5etHC//7p6KutnfGgfoJ+Q1Fu FQZVckN4WslSQU3zWTvILccYOhtBm/cIavoAzdiz87lYb3xjvyk0SR0EeMaodnzEbcbd PrsnoUYeFwdBenAxRcieyUpXdJI25dNXgXjDxtKYjFtEiI2p3K/4vGgl4Uk1ie4c8F/a RH0g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=content-transfer-encoding:mime-version:message-id:date:user-agent :references:organization:in-reply-to:subject:cc:to:from :dkim-signature; bh=rj3/bj3qiByyq03DEtIoenWqlg7LpEjsdDBIJ///74A=; fh=OxDr5SxJALnlPk9Yxffk5L0YyWGKjlEnGSRnzrED6Nc=; b=eEoCu7ajRxLSP3MVbYhRwqlfmI2Oy01MD2sa21T7f9xZRRiFgLIzKRc5nqIaxZwHfq 8t6eCM8YkwlYtT+iwh/KT+JuHDPcdmHd8nk3dn5lXX7/mO4ZeL4escJITtG3qUfchOAL iBAfANgBAHDFVxBHOBVL27B5z1rS/bCVeZm+AXXdHzY0Ve88uJMllNlEUrNF0KWJj6I9 SMtx4aOvW+uRaMlguLTgHZaj/0eSil+PwgOETFQHA443HyJBnk+3p/IF/g5OiF28QLgh c30263L4+wGk0m/EQtHEQqrXtPEwNLH4nmr9aeSyPLk80K/G/bse5b/YslBTVP7+kkdn 5/Dw==; dara=google.com ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=d+nCCiaV; spf=pass (google.com: domain of cohuck@redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=cohuck@redhat.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com. [170.10.133.124]) by mx.google.com with ESMTPS id af79cd13be357-7b6e4d95116si604022185a.298.2024.12.12.06.46.37 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 12 Dec 2024 06:46:37 -0800 (PST) Received-SPF: pass (google.com: domain of cohuck@redhat.com designates 170.10.133.124 as permitted sender) client-ip=170.10.133.124; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=d+nCCiaV; spf=pass (google.com: domain of cohuck@redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=cohuck@redhat.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1734014797; 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=rj3/bj3qiByyq03DEtIoenWqlg7LpEjsdDBIJ///74A=; b=d+nCCiaVkcYCfEFYaC40eVp0ikzUNFexxPemiuGbq7y4HyQLdSWP6sHiPkYXZKJ73hZZ3y lkzXbIoZRMs2p+m69yBz2h3kcaahpex1HQqy6lRYpBHRlBqzcjvgD6pCeaUO3ZqTkhGhJr gxQR5zZ2MII3xmOs5rJEd4mOcYORckc= Received: from mx-prod-mc-04.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-438-PvAlLYKeM9acSycBW-uWow-1; Thu, 12 Dec 2024 09:46:34 -0500 X-MC-Unique: PvAlLYKeM9acSycBW-uWow-1 X-Mimecast-MFC-AGG-ID: PvAlLYKeM9acSycBW-uWow Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-04.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 2EB8919560B2; Thu, 12 Dec 2024 14:46:29 +0000 (UTC) Received: from localhost (dhcp-192-244.str.redhat.com [10.33.192.244]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 06CDE30044C1; Thu, 12 Dec 2024 14:46:25 +0000 (UTC) From: Cornelia Huck To: eric.auger@redhat.com, =?utf-8?Q?Daniel_P=2E_Berrang=C3=A9?= Cc: eric.auger.pro@gmail.com, qemu-devel@nongnu.org, qemu-arm@nongnu.org, kvmarm@lists.linux.dev, peter.maydell@linaro.org, richard.henderson@linaro.org, alex.bennee@linaro.org, maz@kernel.org, oliver.upton@linux.dev, sebott@redhat.com, shameerali.kolothum.thodi@huawei.com, armbru@redhat.com, abologna@redhat.com, jdenemar@redhat.com, shahuang@redhat.com, mark.rutland@arm.com, philmd@linaro.org, pbonzini@redhat.com Subject: Re: [PATCH RFCv2 00/20] kvm/arm: Introduce a customizable aarch64 KVM host model In-Reply-To: <1fea79e4-7a31-4592-8495-7b18cd82d02b@redhat.com> Organization: "Red Hat GmbH, Sitz: Werner-von-Siemens-Ring 12, D-85630 Grasbrunn, Handelsregister: Amtsgericht =?utf-8?Q?M=C3=BCnchen=2C?= HRB 153243, =?utf-8?Q?Gesch=C3=A4ftsf=C3=BChrer=3A?= Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross" References: <20241206112213.88394-1-cohuck@redhat.com> <8734it1bv6.fsf@redhat.com> <1fea79e4-7a31-4592-8495-7b18cd82d02b@redhat.com> User-Agent: Notmuch/0.38.3 (https://notmuchmail.org) Date: Thu, 12 Dec 2024 15:46:23 +0100 Message-ID: <87bjxhc62o.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4 X-TUID: 4Cc0XIKhaftT On Thu, Dec 12 2024, Eric Auger wrote: > On 12/12/24 10:36, Cornelia Huck wrote: >> On Thu, Dec 12 2024, Daniel P. Berrang=C3=A9 wrote: >> >>> On Thu, Dec 12, 2024 at 09:12:33AM +0100, Eric Auger wrote: >>>> Connie, >>>> >>>> On 12/6/24 12:21, Cornelia Huck wrote: >>>>> A respin/update on the aarch64 KVM cpu models. Also available at >>>>> gitlab.com/cohuck/qemu arm-cpu-model-rfcv2 >>> snip >>> >>>> From a named model point of view, since I do not see much traction >>>> upstream besides Red Hat use cases, targetting ARM spec revision >>>> baselines may be overkill. Personally I would try to focus on above >>>> models: AltraMax, AmpereOne, Grace, ... Or maybe the ARM cores they may >>>> be derived from. >>> If we target modelling of vendor named CPU models, then beware that >>> we're opening the door to an very large set (potentially unbounded) >>> of named CPU models over time. If we target ARM spec baselines then >>> the set of named CPU models is fairly modest and grows slowly. >>> >>> Including ARM spec baselines will probably reduce the demand for >>> adding vendor specific named models, though I expect we'll still >>> end up wanting some, or possibly even many. >>> >>> Having some common baseline models is likely useful for mgmt >>> applications in other ways though. >>> >>> Consider you mgmt app wants to set a CPU model that's common across >>> heterogeneous hardware. They don't neccessarily want/need to be >>> able to live migrate between heterogeneous CPUs, but for simplicity >>> of configuration desire to set a single named CPU across all guests, >>> irrespective of what host hey are launched on. The ARM spec baseline >>> named models would give you that config simplicity. >> If we use architecture extensions (i.e. Armv8.x/9.x) as baseline, I'm >> seeing some drawbacks: >> - a lot of work before we can address some specific use cases >> - old models can get new optional features >> - a specific cpu might have a huge set of optional features on top of >> the baseline model >> >> Using a reference core such as Neoverse-V2 probably makes more sense >> (easier to get started, less feature diff?) It would still make a good >> starting point for a simple config. >> > Actually from a dev point of view I am not sure it changes much to have > either ARM spec rev baseline or CPU ref core named model. > > One remark is that if you look at > https://developer.arm.com/documentation/109697/2024_09?lang=3Den > you will see there are quite a lot of spec revisions and quite a few of > them are actually meaningful in the light of currently avaiable and > relevant HW we want to address. What I would like to avoid is to be > obliged to look at all of them in a generic manner while we just want to > address few cpu ref models. Yes, exactly. > > Also starting from the ARM spec rev baseline the end-user may need to > add more feature opt-ins to be close to a specific cpu model. So I > foresee extra complexity for the end-user. For ref cores, it's easier to pick the ones that actually matter for a specific use case, for arch exts I don't think we can avoid implementing those we don't really care about. And yes, from the sample of cpus I've looked at they seem to be much closer to a ref core than to an arch ext.