From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0408922A1E2 for ; Mon, 7 Apr 2025 08:34:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1744014879; cv=none; b=fAcwqhDvm9K8RTH6PLdH6pOk8IkhuWTXFn7duT/+xz0v4341bCR0bnZMbWFC0AW1GqCY4AiWwzL3hQyKanQQjuE1bT68EmPiT6EnDh6pzCnUOVRMKDZUFBuRz5lBnzC3CX+H7TxwtOk9lFUMcWaEn+wj98EKOg3nz2mAuWkI/z4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1744014879; c=relaxed/simple; bh=sLck2J+6PcjmSINGrDUpZvijf9T2VzrBWCePSK/Qvj8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=DwxixZVEL89lQFFLcQtp+Ms52CPI4ZjaybpgpewPwyaRFlCT0vjNFn/Ga7vDXJ8To9RmKeb5bDVy2bw1lIeNLyyPNlZ95NVpF3d+nGsFOpN/JWGkHRgQR6GTD/q0sxJ4knELFNm9B2Dn9Tdzwi9fN7gtAt48SEasK6lg30fbMjM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=QpdX44Lg; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="QpdX44Lg" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1744014876; 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: in-reply-to:in-reply-to:references:references; bh=RyTmsi9BhA0X2tfDIhwHRBuV/xgf5KDyDiyovwov3BE=; b=QpdX44LgbzIPJTqRMIvF5PZ7fFBPXIgzvk6qPV4RxuarKW7iXOq4pvWTSW/Zej43/XdUdF iNixCp2vkg5yQHU6fkczUuFRTPEqUxtcgcUyqhCIsd+iMKFv4NM+bESdAVyCUJ84U+ha/H PspcaSKa/V/UJyKByhlhRLO3/94cYOs= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-142-6rZSWLW0M82RWtiv39pD9g-1; Mon, 07 Apr 2025 04:34:35 -0400 X-MC-Unique: 6rZSWLW0M82RWtiv39pD9g-1 X-Mimecast-MFC-AGG-ID: 6rZSWLW0M82RWtiv39pD9g_1744014874 Received: by mail-wm1-f69.google.com with SMTP id 5b1f17b1804b1-43eed325461so6101745e9.3 for ; Mon, 07 Apr 2025 01:34:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744014874; x=1744619674; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=RyTmsi9BhA0X2tfDIhwHRBuV/xgf5KDyDiyovwov3BE=; b=CV0NbRRfiddzVet50PxKrXmOub/S1ureSqc4mv+fYlfHXQ7D1Cg5j0zsSGRYIX1OYB DJlXfbmoQ/RiweEyMCgw1MOlEpibTKDYe7GJ8h44STJBHsfN6sLecdYaKH7l5M9S9R8U wfndroOrIsBDQQ+AkV/USsVUOEaqrXo7JmlZzHNQOQF3GnZEJ1knNSfsqZu6UJYASef2 YQUkwbT+AzfS1p1g+xei/NF/6URrNN3432BLdq+Di6rThyklyRrkkqc/aiocK/ZSFFJl NSE4N+zNaGsedIgl9YaF4avf13GAuoStyktrAbF6NzH53Vo8uTp2HgYsrXrDGFAyHZUt vipw== X-Forwarded-Encrypted: i=1; AJvYcCX4UaIf/HeAjeTXb/q7e1eaSOOYFu5tZdat7sSCeHp8jyHa039GO7jnNocIJaW8S6RLh7k15Yu/g0oO@vger.kernel.org X-Gm-Message-State: AOJu0Yynr5E5eFiBCCOBsBn9I1GLBQFnNMzeyKctz6HyLm0OZ+Xv/1IB L2dBSJSDAw7n1dfWmHB2zoUVDGnZjzp4B337u/HGVyuL4okeC70bImqmiVMNitnTlnqaYI5HxCW CfzFpCewywiCnGi+zY7t2bHGCHykvzJPGPDOzjpwWdnk4hu2Y7QUfyzVODE8= X-Gm-Gg: ASbGncv5ZPqv079hogXM/nLkDaGmw2848mxf0PHZl/FoBBdWTxd6CwG7k3njMureWpU AVEpWjkjSjomrVxgz+NBNduiwkt1YcGM7+8dTFtXdUQjqNRdm4lyAMG+PVivVjv9CN3dCH0bCY1 rXhYd3j+AgJUQwDRNEEo+k3LnFu+X0dV4xwnH5R4rZvbvC7eVvvLjkN78zf2ZFGdm7emx7JMbiu VCX1qnbDY0lUUyGijIkSWjUC7Q4NMYBqBl6HCXh2chhEoe2tOFcXzG9MB0MtU2mgB3hmVty/6an p0dNrXnMuQ== X-Received: by 2002:a05:600c:1e13:b0:43d:abd:ad0e with SMTP id 5b1f17b1804b1-43ecf8e72d6mr114694725e9.18.1744014874162; Mon, 07 Apr 2025 01:34:34 -0700 (PDT) X-Google-Smtp-Source: AGHT+IH+83STYsHXI3xn6x5xnem+/h77ehJWni3dU6P1EgXI8aWI6y/h2doOJ2sCUgok7+DS4MLeKg== X-Received: by 2002:a05:600c:1e13:b0:43d:abd:ad0e with SMTP id 5b1f17b1804b1-43ecf8e72d6mr114694305e9.18.1744014873776; Mon, 07 Apr 2025 01:34:33 -0700 (PDT) Received: from redhat.com ([2a0d:6fc0:1517:1000:ea83:8e5f:3302:3575]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-43ec1630f21sm126976935e9.8.2025.04.07.01.34.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 07 Apr 2025 01:34:33 -0700 (PDT) Date: Mon, 7 Apr 2025 04:34:29 -0400 From: "Michael S. Tsirkin" To: David Hildenbrand Cc: Halil Pasic , linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, virtualization@lists.linux.dev, kvm@vger.kernel.org, Chandra Merla , Stable@vger.kernel.org, Cornelia Huck , Thomas Huth , Eric Farman , Heiko Carstens , Vasily Gorbik , Alexander Gordeev , Christian Borntraeger , Sven Schnelle , Wei Wang Subject: Re: [PATCH v1] s390/virtio_ccw: don't allocate/assign airqs for non-existing queues Message-ID: <20250407042058-mutt-send-email-mst@kernel.org> References: <20250404063619.0fa60a41.pasic@linux.ibm.com> <4a33daa3-7415-411e-a491-07635e3cfdc4@redhat.com> <20250404153620.04d2df05.pasic@linux.ibm.com> <20250404160025.3ab56f60.pasic@linux.ibm.com> <6f548b8b-8c6e-4221-a5d5-8e7a9013f9c3@redhat.com> <20250404173910.6581706a.pasic@linux.ibm.com> <20250407034901-mutt-send-email-mst@kernel.org> <2b187710-329d-4d36-b2e7-158709ea60d6@redhat.com> Precedence: bulk X-Mailing-List: linux-s390@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2b187710-329d-4d36-b2e7-158709ea60d6@redhat.com> On Mon, Apr 07, 2025 at 10:17:10AM +0200, David Hildenbrand wrote: > On 07.04.25 09:52, Michael S. Tsirkin wrote: > > On Fri, Apr 04, 2025 at 05:39:10PM +0200, Halil Pasic wrote: > > > > > > > > Not perfect, but AFAIKS, not horrible. > > > > > > It is like it is. QEMU does queue exist if the corresponding feature > > > is offered by the device, and that is what we have to live with. > > > > I don't think we can live with this properly though. > > It means a guest that does not know about some features > > does not know where to find things. > > Please describe a real scenario, I'm missing the point. OK so. Device has VIRTIO_BALLOON_F_FREE_PAGE_HINT and VIRTIO_BALLOON_F_REPORTING Driver only knows about VIRTIO_BALLOON_F_REPORTING so it does not know what does VIRTIO_BALLOON_F_FREE_PAGE_HINT do. How does it know which vq to use for reporting? It will try to use the free page hint one. > Whoever adds new feat_X *must be aware* about all previous features, > otherwise we'd be reusing feature bits and everything falls to pieces. The knowledge is supposed be limited to which feature bit to use. > > > > So now, I am inclined to add linux code to work with current qemu and > > with spec compliant one, and add qemu code to work with current linux > > and spec compliant one. > > > > Document the bug in the spec, maybe, in a non conformance section. > > I'm afraid this results in a lot of churn without really making things > better. > IMHO, documenting things how they actually behave, and maybe moving towards > fixed queue indexes for new features is the low hanging fruit. I worry about how to we ensure that? If old code is messed up people will just keep propagating that. I would like to fix old code so that new code is correct. > > As raised, it's not just qemu+linux, it's *at least* also cloud-hypervisor. > > -- > Cheers, > > David / dhildenb There's a slippery slope here in that people will come to us with buggy devices and ask to change the spec. -- MST