extboot: Purpose of cmd value

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Anthony,

I have to fix extboot for non-KVM usage which means pushing its
variables to writable RAM (probably some spare INT vector(s) in the
BASIC area).

In that process, I stumbled over the cmd value passed to extboot_init,
then stored in qemu_malloc'ed memory, and finally reported to the guest
side via port 0x404. It's constant so far, always 1. So there is quite a
bit unused code and data on both sides. Can we drop that?

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux