-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about VM_EXIT_ACK_INTR_ON_EXIT #31
Comments
It's not needed. In Bareflank, we don't set it in the base hypervisor. |
Nice, thanks Rian! |
It’s not needed, you’re right. Want to do a pull request please (and test
it?)
On Thu, Aug 2, 2018 at 12:12 AM Parallel Xenoexcite < ***@***.***> wrote:
Nice, thanks Rian!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFxIeLjG10LKWt7CnBjBJSwxGTsFQaFEks5uMjXHgaJpZM4Vn1IM>
.
--
Best regards,
Alex Ionescu
|
If testing inside of the VMWare is enough, I'll gladly provide pull request later today. :) |
Yep it’s eniugh :)
On Thu, Aug 2, 2018 at 4:35 PM Parallel Xenoexcite ***@***.***> wrote:
If testing inside of the VMWare is enough, I'll gladly provide pull
request later today. :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFxIeOj_4sZn4WeJ3HR39M9CeNFavn-Mks5uMxw5gaJpZM4Vn1IM>
.
--
Best regards,
Alex Ionescu
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
is setting VM_EXIT_ACK_INTR_ON_EXIT flag really necessary, if PIN_BASED_EXT_INTR is not set? I hope it's not super stupid question, but if I understand Intel Manual correctly, you shouldn't get any VMEXITs for external interrupts when PIN_BASED_EXT_INTR is not set - and if this is the case, the VM_EXIT_ACK_INTR_ON_EXIT is unnecessary.
I'm quite confused by this - I've been stuck on the VM_EXIT_ACK_INTR_ON_EXIT flag for too long in the Intel Manual, and when I thought I understand what it does, I realised many "simple opensource hypervisors" unneccessarily set it (SimpleVisor, ksm, HyperPlatform, ...).
So now I'm wondering, if either my understanding is correct OR if everyone just blatantly copy-pasted this practice from somewhere :)
If I'm completely wrong, I would be glad if you corrected me.
The text was updated successfully, but these errors were encountered: