* Virtual Interrupt Delivery
@ 2017-02-27 18:13 Dmitry Rockosov
2017-03-01 20:35 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 3+ messages in thread
From: Dmitry Rockosov @ 2017-02-27 18:13 UTC (permalink / raw)
To: Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 421 bytes --]
Hi guys,
Do you know when *recognized* Virtual Interrupt on VM-Entry will be
delivered if Virtual-Interrupt Delivery is enabled and interrupt delivery
is blocking by STI?
Previously, VMM used Interrupt-Window, but as I see in XEN code,
Interrupt-Window
is not used when Virtual Interrupt Delivery is enabled.
Does it mean, we will get Virtual Interrupt on the next VM-entry?
Thank you!
Best Regards,
Rockosov Dmitry
[-- Attachment #1.2: Type: text/html, Size: 1239 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Virtual Interrupt Delivery
2017-02-27 18:13 Virtual Interrupt Delivery Dmitry Rockosov
@ 2017-03-01 20:35 ` Konrad Rzeszutek Wilk
2017-03-02 6:27 ` Tian, Kevin
0 siblings, 1 reply; 3+ messages in thread
From: Konrad Rzeszutek Wilk @ 2017-03-01 20:35 UTC (permalink / raw)
To: Dmitry Rockosov, kevin.tian, jun.nakajima; +Cc: Xen-devel
On Mon, Feb 27, 2017 at 09:13:29PM +0300, Dmitry Rockosov wrote:
> Hi guys,
>
> Do you know when *recognized* Virtual Interrupt on VM-Entry will be
> delivered if Virtual-Interrupt Delivery is enabled and interrupt delivery
> is blocking by STI?
This sounds like a good question to the Intel maintainers, CC-ing them.
>
> Previously, VMM used Interrupt-Window, but as I see in XEN code,
> Interrupt-Window
> is not used when Virtual Interrupt Delivery is enabled.
Right, the Intel SDM has a whole section about that.
>
> Does it mean, we will get Virtual Interrupt on the next VM-entry?
By my understanding of the Intel SDM it depends on whether the
vector is one of those that the CPU can inject without involving
the VMM.
I would recommend you read the Intel SDM - the answer may be right
there.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Virtual Interrupt Delivery
2017-03-01 20:35 ` Konrad Rzeszutek Wilk
@ 2017-03-02 6:27 ` Tian, Kevin
0 siblings, 0 replies; 3+ messages in thread
From: Tian, Kevin @ 2017-03-02 6:27 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, Dmitry Rockosov, Nakajima, Jun; +Cc: Xen-devel
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> Sent: Thursday, March 02, 2017 4:36 AM
>
> On Mon, Feb 27, 2017 at 09:13:29PM +0300, Dmitry Rockosov wrote:
> > Hi guys,
> >
> > Do you know when *recognized* Virtual Interrupt on VM-Entry will be
> > delivered if Virtual-Interrupt Delivery is enabled and interrupt delivery
> > is blocking by STI?
>
> This sounds like a good question to the Intel maintainers, CC-ing them.
virtual interrupt delivery doesn't change the implication of blocking
by STI. It will be evaluated and delivered when it's allowed.
>
> >
> > Previously, VMM used Interrupt-Window, but as I see in XEN code,
> > Interrupt-Window
> > is not used when Virtual Interrupt Delivery is enabled.
>
> Right, the Intel SDM has a whole section about that.
> >
> > Does it mean, we will get Virtual Interrupt on the next VM-entry?
>
> By my understanding of the Intel SDM it depends on whether the
> vector is one of those that the CPU can inject without involving
> the VMM.
>
> I would recommend you read the Intel SDM - the answer may be right
> there.
yes SDM has a very clear description of when a virtual interrupt
delivery will happen. check CH29.2 (Evaluation and Delivery of
Virtual Interrupts).
Thanks
Kevin
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-03-02 6:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-02-27 18:13 Virtual Interrupt Delivery Dmitry Rockosov
2017-03-01 20:35 ` Konrad Rzeszutek Wilk
2017-03-02 6:27 ` Tian, Kevin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).