Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp11160909ybi; Thu, 25 Jul 2019 11:03:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqwmq+8ty8PXrqPDopI2d9L60g5nlhATRSmOWAVFsMYEexhLGf9TCYxGdVEWA/urHWo9egJp X-Received: by 2002:a63:58c:: with SMTP id 134mr91262784pgf.106.1564077791634; Thu, 25 Jul 2019 11:03:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564077791; cv=none; d=google.com; s=arc-20160816; b=yL4Om1yXjUWmFa89FkcVdgqMRDwHc2Lpp6J8QzXfwaDmFE7aHM8nHR0zcLVKu1dzZe 4bbX/w2IF2WOSJLnuv93OkKUV3Lm0vqS/loX+TwmauU9GMuEZ1MzyjLPNEpxdHZtmPmU MD+Sp7MAS7Rfxu3rXLhhdlzvyPART/NRLcfQ0PIdNWDRJTBLN8zo9gVf76qrH3pA5mfT maVKKdFWE6vARIppV73s2ekY+N+2XoF9IQBRitMaZ7hPBynOZ6Xbej8tsCkKCMN0F9nX +6Kyp2LSnC3eSIrX9gLNFik1UasmM1aPHoKiyRETEyyJkF24SET8X2O1n6w7KDN2G1Sj BhEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=OqSdYLNp3QEtJFrfzpK5pNge56bxyGG+CtvF4Ygj4Hw=; b=p8aPyYxLEQOO/0cSrdA0pSEdWjmqCvSXRDAht6/dvUpi0IiUEIQEwRUA2eQCJRLxp5 1A8gf7sWe+u88F3gbvwcGhCWCkZGwgj3KtPxTD8l3I2fU+dEceFDTPLEME/Hbw5NTkx2 ABu407J/AfjrLxLGqsIEC/yNmF3MOLx10zd/xnht01kcNeat8Ho7AdVAIlZd05RS4uor pBV0lRkPyxDAQECnTUrjIqPUvSUun4MXStx2L1RNkaaBQmiCAIimcZkhe70jPgUL+7um ielphunceHP8nAMUWFkmJFiyn2eagV1j+pSzLl619AgxH2y0Yj5wKBsomh/yVIeiGXnt 8JaQ== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w5si18259813pfi.264.2019.07.25.11.02.48; Thu, 25 Jul 2019 11:03:11 -0700 (PDT) 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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388569AbfGYO4Q (ORCPT + 99 others); Thu, 25 Jul 2019 10:56:16 -0400 Received: from mga14.intel.com ([192.55.52.115]:44785 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387422AbfGYO4Q (ORCPT ); Thu, 25 Jul 2019 10:56:16 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jul 2019 07:56:15 -0700 X-IronPort-AV: E=Sophos;i="5.64,307,1559545200"; d="scan'208";a="321687109" Received: from ahduyck-desk1.jf.intel.com ([10.7.198.76]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jul 2019 07:56:15 -0700 Message-ID: Subject: Re: [PATCH v2 5/5] virtio-balloon: Add support for providing page hints to host From: Alexander Duyck To: Nitesh Narayan Lal , "Michael S. Tsirkin" , Alexander Duyck Cc: kvm@vger.kernel.org, david@redhat.com, dave.hansen@intel.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, akpm@linux-foundation.org, yang.zhang.wz@gmail.com, pagupta@redhat.com, riel@surriel.com, konrad.wilk@oracle.com, lcapitulino@redhat.com, wei.w.wang@intel.com, aarcange@redhat.com, pbonzini@redhat.com, dan.j.williams@intel.com Date: Thu, 25 Jul 2019 07:56:15 -0700 In-Reply-To: <21cc88cd-3577-e8b4-376f-26c7848f5764@redhat.com> References: <20190724165158.6685.87228.stgit@localhost.localdomain> <20190724170514.6685.17161.stgit@localhost.localdomain> <20190724143902-mutt-send-email-mst@kernel.org> <21cc88cd-3577-e8b4-376f-26c7848f5764@redhat.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2019-07-25 at 10:44 -0400, Nitesh Narayan Lal wrote: > On 7/24/19 3:02 PM, Michael S. Tsirkin wrote: > > On Wed, Jul 24, 2019 at 10:05:14AM -0700, Alexander Duyck wrote: > > > From: Alexander Duyck > > > > > > Add support for the page hinting feature provided by virtio-balloon. > > > Hinting differs from the regular balloon functionality in that is is > > > much less durable than a standard memory balloon. Instead of creating a > > > list of pages that cannot be accessed the pages are only inaccessible > > > while they are being indicated to the virtio interface. Once the > > > interface has acknowledged them they are placed back into their respective > > > free lists and are once again accessible by the guest system. > > > > > > Signed-off-by: Alexander Duyck > > Looking at the design, it seems that hinted pages can immediately be > > reused. I wonder how we can efficiently support this > > with kvm when poisoning is in effect. Of course we can just > > ignore the poison. However it seems cleaner to > > 1. verify page is poisoned with the correct value > > 2. fill the page with the correct value on fault > > > > Requirement 2 requires some kind of madvise that > > will save the poison e.g. in the VMA. > > > > Not a blocker for sure ... > > > > > > > --- > > > drivers/virtio/Kconfig | 1 + > > > drivers/virtio/virtio_balloon.c | 47 +++++++++++++++++++++++++++++++++++ > > > include/uapi/linux/virtio_balloon.h | 1 + > > > 3 files changed, 49 insertions(+) > > > > > > diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig > > > index 078615cf2afc..d45556ae1f81 100644 > > > --- a/drivers/virtio/Kconfig > > > +++ b/drivers/virtio/Kconfig > > > @@ -58,6 +58,7 @@ config VIRTIO_BALLOON > > > tristate "Virtio balloon driver" > > > depends on VIRTIO > > > select MEMORY_BALLOON > > > + select PAGE_HINTING > > > ---help--- > > > This driver supports increasing and decreasing the amount > > > of memory within a KVM guest. > > > diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c > > > index 226fbb995fb0..dee9f8f3ad09 100644 > > > --- a/drivers/virtio/virtio_balloon.c > > > +++ b/drivers/virtio/virtio_balloon.c > > > @@ -19,6 +19,7 @@ > > > #include > > > #include > > > #include > > > +#include > > > > > > /* > > > * Balloon device works in 4K page units. So each page is pointed to by > > > @@ -27,6 +28,7 @@ > > > */ > > > #define VIRTIO_BALLOON_PAGES_PER_PAGE (unsigned)(PAGE_SIZE >> VIRTIO_BALLOON_PFN_SHIFT) > > > #define VIRTIO_BALLOON_ARRAY_PFNS_MAX 256 > > > +#define VIRTIO_BALLOON_ARRAY_HINTS_MAX 32 > > > #define VIRTBALLOON_OOM_NOTIFY_PRIORITY 80 > > > > > > #define VIRTIO_BALLOON_FREE_PAGE_ALLOC_FLAG (__GFP_NORETRY | __GFP_NOWARN | \ > > > @@ -46,6 +48,7 @@ enum virtio_balloon_vq { > > > VIRTIO_BALLOON_VQ_DEFLATE, > > > VIRTIO_BALLOON_VQ_STATS, > > > VIRTIO_BALLOON_VQ_FREE_PAGE, > > > + VIRTIO_BALLOON_VQ_HINTING, > > > VIRTIO_BALLOON_VQ_MAX > > > }; > > > > > > @@ -113,6 +116,10 @@ struct virtio_balloon { > > > > > > /* To register a shrinker to shrink memory upon memory pressure */ > > > struct shrinker shrinker; > > > + > > > + /* Unused page hinting device */ > > > + struct virtqueue *hinting_vq; > > > + struct page_hinting_dev_info ph_dev_info; > > > }; > > > > > > static struct virtio_device_id id_table[] = { > > > @@ -152,6 +159,22 @@ static void tell_host(struct virtio_balloon *vb, struct virtqueue *vq) > > > > > > } > > > > > > +void virtballoon_page_hinting_react(struct page_hinting_dev_info *ph_dev_info, > > > + unsigned int num_hints) > > > +{ > > > + struct virtio_balloon *vb = > > > + container_of(ph_dev_info, struct virtio_balloon, ph_dev_info); > > > + struct virtqueue *vq = vb->hinting_vq; > > > + unsigned int unused; > > > + > > > + /* We should always be able to add these buffers to an empty queue. */ > > > > can be an out of memory condition, and then ... > > Do we need an error check here? > > For situations where this fails we should disable hinting completely, maybe? No. Instead I will just limit the capacity to no more than the vq size. Doing that should allow us to avoid the out of memory issue here if I am understanding things correctly. I'm assuming the allocation being referred to is alloc_indirect_split(), if so then it looks like it can fail and then we just fall back to using the vring.desc directly which will work for my purposes as long as I limit the capacity of the scatterlist to no more than the size of the vring.