Patch for MS Hyper V (virtualization)

[Sergey Babkin]

   (Let's see if I've figured yet another workaround for the web
   interface   The address space used by the card I think is actually 0x80 bytes   in the I/O port space. The card has it located at the port 0xEC00.
   Yester   card's registers    all ones written to this    (1 is the I/O space indicator),    not the missing bit 0 (which should be    I've tried adding it back, and it made no diffe   I'll try FreeBSD 8 and see what happens.
   -SB
   Ap
     On Monday 06 April 2009 11:12:33     > John Baldwin wrote:
     > >
     >      > > >     > >     >     > > > > Hmm, the problem is we need to be able t     to size them.
     б Any
     > > OS
     > > &     regions are     being
     > > > > decoded by devices. б We can't avoid     > > >
     > > > I have only vague ide     correct diagnosis
     > > > in this     (Windows,
     > >      the original     > > > premise is wrong-ish.
     > >
     > > Every O     defined
     procedure<     register, and it is      > > device gets memory and I/O port resources. OS (or B     writes a starting
     > > address into the register to tell the P     given
     > > resource "starts".
     >
     > Th     > done it.      > so it doesn't      Yes it does because we don't know how _big_ the BAR      has to know if
     the device is decoding 1MB or 64KB because w     entire
     window to prevent any other devices from u     write the
     existing value, we write all 1's to i     lower N
     bits "stick" at zero and we use that t     size. See
     pci_add_map() in sys/dev/pci/pci.c
     > Anyway, as far as I can tell, it's only the base register of
          > qu     >
     >      this
     >      > anythi     Can you test unmodified FreeBSD      relative to
     7 to disable decoding vi     BARs that may
     address this.
          --
     John Baldwin

References

   1. 3D"mailto:jhb at freebsd.org"
   2. 3D"mailto:jhb at freebsd.org"