Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp1105247pxa; Wed, 5 Aug 2020 22:53:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzUmCF06qm37Vaxc2UUv9NDKBG2qZYt8w7eGHVWuUd+FvQlQLvvcvUtQZjA2Jp9bwfucArf X-Received: by 2002:a17:906:d102:: with SMTP id b2mr2564606ejz.465.1596693229177; Wed, 05 Aug 2020 22:53:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596693229; cv=none; d=google.com; s=arc-20160816; b=faEKJTFs9I+6v/PRaYzsv/jTCL4Jfmp0+Zl87eoHOLBRPrO3n5T2eM9wD5Svts08vc 7rlRDvXJmJxIAr/AuANqAYf1A+O/5BXINRYLgnOCiYCDi0h8f8EXx3XnHLmQc/JRrOMq 8JJFtLbx87N5bCT9ZXSSBVBoznOQPQOKHt1vUQEgmFc3Gxe77YPjmZFogn8oVmv8TP03 HT8xmY/IVgxsd3BGPGGaZSnjCFPK3bpagLMKQ2BSvWJ4o3o22nF/etTxbHwLmhv8+S63 PnFjAIcdWCF3yW/2bLqf8o984d9SYgFZq4tr9M/itZgwZqYaePAptE4nxP2IA9iZ7aF/ /ReQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=g0AG8W/Xs0dRN98tWfYfSB2XGEBT9FxGN8gSm2qY254=; b=MaoBEeNDffAuT5XifwsP8MPTqvA69+deHwZS32AgslBSQujRkq31mAeuBhCzdqfCEB 3Uu4NfWo77E5I/rZVGXKYbbT8q9PKeLxx7wL0RfCmem7yR8Oc76EeJKJOd3lPHl2evJl r9wEnf/maAfuQkOMrtVnRzj61V0zpMq9lFhYAc81HHzBcjex41dzClEUmTbOJPdAYmDl 7B5de3BC/BdjyhC1f+XcvZz6FOwvRLKC0UOcPRpI0gKu9kBuX2SsHPbPEN88eZ1GdT79 FC9xSbeUwKwgv8bkyLNucdrqIk27yoQQyxuHDWFwkIQbZMvUCts1ey6BvUHpDjV6xos7 c1Yg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=fJSZquCO; 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 r20si2731080ejz.158.2020.08.05.22.53.26; Wed, 05 Aug 2020 22:53: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=fJSZquCO; 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 S1726987AbgHFFxR (ORCPT + 99 others); Thu, 6 Aug 2020 01:53:17 -0400 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:52313 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726051AbgHFFxQ (ORCPT ); Thu, 6 Aug 2020 01:53:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1596693194; 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=g0AG8W/Xs0dRN98tWfYfSB2XGEBT9FxGN8gSm2qY254=; b=fJSZquCOxOFKzkNh2x7kOF0rJB5tTrsnLAsR0MS33EU49omBMjxD0wq0lQ1wFGk+CRAre+ wqZIpKTleMxHPQnkOe0n1xMklAEfFvCJHhsIjVq3rB6tuSQhtzd/Uq7hYpVk1w4YXSTzAj oM37i24buqvz+o5xUol1988Q+lU5H8g= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-350-PJDzE5tHOQavGq8vHvonSg-1; Thu, 06 Aug 2020 01:53:13 -0400 X-MC-Unique: PJDzE5tHOQavGq8vHvonSg-1 Received: by mail-wr1-f69.google.com with SMTP id s23so14142349wrb.12 for ; Wed, 05 Aug 2020 22:53:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=g0AG8W/Xs0dRN98tWfYfSB2XGEBT9FxGN8gSm2qY254=; b=MhzLFKh3Np/L2P5mw8M5TX2niEJUCiJGYDGu+nix6CxeudQGR13E/KHp7EDOPg50aQ /zZMu5cMG8z+iVkfAo+ux1+hUGnRUkjjwfXjlWDjU2q0w4Y6PsiAEFz3nehlIJbLlSI0 swRcvytwR9Q70dulhm33s0e/mUMvXdWMkWVoFVIbhRyb+l8XSyRG7yAULJO4r/WuDvoH LE2Z+o0BZxCacYGxTdwLMCxMwnk1jF63Wz0VHdWV1c46FXvDCZCycuT3mheW3T9tvGlk +JGDoan+R4w5B0bAgD8gqoR81aLvc5cOE7AkDAtnvuPAVP5E2IJkubTwsBnfMyPa/tTA UlKQ== X-Gm-Message-State: AOAM532lG2oPzIP0t0gj6gzc8BmP++YJ6rD352227XLjfYDjJgdeiVkH vuK454ny5O3qPmNabj2vRozK8/j09AMNAhtZa9VqTC8nj8G14D9l0ZSpaxehqqouTCKrMxVDd8K 4XG9vriHTQCqsuwo0f5ki7V3c X-Received: by 2002:a7b:c7c6:: with SMTP id z6mr6718362wmk.17.1596693191726; Wed, 05 Aug 2020 22:53:11 -0700 (PDT) X-Received: by 2002:a7b:c7c6:: with SMTP id z6mr6718355wmk.17.1596693191496; Wed, 05 Aug 2020 22:53:11 -0700 (PDT) Received: from redhat.com (bzq-79-177-102-128.red.bezeqint.net. [79.177.102.128]) by smtp.gmail.com with ESMTPSA id f15sm4931149wmj.39.2020.08.05.22.53.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 05 Aug 2020 22:53:10 -0700 (PDT) Date: Thu, 6 Aug 2020 01:53:08 -0400 From: "Michael S. Tsirkin" To: Jason Wang Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org Subject: Re: [PATCH v2 19/24] vdpa: make sure set_features in invoked for legacy Message-ID: <20200806015112-mutt-send-email-mst@kernel.org> References: <20200803205814.540410-1-mst@redhat.com> <20200803205814.540410-20-mst@redhat.com> <9e47d227-f220-4651-dcb9-7a11f059a715@redhat.com> <20200805073929-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 06, 2020 at 11:23:05AM +0800, Jason Wang wrote: > > On 2020/8/5 下午7:40, Michael S. Tsirkin wrote: > > On Wed, Aug 05, 2020 at 02:14:07PM +0800, Jason Wang wrote: > > > On 2020/8/4 上午5:00, Michael S. Tsirkin wrote: > > > > Some legacy guests just assume features are 0 after reset. > > > > We detect that config space is accessed before features are > > > > set and set features to 0 automatically. > > > > Note: some legacy guests might not even access config space, if this is > > > > reported in the field we might need to catch a kick to handle these. > > > I wonder whether it's easier to just support modern device? > > > > > > Thanks > > Well hardware vendors are I think interested in supporting legacy > > guests. Limiting vdpa to modern only would make it uncompetitive. > > > My understanding is that, IOMMU_PLATFORM is mandatory for hardware vDPA to > work. Hmm I don't really see why. Assume host maps guest memory properly, VM does not have an IOMMU, legacy guest can just work. Care explaining what's wrong with this picture? > So it can only work for modern device ... > > Thanks > > > > > > > >