On Fri, May 20, 2011 at 05:03:33PM +0200, Paolo Bonzini wrote: > SAM logical unit numbers are complicated beasts that can address > multiple levels of buses and targets before finally reaching > logical units. Begin supporting them by correctly parsing vSCSI > LUNs. > > Note that with the current (admittedly incorrect) code OpenFirmware > thought the devices were at "bus X, target 0, lun 0" (because OF > prefers access mode 0, which places bus numbers in the top byte), > while Linux thought it was "bus 0, target Y, lun 0" (because Linux > uses access mode 2, which places target numbers in the top byte). > With this patch, everything consistently uses the former notation.
Do we actually need the complete LUN encoding scheme? What speaks against always presenting the flat LUN addressing scheme to guests?
