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]

 




Am 09.03.2013 um 03:26 schrieb Paul Mackerras <paulus@xxxxxxxxx>:

> On Fri, Mar 08, 2013 at 12:04:30PM +0100, Alexander Graf wrote:
>> 
>> 
>> Am 08.03.2013 um 11:37 schrieb Paul Mackerras <paulus@xxxxxxxxx>:
>> 
>>> I have
>>> used the first argument (cap->args[0]) to specify which interrupt
>>> controller you want to connect the vcpu to.
>> 
>> Ah, nice idea. So you basically make the vcpu connection explicit. Perfect! Then just pass the interrupt controller pin id in cap->args[1] so we don't need to guess which vcpu we're talking about and all is well :). No implicit assumptions left in the kernel.
> 
> By "pin", do you mean output pin of the interrupt controller, or input
> pin of the CPU (i.e. external/debug/critical)?

I basically mean the interrupt controller's notion of that cpu's ID. That can just as well be multiple output pins :).


Alex

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