Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp3605655pxy; Tue, 4 May 2021 06:10:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJygltS1HEYLBlaUaCw67D3uD8cWG1jOQdKv+Kwat1JSXGBhSf1JMxtAksLaWXRFrdO+4x2y X-Received: by 2002:a50:cd57:: with SMTP id d23mr9716985edj.5.1620133849983; Tue, 04 May 2021 06:10:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620133849; cv=none; d=google.com; s=arc-20160816; b=GJ5sypmczOFClzcvUBGW8Bgh4t/QG/wCh73z1Rejk7YpnQqwwU3s72okDzkOMXcAUQ N/MsiBRou7VL9NqKGKHzM5kHxXepCWeK5r3XR7DJ1M566NBXgHisx1QRbBJoVnPlH1XA X4J0pj3E3jec3kaiHgzEHjLFHHq3aesReVXsdrN2NACsIez75GmDZX5ClNTJ1QCCT72/ pnypSOTEuGORiaq02kASEy6KhxxvPGkDCSj8Vs+GQ19JhilNsCX2BdsA8rvniLlrbuSm nBqOlN4z4A1OwKeXonWz60iNUETHqdL+G8WAhzpV6ppVmSO0hzPFJXE0AFbsn5AvQVKL MxOg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:dkim-signature; bh=I+a3Gqq/AQH86AQgX5MsIHGOIG8nweku9Ika1zopWOs=; b=XPj/T1BBWDedIbq9mOhwpl2hbQ5lv12qovfyK7sFQLvY8bBUaify0WcGVgLYfF78cK 1aVpf6onWxpH3pECVo9fPVYHgFJCrrZZyeIDgt58WsnxyjPcaMwyLOG/j03NayGZn64N 1mKqe2+GkkKl1Fmk3MxxgPBHGgiZCgN8GClf5bhaFx+F4ncSUVB8LnSklkVGXPKZZhf0 j2Bs7lsMaEHIBsZHFkMkdH6fzHuyQrq8skBbKPXum+EOe+8tqSfpnLOuppv49SstU8dk sOo6/q7Pg5zHr81yJyuwnjYEzX7W6YstneDkskmJgIk8kCpdAKDPBVlo/II3Rer4m5sZ fWaA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=OrG7CH+d; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n24si10756552eds.571.2021.05.04.06.10.23; Tue, 04 May 2021 06:10:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=OrG7CH+d; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230448AbhEDNKD (ORCPT + 99 others); Tue, 4 May 2021 09:10:03 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:24270 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230410AbhEDNKC (ORCPT ); Tue, 4 May 2021 09:10:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1620133747; 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=I+a3Gqq/AQH86AQgX5MsIHGOIG8nweku9Ika1zopWOs=; b=OrG7CH+dmKwc0rUWbsSyQE7YIRE0F/5PFJaLBOPNH5Z2pG8jUaTfcSqdBZT96ognY1tHoB jhaMzv84G/lbK3ws3khdEujkoV42CDNjso0GTwWsEXkTJ7GEBRJBE1J7qAdiI8632ybV0p 7Hrl7l5vpMeXRF2BHmrO+lC9arQYPDM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-433-sAMffVlyOI2oanb_IGH7cQ-1; Tue, 04 May 2021 09:09:03 -0400 X-MC-Unique: sAMffVlyOI2oanb_IGH7cQ-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 4102964157; Tue, 4 May 2021 13:09:01 +0000 (UTC) Received: from gondolin.fritz.box (ovpn-113-126.ams2.redhat.com [10.36.113.126]) by smtp.corp.redhat.com (Postfix) with ESMTP id 37B075D72F; Tue, 4 May 2021 13:08:53 +0000 (UTC) Date: Tue, 4 May 2021 15:08:51 +0200 From: Cornelia Huck To: Christoph Hellwig Cc: Greg Kroah-Hartman , qemu-devel@nongnu.org, Daniel Vetter , kvm@vger.kernel.org, David Airlie , Michael Ellerman , Greg Kurz , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Alex Williamson , Paul Mackerras , Jason Gunthorpe , linux-api@vger.kernel.org, qemu-ppc@nongnu.org, linuxppc-dev@lists.ozlabs.org Subject: Re: remove the nvlink2 pci_vfio subdriver v2 Message-ID: <20210504150851.54e278f8.cohuck@redhat.com> In-Reply-To: <20210504130039.GA7711@lst.de> References: <20210326061311.1497642-1-hch@lst.de> <20210504142236.76994047@bahia.lan> <20210504130039.GA7711@lst.de> Organization: Red Hat GmbH MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 4 May 2021 15:00:39 +0200 Christoph Hellwig wrote: > On Tue, May 04, 2021 at 02:59:07PM +0200, Greg Kroah-Hartman wrote: > > > Hi Christoph, > > > > > > FYI, these uapi changes break build of QEMU. > > > > What uapi changes? > > > > What exactly breaks? > > > > Why does QEMU require kernel driver stuff? > > Looks like it pull in the uapi struct definitions unconditionally > instead of having a local copy. We could fix that by just putting > them back, but to me this seems like a rather broken configuration > in qemu when it pulls in headers from the running/installed kernel > without any feature checks before using them. > It is not pulling them from the installed kernel, but from a development version to get new definitions. Removing things in the kernel requires workarounds in QEMU until it can remove those things as well. It is not a dumb update...