From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0340DC77B7A for ; Fri, 19 May 2023 08:50:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229489AbjESIu6 (ORCPT ); Fri, 19 May 2023 04:50:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39122 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230522AbjESIut (ORCPT ); Fri, 19 May 2023 04:50:49 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1E1CBE73 for ; Fri, 19 May 2023 01:50:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1684486200; 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=sAIqcNSg1jUS/ZZ6Q74aglsapI+xga8RTTWMs46LGnk=; b=IwFgtftRWaB6LEZOa6NKKx8NLDh83IloDmWVGm4y2K/q5/J7iw+LdBv9WPjWDBtX6gsFsd 54VpqldkfCOZm3+PC7cQY+lc5nxmCevh/W763+G7z6WEOkZu9iVrDw6BNonUD5l8rtVtRL 814O6nObmbCtBGxw2cazHlgjxrYd8HQ= Received: from mail-lj1-f198.google.com (mail-lj1-f198.google.com [209.85.208.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-668-ixF65JVVPXaXLo2hKue6-w-1; Fri, 19 May 2023 04:49:57 -0400 X-MC-Unique: ixF65JVVPXaXLo2hKue6-w-1 Received: by mail-lj1-f198.google.com with SMTP id 38308e7fff4ca-2ac7e062911so16102991fa.2 for ; Fri, 19 May 2023 01:49:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684486195; x=1687078195; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=sAIqcNSg1jUS/ZZ6Q74aglsapI+xga8RTTWMs46LGnk=; b=JpAOshKf+ZLpnSq+qzpymtJ7S60bBdqg2uhowo85kUxUXfoPLvp0103Uh/n4qQI+w/ r+dX8YRKsk8qBuEYcXy2DqXLCrmPp1LaEWxMZGKoWxzfzSGWwvOtZv4MRO/bVRqcs5bc y14WVpOYlMxkLY25Xbsc+795FXatVhi1kxdETkGXKlyqoOniePHtwSY4mhONgtiwhZd0 QDTmtp9PfXwx1tUIYG5eT4MiJ3Ww/a96LexMzOwKv3O2ofTnVgePGjrq6TYIyqBl0t5o xNMjmukYXL5Aap/tlb7aHqPCnXscEMj69jFy5yxBVxT6D8OAQuNbkAjpSDbBPeNpSHPo IAaA== X-Gm-Message-State: AC+VfDwKot06occz3r3BD9pgP94EeXiXfSkAjU562PNtJr82Tc1X0pmb udb8QXRytEGQ6vw3tkEEZH0/YNLOVcZr0UKsCBUgyIQOC74Z0EBiSieN1K9/w5swXCOWH8O3ub/ u/CilQ9m+a9EHla27Gizg X-Received: by 2002:a2e:9c41:0:b0:2a7:6e37:ee68 with SMTP id t1-20020a2e9c41000000b002a76e37ee68mr419748ljj.12.1684486195653; Fri, 19 May 2023 01:49:55 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4h/RBMG4WF9ve5fBx7mJkNNme62aR0mw5ncO+jQ7BcZhAczwljFZif6SBGvR1rjHcvG+Y9nQ== X-Received: by 2002:a2e:9c41:0:b0:2a7:6e37:ee68 with SMTP id t1-20020a2e9c41000000b002a76e37ee68mr419737ljj.12.1684486195312; Fri, 19 May 2023 01:49:55 -0700 (PDT) Received: from redhat.com ([2a02:14f:175:3e4d:6703:27b9:6f74:5282]) by smtp.gmail.com with ESMTPSA id b7-20020a2e9887000000b002a9ec7c0b4csm718736ljj.10.2023.05.19.01.49.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 19 May 2023 01:49:54 -0700 (PDT) Date: Fri, 19 May 2023 04:49:46 -0400 From: "Michael S. Tsirkin" To: Jonathan Cameron Cc: qemu-devel@nongnu.org, Fan Ni , linux-cxl@vger.kernel.org, linuxarm@huawei.com, Ira Weiny , Alison Schofield , Michael Roth , Philippe =?iso-8859-1?Q?Mathieu-Daud=E9?= , Dave Jiang , Markus Armbruster , Daniel P =?iso-8859-1?Q?=2E_Berrang=E9?= , Eric Blake , Mike Maslenkin , =?iso-8859-1?Q?Marc-Andr=E9?= Lureau , Thomas Huth Subject: Re: [PATCH v5 0/6] hw/cxl: Poison get, inject, clear Message-ID: <20230519030942-mutt-send-email-mst@kernel.org> References: <20230423162013.4535-1-Jonathan.Cameron@huawei.com> MIME-Version: 1.0 In-Reply-To: <20230423162013.4535-1-Jonathan.Cameron@huawei.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Precedence: bulk List-ID: X-Mailing-List: linux-cxl@vger.kernel.org On Sun, Apr 23, 2023 at 05:20:07PM +0100, Jonathan Cameron wrote: > v5: More details in each patch. > - Simpler algorithm to find entry when clearing. > - Improvements to debugability and docs for 24 bit endian functions. > - Use of ROUND_DOWN() to simplify the various alignment questions. > - Use CXL_CACHELINE_SIZE define to explain the mysterious 64 byte > granularity > - Use memory_region_size() instead of direct accesses. picked first 3 but dropped the rest for now due to build errors. > Many of the precursors listed for v4 have now been applied, but > a few minor fixes have come up in the meantime so there are still > a few precursors including the volatile support left from v4 > precursors. > > Depends on > [PATCH 0/2] hw/cxl: CDAT file handling fixes. > [PATCH v2 0/3] hw/cxl: Fix decoder commit and uncommit handling > [PATCH 0/3] docs/cxl: Gathering of fixes for 8.0 CXL docs. > [PATCH v5 0/3] hw/mem: CXL Type-3 Volatile Memory Support > > Based on: Message-ID: 20230421132020.7408-1-Jonathan.Cameron@huawei.com > Based on: Message-ID: 20230421135906.3515-1-Jonathan.Cameron@huawei.com > Based on: Message-ID: 20230421134507.26842-1-Jonathan.Cameron@huawei.com > Based on: Message-ID: 20230421160827.2227-1-Jonathan.Cameron@huawei.com > > The kernel support for Poison handling is currently in the cxl/pending > branch and hopefully should be in the CXL pull request next week. > > https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git/log/?h=pending > > This code has been very useful for testing and helped identify various > corner cases. > > Updated cover letter. > > The series supports: > 1) Injection of variable length poison regions via QMP (to fake real > memory corruption and ensure we deal with odd overflow corner cases > such as clearing the middle of a large region making the list overflow > as we go from one long entry to two smaller entries. > 2) Read of poison list via the CXL mailbox. > 3) Injection via the poison injection mailbox command (limited to 64 byte > entries - spec constraint) > 4) Clearing of poison injected via either method. > > The implementation is meant to be a valid combination of impdef choices > based on what the spec allowed. There are a number of places where it could > be made more sophisticated that we might consider in future: > * Fusing adjacent poison entries if the types match. > * Separate injection list and main poison list, to test out limits on > injected poison list being smaller than the main list. > * Poison list overflow event (needs event log support in general) > * Connecting up to the poison list error record generation (rather complex > and not needed for currently kernel handling testing). > * Triggering the synchronous and asynchronous errors that occur on reads > and writes of the memory when the host receives poison. > > As the kernel code is currently fairly simple, it is likely that the above > does not yet matter but who knows what will turn up in future! > > > Ira Weiny (2): > hw/cxl: Introduce cxl_device_get_timestamp() utility function > bswap: Add the ability to store to an unaligned 24 bit field > > Jonathan Cameron (4): > hw/cxl: rename mailbox return code type from ret_code to CXLRetCode > hw/cxl: QMP based poison injection support > hw/cxl: Add poison injection via the mailbox. > hw/cxl: Add clear poison mailbox command support. > > docs/devel/loads-stores.rst | 1 + > hw/cxl/cxl-device-utils.c | 15 ++ > hw/cxl/cxl-mailbox-utils.c | 289 ++++++++++++++++++++++++++++++------ > hw/mem/cxl_type3.c | 93 ++++++++++++ > hw/mem/cxl_type3_stubs.c | 6 + > include/hw/cxl/cxl.h | 1 + > include/hw/cxl/cxl_device.h | 23 +++ > include/qemu/bswap.h | 25 ++++ > qapi/cxl.json | 18 +++ > 9 files changed, 429 insertions(+), 42 deletions(-) > > -- > 2.37.2