Re: [STRAWMAN PATCH] KVM: PPC: Add ioctl to specify interrupt controller architecture to emulate

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

 



On Thu, Mar 14, 2013 at 01:15:35PM -0500, Scott Wood wrote:
> On 03/13/2013 08:26:20 PM, Paul Mackerras wrote:

> >I arbitrarily
> >assigned 0x58494353 for KVM_CAP_IRQ_XICS as the args[0] value to
> >indicate XICS.
> 
> Why is it called KVM_CAP_<whatever> if it's not a capability?

Because it's associated with a capability.  I'm not wedded to the name.

> >I think it would be better if we don't have to get a
> >new capability number assigned every time we want to add a new type of
> >interrupt controller.
> 
> How often does it really happen?  If a simple enumeration is good
> enough for identifying the main IRQ controller device type, it
> should be good enough for identifying the vcpu irq arch.

Whatever.  I really don't care at this point, I'm just getting
extremely tired of the bikeshedding.  If you don't like it, propose
something.

Paul.
--
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