linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gshan@redhat.com>
To: linux-arm-kernel@lists.infradead.org
Cc: mark.rutland@arm.com, gshan@redhat.com, james.morse@arm.com
Subject: [Question] How to testing SDEI client driver
Date: Tue, 30 Jun 2020 15:17:55 +1000	[thread overview]
Message-ID: <8cdef8ea-e550-ccff-2041-526d6f6fcda0@redhat.com> (raw)

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

             reply	other threads:[~2020-06-30  5:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30  5:17 Gavin Shan [this message]
2020-07-01 11:57 ` [Question] How to testing SDEI client driver James Morse
2020-07-03  0:26   ` Gavin Shan
2020-07-08 16:11     ` James Morse
2020-07-08 16:49       ` Paolo Bonzini
2020-07-09  5:33         ` Gavin Shan
2020-07-09 18:31           ` James Morse
2020-07-10  9:08             ` Gavin Shan
2020-07-10  9:38               ` Paolo Bonzini
2020-07-09 18:30         ` James Morse
2020-07-09 18:50           ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8cdef8ea-e550-ccff-2041-526d6f6fcda0@redhat.com \
    --to=gshan@redhat.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).