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 X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,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 C4C5BC433DF for ; Tue, 30 Jun 2020 05:19:30 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (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 8B3E020720 for ; Tue, 30 Jun 2020 05:19:30 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="RjiynCQM"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="TF2C7Hh0" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8B3E020720 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Type: Content-Transfer-Encoding:Cc:Reply-To:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Date:Message-ID:Subject: From:To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Owner; bh=MupW4tHMJi1jZcdI9duII6tp4r6SoEVxlq7oNHzn0f8=; b=RjiynCQMp6RJEUiZStbjnF+nrp jUQiQxy9t/1gmCk2+5aY6kvJC/vMZbcnUHvoZR76Gtoj1rx24xXL322hiaye52ON/HLGDJBV549Ar E68bv9dYwsS2JJp9yH8O0pSnCk2/rsz5zPk4WnMWHRZ483PWfHnAx7raCN8lC6xUPn7R8RjtYGc60 kc3F3GibUtVIYxivrPueNLSAfajBwMsHJqHacBrq/C7dvPRvCGs5HWFIHR1uUXJ8FTOHMUFi68JL+ BM+lIJ7/9S8+yWna+IC2LWrwelUsB7N5mc20ks7ipSf8G2ZS6epmD6MWRk1P6gcpJi5pXNNucjvYu uqc4fZ7Q==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jq8el-0005fr-J4; Tue, 30 Jun 2020 05:18:07 +0000 Received: from us-smtp-1.mimecast.com ([207.211.31.81] helo=us-smtp-delivery-1.mimecast.com) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jq8ei-0005fe-H2 for linux-arm-kernel@lists.infradead.org; Tue, 30 Jun 2020 05:18:05 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1593494284; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=eAqXx1hKmcZYpXoV2DqfrVReM71CUqzVMXBeED0svHA=; b=TF2C7Hh0y95NHi0D6/y+NioESE2LIbYLwxGCqpqkd3t22aNqPCqpSeTBi6CXO5G9gJn8tS S7ecASlYumNPFBBcy7XhzlOBT6v2jMEYGP3aahU1jO03eogm07VqQOsPZa+LrtLw2apdzQ 6yb4fPPFPcBa0e0pccGLnIGoGZvp0Qw= 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-209-aqNWlZbTPASYX2ucMZ3YOA-1; Tue, 30 Jun 2020 01:18:01 -0400 X-MC-Unique: aqNWlZbTPASYX2ucMZ3YOA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id B87991800D42; Tue, 30 Jun 2020 05:18:00 +0000 (UTC) Received: from localhost.localdomain (vpn2-54-102.bne.redhat.com [10.64.54.102]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2E42060BF3; Tue, 30 Jun 2020 05:17:58 +0000 (UTC) To: linux-arm-kernel@lists.infradead.org From: Gavin Shan Subject: [Question] How to testing SDEI client driver Message-ID: <8cdef8ea-e550-ccff-2041-526d6f6fcda0@redhat.com> Date: Tue, 30 Jun 2020 15:17:55 +1000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.0 MIME-Version: 1.0 Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Gavin Shan Cc: mark.rutland@arm.com, gshan@redhat.com, james.morse@arm.com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Folks, I'm currently looking into SDEI client driver and reworking on it so that it can provide capability/services to arm64/kvm to get it virtualized. The primary reason is we want to use SDEI to deliver the asynchronous page fault notification from host to guest. The code of rework on SDEI client driver, including some cleanup, is almost done. Currently, I have issues on how to test/verify the client driver. Any suggestions regarding this are appreciated. It seems that TRF (Trusted Firmware) is the only firmware with SDEI service implemented and supported. If so, does it mean I need to install TRF on my bare metal machine? I'm wandering how it can be installed and not sure if there is any document about this. Besides, GHES seems the only user of SDEI in the linux kernel. If so, is there a way to inject the relevant errors and how? Thanks in advance for your comments and suggestions. Thanks, Gavin _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel