Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp5101295imb; Thu, 7 Mar 2019 07:48:05 -0800 (PST) X-Google-Smtp-Source: APXvYqwQixyCSe+26IYfdyno12aJShIMOlYE3SyDUfJF2B/rOSwy/1EVg7jM4bduKEqnxwcmraAD X-Received: by 2002:a62:4e8a:: with SMTP id c132mr13252043pfb.24.1551973684987; Thu, 07 Mar 2019 07:48:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551973684; cv=none; d=google.com; s=arc-20160816; b=aKzVYjZrnC/pHa/ljhzSMVqF4Wqr6RRkinAKOTqklwJkDjknpAI76A+be/MxE52fTW Tlm4pwONy/koXIGiHSS2BEE4ItaAo6SpYLjK3D4hpOErTiulqViSZrNwrWkQY54y36Af KMI57afMqFkHQ8XIbppeaNoZWm9lpHnmheYVaGJL6tCQjY07zIsMuYpKZBnBYp9m8gC7 hxsEDVmH4O5xFYr0Ra9CBQimms71oq0s68PVl6LMm1ecqM2z3olf7/mBHdUVzydLOGAA 7DQpZFOc5lX5TvbckLtpqhRHD7efzJi27PwV4jq4lowBtSXT5Y0aVE623G1paHskZ/bI vLtw== 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-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=BhTxD3ySC1uQNcQaurRgNi8lE2OWakmfxk2tvcIPUn4=; b=bpM93ncARiN2A0jBfQ4dUd8tKvB4h6w3N37pxAiFL6NWaKuqV54vXxoV8NspxNR9PM sumBODNMYHRxPWgbJhUKqA2xv99vrEqzmPSxjxCp48oNUzxueVE/QiHh9iCAu7GMQ8hv SssSkJD40fEcBzXLM7XtK8oKVpYeahPV9xYoFw2d1ITyCdleD5NOooKgdhzfjGbDVb2J i4kPLx+ZtCGw/Dd8YMkyrQoursEvXo45cXKQ/f6x4kCD5wXOPFJ7tHBFD0TS/cEajQWR MaWkSU8l7ON0DwnKDTis0FrQUt9wgNDB3bfzp9K6YytRLwRMgmcwOmZsGzCv9EBa2RxQ pGJA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 186si4600200pfe.262.2019.03.07.07.47.48; Thu, 07 Mar 2019 07:48:04 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726412AbfCGPr1 (ORCPT + 99 others); Thu, 7 Mar 2019 10:47:27 -0500 Received: from mail-qk1-f194.google.com ([209.85.222.194]:39148 "EHLO mail-qk1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726186AbfCGPr0 (ORCPT ); Thu, 7 Mar 2019 10:47:26 -0500 Received: by mail-qk1-f194.google.com with SMTP id x6so9285350qki.6 for ; Thu, 07 Mar 2019 07:47:26 -0800 (PST) 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:in-reply-to; bh=BhTxD3ySC1uQNcQaurRgNi8lE2OWakmfxk2tvcIPUn4=; b=th6erMheCIAZzyC/spHeuzkgRa7ceHNK9SK61G8jGdtATsuY0yuPRvC0UevFw+NpD1 Oexr8I4g9kWu7f6jLytOZ2ii+gM8Tt1i3MQ/0h87YKOR6r58DhKHLhmI5/qnFJJxKoSp oBjbTEFNRub2SAshJUWL7BBz7ROKHhS2SCHipPkHHf9coHe7fayXXNkJNrRTizEnakm1 yMNcYgijpfR8njdNXVQc14NUZI5JV6cWJ0oGqr5MWy8J7sPQP8OUIZe7R9F1t3IjEr86 sOgpu/5aNfl6/7OE1m1vmT1m+JwYnAq/TxKHu5A6mxRLxYnEHqurYY/4aOimi6UHDAVe P+zg== X-Gm-Message-State: APjAAAVMch4Fsa0SebKX1G3BzBXlD0zT8S5xD8dBPW9Nk39qmJUOA572 zMvrQR9xPbrBWfw++9dsmXiWMw== X-Received: by 2002:a05:620a:148a:: with SMTP id w10mr10023352qkj.172.1551973646133; Thu, 07 Mar 2019 07:47:26 -0800 (PST) Received: from redhat.com (pool-173-76-246-42.bstnma.fios.verizon.net. [173.76.246.42]) by smtp.gmail.com with ESMTPSA id s49sm3115748qtk.7.2019.03.07.07.47.23 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 07 Mar 2019 07:47:25 -0800 (PST) Date: Thu, 7 Mar 2019 10:47:22 -0500 From: "Michael S. Tsirkin" To: Jason Wang Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, peterx@redhat.com, linux-mm@kvack.org, aarcange@redhat.com Subject: Re: [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address Message-ID: <20190307103503-mutt-send-email-mst@kernel.org> References: <1551856692-3384-1-git-send-email-jasowang@redhat.com> <1551856692-3384-6-git-send-email-jasowang@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1551856692-3384-6-git-send-email-jasowang@redhat.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 06, 2019 at 02:18:12AM -0500, Jason Wang wrote: > +static const struct mmu_notifier_ops vhost_mmu_notifier_ops = { > + .invalidate_range = vhost_invalidate_range, > +}; > + > void vhost_dev_init(struct vhost_dev *dev, > struct vhost_virtqueue **vqs, int nvqs, int iov_limit) > { I also wonder here: when page is write protected then it does not look like .invalidate_range is invoked. E.g. mm/ksm.c calls mmu_notifier_invalidate_range_start and mmu_notifier_invalidate_range_end but not mmu_notifier_invalidate_range. Similarly, rmap in page_mkclean_one will not call mmu_notifier_invalidate_range. If I'm right vhost won't get notified when page is write-protected since you didn't install start/end notifiers. Note that end notifier can be called with page locked, so it's not as straight-forward as just adding a call. Writing into a write-protected page isn't a good idea. Note that documentation says: it is fine to delay the mmu_notifier_invalidate_range call to mmu_notifier_invalidate_range_end() outside the page table lock. implying it's called just later. -- MST