Hi James,

On 9/19/20 2:15 AM, James Morse wrote:

On 30/07/2020 02:45, Gavin Shan wrote:

quoted

This splits struct sdei_event into two structs: sdei_event and
sdei_internal_event. The former one can be dereferenced from external
module like arm64/kvm when SDEI virtualization is supported. The later
one is used by the client driver only.

This should be part of the series that need its.

I don't see any reason to share this as it risks muddling events the OS has as a client,
with those its offering as a hypervisor.

I doubt any KVM support would need to have anything to do with the client support.

The same argument goes for patch 15.

I'll drop PATCH[14/15] and PATCH[15/15] from this series and fold them
into the series of "Support SDEI virtualization". Lets have more discussion
when that series is reviewed.

The primary reason is to export "struct sdei_event" to KVM so that the
information about the SDEI event, like priority/signaled etc, can be
fetched from the struct. It's only meaningful if the corresponding
SDEI event is exported by underly firmware and passed through to the
guest.

Cheers,
Gavin



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel