On Tue, Oct 03, 2023 at 04:40:48PM +0100, Jonathan Cameron wrote:
> On Thu, 28 Sep 2023 19:32:42 +0200 Lukas Wunner <lukas@xxxxxxxxx> wrote:
> > At any given time, only a single entity in a physical system may have
> > an SPDM connection to a device. That's because the GET_VERSION request
> > (which begins an authentication sequence) resets "the connection and all
> > context associated with that connection" (SPDM 1.3.0 margin no 158).
> >
> > Thus, when a device is passed through to a guest and the guest has
> > authenticated it, a subsequent authentication by the host would reset
> > the device's CMA-SPDM session behind the guest's back.
> >
> > Prevent by letting the guest claim exclusive CMA ownership of the device
> > during passthrough. Refuse CMA reauthentication on the host as long.
> > After passthrough has concluded, reauthenticate the device on the host.
>
> Is there anything stopping a PF presenting multiple CMA capable DOE
> instances? I'd expect them to have their own contexts if they do..
The spec does not seem to *explicitly* forbid a PF having multiple
CMA-capable DOE instances, but PCIe r6.1 sec 6.31.3 says:
"The instance of DOE used for CMA-SPDM must support ..."
Note the singular ("The instance"). It seems to suggest that the
spec authors assumed there's only a single DOE instance for CMA-SPDM.
Could you (as an English native speaker) comment on the clarity of the
two sentences "Prevent ... as long." above, as Ilpo objected to them?
The antecedent of "Prevent" is the undesirable behaviour in the preceding
sentence (host resets guest's SPDM connection).
The antecedent of "as long" is "during passthrough" in the preceding
sentence.
Is that clear and understandable for an English native speaker or
should I rephrase?
Thanks,
Lukas
