From nobody Tue Nov 26 15:48:08 2024 Delivered-To: importer@patchew.org Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1707204204; cv=none; d=zohomail.com; s=zohoarc; b=I4y/GehEw+ssjPyUbQzYnMv1nMb+Ac3VtbIyhReIrhvxh3He8hOySEaXumFcQn6srVoKudABCGbrgsZg/jL6NbyrwzFGP6oXSbL5MjDUq6Z5S9GoFO3Cf75QBFcZXh3rFjBDag0VRIvZV6IR6T2N7NS4MW0wMEl7BQSAzeVwGjk= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1707204204; h=Content-Transfer-Encoding:Cc:Cc:Date:Date:From:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:Subject:To:To:Message-Id:Reply-To; bh=VaDWX+qoqmQOU3mjoQIubYBKd2PJY0JKXQfY2XUfyJY=; b=js4RPScuXwQwyNyjZsgnnIuMEEz5wWRPYyVfiwQW9Z8znAP0TB6uP8V4eN7W8/kvt9jF0Nmx/iHqf4yhe+6r+FreBq20aW2gdzQcyJllEaGHTvXdGc4VvJZzNnWecsj3cOTco71QmZhasp9Wxx9BJ5eG84mpOUBptgDxYYk2i6w= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) by mx.zohomail.com with SMTPS id 1707204204711701.3414881357272; Mon, 5 Feb 2024 23:23:24 -0800 (PST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rXFn1-0002sZ-In; Tue, 06 Feb 2024 02:22:43 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rXFmy-0002ox-Tm for qemu-devel@nongnu.org; Tue, 06 Feb 2024 02:22:40 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rXFmx-0006n3-4g for qemu-devel@nongnu.org; Tue, 06 Feb 2024 02:22:40 -0500 Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-327-LFz5gNNkOuCHZlds9xrBRA-1; Tue, 06 Feb 2024 02:22:32 -0500 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B307385A58B; Tue, 6 Feb 2024 07:22:31 +0000 (UTC) Received: from t14s.redhat.com (unknown [10.39.192.127]) by smtp.corp.redhat.com (Postfix) with ESMTP id A2D141121312; Tue, 6 Feb 2024 07:22:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1707204157; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VaDWX+qoqmQOU3mjoQIubYBKd2PJY0JKXQfY2XUfyJY=; b=UAKILHH83RTzOtNRmQxaL1+pBK9551yDOMtYgFXj4vTmGbVt+YPQS03E/glffdrsGe9slr X4MiaegUUQfkUxHIEy/BVMciXcl2MtpqfpEpV+8wr9NR1uuWDdNhKwnLq+FNXcLdZv75sx nNhdZWtAXpPJWwxl/oMR9TCynhCMuL0= X-MC-Unique: LFz5gNNkOuCHZlds9xrBRA-1 From: David Hildenbrand To: qemu-devel@nongnu.org Cc: Peter Maydell , Paolo Bonzini , David Hildenbrand , Zhenyu Zhang , Michal Privoznik , Mario Casquero , "Maciej S . Szmigiero" Subject: [PULL v3 2/3] memory-device: reintroduce memory region size check Date: Tue, 6 Feb 2024 08:22:24 +0100 Message-ID: <20240206072225.21187-3-david@redhat.com> In-Reply-To: <20240206072225.21187-1-david@redhat.com> References: <20240206072225.21187-1-david@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.3 Received-SPF: pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) client-ip=209.51.188.17; envelope-from=qemu-devel-bounces+importer=patchew.org@nongnu.org; helo=lists.gnu.org; Received-SPF: pass client-ip=170.10.129.124; envelope-from=david@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -23 X-Spam_score: -2.4 X-Spam_bar: -- X-Spam_report: (-2.4 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.285, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+importer=patchew.org@nongnu.org Sender: qemu-devel-bounces+importer=patchew.org@nongnu.org X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1707204206109100003 Content-Type: text/plain; charset="utf-8" We used to check that the memory region size is multiples of the overall requested address alignment for the device memory address. We removed that check, because there are cases (i.e., hv-balloon) where devices unconditionally request an address alignment that has a very large alignment (i.e., 32 GiB), but the actual memory device size might not be multiples of that alignment. However, this change: (a) allows for some practically impossible DIMM sizes, like "1GB+1 byte". (b) allows for DIMMs that partially cover hugetlb pages, previously reported in [1]. Both scenarios don't make any sense: we might even waste memory. So let's reintroduce that check, but only check that the memory region size is multiples of the memory region alignment (i.e., page size, huge page size), but not any additional memory device requirements communicated using md->get_min_alignment(). The following examples now fail again as expected: (a) 1M with 2M THP qemu-system-x86_64 -m 4g,maxmem=3D16g,slots=3D1 -S -nodefaults -nographic \ -object memory-backend-ram,id=3Dmem1,size=3D1M \ -device pc-dimm,id=3Ddimm1,memdev=3Dmem1 -> backend memory size must be multiple of 0x200000 (b) 1G+1byte qemu-system-x86_64 -m 4g,maxmem=3D16g,slots=3D1 -S -nodefaults -nographic \ -object memory-backend-ram,id=3Dmem1,size=3D1073741825B \ -device pc-dimm,id=3Ddimm1,memdev=3Dmem1 -> backend memory size must be multiple of 0x200000 (c) Unliagned hugetlb size (2M) qemu-system-x86_64 -m 4g,maxmem=3D16g,slots=3D1 -S -nodefaults -nographic \ -object memory-backend-file,id=3Dmem1,mem-path=3D/dev/hu= gepages/tmp,size=3D511M \ -device pc-dimm,id=3Ddimm1,memdev=3Dmem1 backend memory size must be multiple of 0x200000 (d) Unliagned hugetlb size (1G) qemu-system-x86_64 -m 4g,maxmem=3D16g,slots=3D1 -S -nodefaults -nographic \ -object memory-backend-file,id=3Dmem1,mem-path=3D/dev/h= ugepages1G/tmp,size=3D2047M \ -device pc-dimm,id=3Ddimm1,memdev=3Dmem1 -> backend memory size must be multiple of 0x40000000 Note that this fix depends on a hv-balloon change to communicate its additional alignment requirements using get_min_alignment() instead of through the memory region. [1] https://lkml.kernel.org/r/f77d641d500324525ac036fe1827b3070de75fc1.1701= 088320.git.mprivozn@redhat.com Message-ID: <20240117135554.787344-3-david@redhat.com> Reported-by: Zhenyu Zhang Reported-by: Michal Privoznik Fixes: eb1b7c4bd413 ("memory-device: Drop size alignment check") Tested-by: Zhenyu Zhang Tested-by: Mario Casquero Reviewed-by: Maciej S. Szmigiero Signed-off-by: David Hildenbrand --- hw/mem/memory-device.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/hw/mem/memory-device.c b/hw/mem/memory-device.c index a1b1af26bc..e098585cda 100644 --- a/hw/mem/memory-device.c +++ b/hw/mem/memory-device.c @@ -374,6 +374,20 @@ void memory_device_pre_plug(MemoryDeviceState *md, Mac= hineState *ms, goto out; } =20 + /* + * We always want the memory region size to be multiples of the memory + * region alignment: for example, DIMMs with 1G+1byte size don't make + * any sense. Note that we don't check that the size is multiples + * of any additional alignment requirements the memory device might + * have when it comes to the address in physical address space. + */ + if (!QEMU_IS_ALIGNED(memory_region_size(mr), + memory_region_get_alignment(mr))) { + error_setg(errp, "backend memory size must be multiple of 0x%" + PRIx64, memory_region_get_alignment(mr)); + return; + } + if (legacy_align) { align =3D *legacy_align; } else { --=20 2.43.0