Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp4451221ybb; Tue, 14 Apr 2020 07:35:14 -0700 (PDT) X-Google-Smtp-Source: APiQypLAaVSMd5C1+ISlTgisd+AroJMeE/wJr9K53+euI/7c46QQdVHivN0XgMy0m54Q10vMeV42 X-Received: by 2002:a17:906:5e45:: with SMTP id b5mr454981eju.0.1586874914032; Tue, 14 Apr 2020 07:35:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586874914; cv=none; d=google.com; s=arc-20160816; b=lUkT5+nIR94J2tktmmFn7LbXxLlwko3z8z9Da7CuerPVJ/ePLxpVdx+I35dsF1F8tl Nk2Wjpmkk7qR0WBUGd+EVM2MmzJ91vxUQz+YTdqiGJiHvytVpyD/zVT+DYVWu79dYXZi U+gOViZ9qunSTKRafFveIvi+06Ty/qa/lmqYwrTqSJ7RMN61CJ0+2DU9CutAdnqiBtvP qyUra/g04WbpW4qePC77GC15fp7BPzhNd1jkJIsctGZAm6BSRZ2BR+fGP/vQFK4R0crv 8GYRbCKb4pfzU0TWJ/8ZCEdxveACCJ4c2VeliOyfHzEw1+9DtrFyOZDMHA5vQu/K+X9T qKcw== 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 :dkim-signature; bh=DOrTl4YvBq5Mc/4tt5fmz7abkbkAWLtGCwVC/yQsB/U=; b=fyLiIGiaaInnpot1UvrfqjC2dHf3k4oJ73ZGwuUvShk3RtLuwipSCL/qu24drWuZy5 IOR9RZVtwtRucIGF9C+rgGAYVnNnEawdK1Gc0CMJ98xSS+C22R1QA8156F30hhtMGxRL agFgyUlaoR1o0Tgewd1HuD+38J3Y0Yf3puE+imh30HVCxxAM9hRh+TdkeJeF+0fH0Mh+ Mk90Vg54Qul+b+5B4jfKMrR7YLplfnGcM+fNI5slh/VNBff+8S3ERm5FGrQlPDDAvo1e SEX2NGH5VCt5c5Rl6IZ6YJadT5g9irgPOA4L64DUsPKrdBNPmg99T56b2jJJgeF6HlZE I0vQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=QvZ7pCmq; spf=pass (google.com: best guess record for 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 q4si9977595edn.161.2020.04.14.07.34.50; Tue, 14 Apr 2020 07:35:14 -0700 (PDT) Received-SPF: pass (google.com: best guess record for 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=QvZ7pCmq; spf=pass (google.com: best guess record for 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 S2405863AbgDNGRP (ORCPT + 99 others); Tue, 14 Apr 2020 02:17:15 -0400 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:60967 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2405854AbgDNGRL (ORCPT ); Tue, 14 Apr 2020 02:17:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1586845030; 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=DOrTl4YvBq5Mc/4tt5fmz7abkbkAWLtGCwVC/yQsB/U=; b=QvZ7pCmq0TCfuHCewRZ1S6GuNsFlu4mdFcjkULnxnhnz+To2zSqZG01T55tdhA/5Y6/Crg zBond/FWYHfhXAseF2iUpbedKMUAAyxp6YvkEetGBeJ4cUwD3hz2UaTTabEpnkzpp1wAxf wM/U3VYcLyjbUuOo+JwV6kCh/Z9riBc= 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-362-5IYuHBlQO_yDrdlI2Zhw9g-1; Tue, 14 Apr 2020 02:17:06 -0400 X-MC-Unique: 5IYuHBlQO_yDrdlI2Zhw9g-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 6CAFD800D5C; Tue, 14 Apr 2020 06:17:05 +0000 (UTC) Received: from kamzik.brq.redhat.com (unknown [10.40.193.1]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 247D65D9CD; Tue, 14 Apr 2020 06:16:57 +0000 (UTC) Date: Tue, 14 Apr 2020 08:16:54 +0200 From: Andrew Jones To: Sean Christopherson Cc: Wainer dos Santos Moschetta , pbonzini@redhat.com, kvm@vger.kernel.org, david@redhat.com, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, krish.sadhukhan@oracle.com Subject: Re: [PATCH v5 0/2] selftests: kvm: Introduce the mem_slot_test test Message-ID: <20200414061654.qhuo3hsslz32qwgc@kamzik.brq.redhat.com> References: <20200409220905.26573-1-wainersm@redhat.com> <20200410204509.GK22482@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200410204509.GK22482@linux.intel.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 10, 2020 at 01:45:09PM -0700, Sean Christopherson wrote: > On Thu, Apr 09, 2020 at 07:09:03PM -0300, Wainer dos Santos Moschetta wrote: > > This series introduces a new KVM selftest (mem_slot_test) that goal > > is to verify memory slots can be added up to the maximum allowed. An > > extra slot is attempted which should occur on error. > > > > The patch 01 is needed so that the VM fd can be accessed from the > > test code (for the ioctl call attempting to add an extra slot). > > > > I ran the test successfully on x86_64, aarch64, and s390x. This > > is why it is enabled to build on those arches. > > Any objection to folding these patches into a series I have to clean up > set_memory_region_test (which was mentioned in a prior version) and add > this as a testcase to set_memory_region_test instead of creating a whole > new test? > > A large chunk of set_memory_region_test will still be x86_64 only, but > having the test reside in common code will hopefully make it easier to > extend to other architectures. > Yes, that would be my preference as well. Eventually I decided it could be done later, but I still prefer it being done from the beginning. Thanks, drew