Re: port-amd64/51919: boot-loader doesn't differentiate XEN and PAE module versions

[John Nemeth <jnemeth%cue.bc.ca@localhost>]

The following reply was made to PR port-amd64/51919; it has been noted by GNATS.

From: John Nemeth <jnemeth%cue.bc.ca@localhost>
To: gnats-bugs%NetBSD.org@localhost, port-amd64-maintainer%netbsd.org@localhost,
        gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, paul%whooppee.com@localhost
Cc: 
Subject: Re: port-amd64/51919: boot-loader doesn't differentiate XEN and PAE module versions
Date: Wed, 25 Jan 2017 22:19:01 -0800

 On Jan 26,  5:35am, Martin Husemann wrote:
 }
 } The following reply was made to PR port-amd64/51919; it has been noted by GNATS.
 } 
 } From: Martin Husemann <martin%duskware.de@localhost>
 }  module versions
 } Date: Thu, 26 Jan 2017 06:33:13 +0100
 } 
 }  I wonder if it would be better/simpler to add a boot.cfg option to override
 }  machine here (and while there, also the module path as discussed before
 
      Possibly.
 
 }  elsewhere ;-})
 }  
 }  The DomU kernels have a special section marking them:
 
      DomU kernels are loaded by Xen itself, the boot loader isn't
 involved at all.
 
 }  and Dom0 seem to have:
 }  
 }    [18] .note.Xen         NOTE             0000000000000000  00cc2ec8
 
      Do you know how to read these notes or at least check for
 their existance from the bootloader?  Also, the Dom0 kernel has to
 be loaded using the multiboot protocol and I don't think we have
 support for boot time loading of modules when using the multiboot
 protocol.
 
 }  but I don't know if both are required or the bootloader can rely on them
 }  to differentiate the two cases.
 }  
 }-- End of excerpt from Martin Husemann