Re: VMSTATE_U64 vs. VMSTATE_UINT64

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

 



On 2011-05-04 20:16, Glauber Costa wrote:
> On Wed, 2011-05-04 at 20:04 +0200, Jan Kiszka wrote:
>> Hi guys,
>>
>> can anyone comment on commit e4d6d49061 ("introduce VMSTATE_U64") in
>> qemu-kvm again? I strongly suspect this thing was only introduced to be
>> able to grab from a __u64 (for kvmclock) without generating a compiler
>> warning that you may got when using uint64_t, right?
>>
>> Thanks,
>> Jan
>>
> I don't remember if it was kvmclock. IIRC, it was my irqchip
> implementation at the time. But I do remember the reason: it was indeed
> to be able to grab kernel data structures directly without a compile
> warning.
> 

Perfect. Then I will also include a revert/drop patch in my series that
switches the only user, kvmclock, to the upstream version.

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