Re: [RFC] Design changes for bidirectional interface compatibility.

[Paul Durrant <xadimgnik@xxxxxxxxx>]

On 30/08/2022 13:03, Martin Harvey wrote:
> -----Original Message-----
> From: win-pv-devel <win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx> On Behalf Of 
> Paul Durrant
>
> > Right, so there is no need for more compatibility code and I'd really like to 
> > keep it that way unless
> > there is a fundamental reason why the current scheme will not work. To my mind 
> > compatibility
> > in both directions will just complicate the code for no *good* reason.
> OK, you reckon it will be more pain than gain.
Yes, that's exactly my concern.

> > The network settings issue is therefore what we need to understand first, I 
> > think.
> Agreed. There is something FUBAR there.
Yes. I am sure it is written somewhere that the network config follows 
the container id such that things like the PCIe serial number cap 
(https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/wdm/ns-wdm-_pci_express_serial_number_capability) 
because it is use to generate the DO's container id if it is present. 
Hence by generating the container id from the MAC address we should be 
able to keep the settings. OTOH maybe bumping the instance id is 
overriding that in some way... which would be annoying.
  Paul

> MH.