On 03/13/2013 08:26:20 PM, Paul Mackerras wrote:
On Wed, Mar 13, 2013 at 07:14:48PM -0500, Scott Wood wrote:
On 03/08/2013 05:04:30 AM, Alexander Graf wrote:
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
On Thu, Mar 07, 2013 at 03:00:52PM +0100, Alexander Graf wrote:
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
On 14.03.2013, at 23:02, Paul Mackerras wrote:
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
On 03/14/2013 05:44:39 PM, Alexander Graf wrote:
On 14.03.2013, at 23:02, Paul Mackerras wrote:
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
On 03/13/2013 08:26:20 PM, Paul Mackerras wrote:
On Wed, Mar 13, 2013 at 07:14:48PM -0500, Scott Wood wrote:
On 03/08/2013 05:04:30 AM, Alexander Graf wrote:
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
On Thu, Mar 07, 2013 at 03:00:52PM +0100, Alexander Graf wrote:
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
On 14.03.2013, at 23:02, Paul Mackerras wrote:
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
On 03/14/2013 05:44:39 PM, Alexander Graf wrote:
On 14.03.2013, at 23:02, Paul Mackerras wrote:
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
On 03/08/2013 05:04:30 AM, Alexander Graf wrote:
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
On Thu, Mar 07, 2013 at 03:00:52PM +0100, Alexander Graf wrote:
Could you please (in a quick and drafty way) try and see if
setting the IRQ arch (using enable_cap) after the
On 14.03.2013, at 01:14, Scott Wood wrote:
On 03/08/2013 05:04:30 AM, Alexander Graf wrote:
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
On Thu, Mar 07, 2013 at 03:00:52PM +0100, Alexander Graf wrote:
Could you please (in a quick and drafty way) try and see if setting
On Wed, Mar 13, 2013 at 07:14:48PM -0500, Scott Wood wrote:
On 03/08/2013 05:04:30 AM, Alexander Graf wrote:
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
On Thu, Mar 07, 2013 at 03:00:52PM +0100, Alexander Graf wrote:
Could you please (in a quick and drafty way)
On 03/08/2013 05:04:30 AM, Alexander Graf wrote:
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
On Thu, Mar 07, 2013 at 03:00:52PM +0100, Alexander Graf wrote:
Could you please (in a quick and drafty way) try and see if
setting the IRQ arch (using enable_cap) after the
On 14.03.2013, at 01:14, Scott Wood wrote:
On 03/08/2013 05:04:30 AM, Alexander Graf wrote:
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
On Thu, Mar 07, 2013 at 03:00:52PM +0100, Alexander Graf wrote:
Could you please (in a quick and drafty way) try and see if setting
On Wed, Mar 13, 2013 at 07:14:48PM -0500, Scott Wood wrote:
On 03/08/2013 05:04:30 AM, Alexander Graf wrote:
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
On Thu, Mar 07, 2013 at 03:00:52PM +0100, Alexander Graf wrote:
Could you please (in a quick and drafty way)
Am 09.03.2013 um 03:26 schrieb Paul Mackerras pau...@samba.org:
On Fri, Mar 08, 2013 at 12:04:30PM +0100, Alexander Graf wrote:
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
I have
used the first argument (cap-args[0]) to specify which interrupt
controller you want
Am 09.03.2013 um 03:26 schrieb Paul Mackerras pau...@samba.org:
On Fri, Mar 08, 2013 at 12:04:30PM +0100, Alexander Graf wrote:
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
I have
used the first argument (cap-args[0]) to specify which interrupt
controller you want
On Thu, Mar 07, 2013 at 03:00:52PM +0100, Alexander Graf wrote:
Could you please (in a quick and drafty way) try and see if setting the IRQ
arch (using enable_cap) after the vcpu got created would work for you?
That enable_cap would then have to loop through all devices and notify irq
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
On Thu, Mar 07, 2013 at 03:00:52PM +0100, Alexander Graf wrote:
Could you please (in a quick and drafty way) try and see if setting the IRQ
arch (using enable_cap) after the vcpu got created would work for you?
That
On Fri, Mar 08, 2013 at 12:04:30PM +0100, Alexander Graf wrote:
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
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
On Fri, Mar 08, 2013 at 12:04:30PM +0100, Alexander Graf wrote:
Am 08.03.2013 um 11:37 schrieb Paul Mackerras pau...@samba.org:
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
On 07.03.2013, at 04:29, Paul Mackerras wrote:
This adds a new ioctl, KVM_SET_IRQ_ARCHITECTURE, which is intended to
be called by userspace to specify that it wishes the kernel to emulate
a specific interrupt controller architecture. This doesn't imply the
creation of any specific device,
On 07.03.2013, at 04:29, Paul Mackerras wrote:
This adds a new ioctl, KVM_SET_IRQ_ARCHITECTURE, which is intended to
be called by userspace to specify that it wishes the kernel to emulate
a specific interrupt controller architecture. This doesn't imply the
creation of any specific device,
This adds a new ioctl, KVM_SET_IRQ_ARCHITECTURE, which is intended to
be called by userspace to specify that it wishes the kernel to emulate
a specific interrupt controller architecture. This doesn't imply the
creation of any specific device, but does indicate that when vcpus are
created, space
This adds a new ioctl, KVM_SET_IRQ_ARCHITECTURE, which is intended to
be called by userspace to specify that it wishes the kernel to emulate
a specific interrupt controller architecture. This doesn't imply the
creation of any specific device, but does indicate that when vcpus are
created, space
24 matches
Mail list logo
