Re: [Xen-devel] fail to register IRQ for virtualization exception
Or should I modify the linux kernel to add support for handling #VE exception? 2016-09-02 16:35 GMT+08:00 Big Strong : > Sorry for that. Could you give any suggestions on how to register the IRQ > handler for #VE? > > 2016-09-02 15:52 GMT+08:00 Jan Beulich : > >> >>> On 02.09.16 at 04:59, wrote: >> > I'm recently trying to utilize the virtualization exception (#VE) >> feature. >> > As the document says, #VE is handled by guest interrupt handler. The IRQ >> > number of #VE is 20. However, when I tried to register an IRQ handler >> for >> > #VE, it returns errno -22, which means invalid arguments. >> > >> > request_irq(20, ve_handler, IRQF_NO_SUSPEND, "ve", NULL) >> > >> > Is there anything wrong? >> >> You're mixing up exception vectors and IRQ numbers. >> >> Jan >> >> > ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] fail to register IRQ for virtualization exception
Sorry for that. Could you give any suggestions on how to register the IRQ handler for #VE? 2016-09-02 15:52 GMT+08:00 Jan Beulich : > >>> On 02.09.16 at 04:59, wrote: > > I'm recently trying to utilize the virtualization exception (#VE) > feature. > > As the document says, #VE is handled by guest interrupt handler. The IRQ > > number of #VE is 20. However, when I tried to register an IRQ handler for > > #VE, it returns errno -22, which means invalid arguments. > > > > request_irq(20, ve_handler, IRQF_NO_SUSPEND, "ve", NULL) > > > > Is there anything wrong? > > You're mixing up exception vectors and IRQ numbers. > > Jan > > ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
Re: [Xen-devel] fail to register IRQ for virtualization exception
>>> On 02.09.16 at 04:59, wrote: > I'm recently trying to utilize the virtualization exception (#VE) feature. > As the document says, #VE is handled by guest interrupt handler. The IRQ > number of #VE is 20. However, when I tried to register an IRQ handler for > #VE, it returns errno -22, which means invalid arguments. > > request_irq(20, ve_handler, IRQF_NO_SUSPEND, "ve", NULL) > > Is there anything wrong? You're mixing up exception vectors and IRQ numbers. Jan ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
[Xen-devel] fail to register IRQ for virtualization exception
Hello. I'm recently trying to utilize the virtualization exception (#VE) feature. As the document says, #VE is handled by guest interrupt handler. The IRQ number of #VE is 20. However, when I tried to register an IRQ handler for #VE, it returns errno -22, which means invalid arguments. request_irq(20, ve_handler, IRQF_NO_SUSPEND, "ve", NULL) Is there anything wrong? To handle this system reserved exception, should I modify the linux kernel instead of using loadable kernel module (LKM)? As the IRQ number 20 is not defined in linux kernel (traps.h), also no exception handling function is defined (traps.c). As it is defined as a system reserved exception, so I can't register it using LKM? BTW, I've already enabled #VE feature using HVMOP_altp2m_vcpu_enable_notify. The attachment is the definition of #VE from Intel Manual. ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel