Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 84DFDC433DB for ; Thu, 28 Jan 2021 10:19:53 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 0D82C64DCC for ; Thu, 28 Jan 2021 10:19:52 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0D82C64DCC Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from list by lists.xenproject.org with outflank-mailman.76846.138826 (Exim 4.92) (envelope-from ) id 1l54Ou-00024f-0H; Thu, 28 Jan 2021 10:19:44 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 76846.138826; Thu, 28 Jan 2021 10:19:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1l54Ot-00024Y-Sz; Thu, 28 Jan 2021 10:19:43 +0000 Received: by outflank-mailman (input) for mailman id 76846; Thu, 28 Jan 2021 10:19:43 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1l54Ot-00024T-CL for xen-devel@lists.xenproject.org; Thu, 28 Jan 2021 10:19:43 +0000 Received: from mx2.suse.de (unknown [195.135.220.15]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id df3136b3-2c73-4baa-9e45-6b4fad499970; Thu, 28 Jan 2021 10:19:42 +0000 (UTC) Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id BC854ACF4; Thu, 28 Jan 2021 10:19:41 +0000 (UTC) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: df3136b3-2c73-4baa-9e45-6b4fad499970 X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1611829181; h=from:from:reply-to: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=KOZxr9SBGDc5a84roM/DomORvI+5KPSD1CGP8Sswfdc=; b=gJ3v7mkzrmKR/9e4qnCGi4zhh2RtHqeexgnvCurchkzB0O4I9MCABiscmili7EMpuQi7a5 xblaiQ/qX3IWZrTWnz2R2ZLz4Eyhj2m8nDEAPLj6VeghJlwx4Lf8PbZZAQQLNtDt4VfAAs gA4RF/7dypGI89H5wsACWgO/rjAk0h0= Subject: Re: [PATCH] x86/pod: Do not fragment PoD memory allocations To: Elliott Mitchell Cc: George Dunlap , Wei Liu , Roger Pau Monn?? , xen-devel@lists.xenproject.org, Andrew Cooper References: <202101242308.10ON8Umj004866@m5p.com> <67ef8210-a65f-9d6a-bea1-46ce06d47fb7@citrix.com> From: Jan Beulich Message-ID: <44450edc-9a64-8a6e-e8d3-3a3f726a96bc@suse.com> Date: Thu, 28 Jan 2021 11:19:41 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 27.01.2021 23:28, Elliott Mitchell wrote: > On Wed, Jan 27, 2021 at 09:03:32PM +0000, Andrew Cooper wrote: >> So.?? What *should* happen is that if QEMU/OVMF dirties more memory than >> exists in the PoD cache, the domain gets terminated. >> >> Irrespective, Xen/dom0 dying isn't an expected consequence of any normal >> action like this. >> >> Do you have a serial log of the crash??? If not, can you set up a crash >> kernel environment to capture the logs, or alternatively reproduce the >> issue on a different box which does have serial? > > No, I don't. I'm setup to debug ARM failures, not x86 ones. Then alternatively can you at least give conditions that need to be met to observe the problem, for someone to repro and then debug? (The less complex the better, of course.) Jan