* interrupt remapping support @ 2012-11-13 3:44 Abhinav Srivastava 2012-11-13 9:29 ` Gleb Natapov 0 siblings, 1 reply; 4+ messages in thread From: Abhinav Srivastava @ 2012-11-13 3:44 UTC (permalink / raw) To: kvm@vger.kernel.org Hi there, I would like to know if KVM supports interrupt remapping and queued invalidation. I could not find it in the kvm source code. I also noticed that these features are in KVM's TODO list. Is that accurate? Any pointers or direction would be appreciated. Thanks, Abhinav ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: interrupt remapping support 2012-11-13 3:44 interrupt remapping support Abhinav Srivastava @ 2012-11-13 9:29 ` Gleb Natapov [not found] ` <CALKiAsFsiiz6eyYWCzoYeL3WV1D56xQsHC57oP8tjX+wRjqixg@mail.gmail.com> 0 siblings, 1 reply; 4+ messages in thread From: Gleb Natapov @ 2012-11-13 9:29 UTC (permalink / raw) To: Abhinav Srivastava; +Cc: kvm@vger.kernel.org On Mon, Nov 12, 2012 at 10:44:51PM -0500, Abhinav Srivastava wrote: > Hi there, > > I would like to know if KVM supports interrupt remapping and queued > invalidation. I could not find it in the kvm source code. > I also noticed that these features are in KVM's TODO list. Is that > accurate? Any pointers or direction would be appreciated. > KVM does not implement VT-d spec if this is your question. Any help with this will be appreciated. -- Gleb. ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <CALKiAsFsiiz6eyYWCzoYeL3WV1D56xQsHC57oP8tjX+wRjqixg@mail.gmail.com>]
* Re: interrupt remapping support [not found] ` <CALKiAsFsiiz6eyYWCzoYeL3WV1D56xQsHC57oP8tjX+wRjqixg@mail.gmail.com> @ 2012-11-14 17:06 ` Gleb Natapov [not found] ` <CALKiAsHyJykMD+taSBMwikWcMY6bbXT2vqedvnyXNo_+S3vSAw@mail.gmail.com> 0 siblings, 1 reply; 4+ messages in thread From: Gleb Natapov @ 2012-11-14 17:06 UTC (permalink / raw) To: emdel; +Cc: Abhinav Srivastava, kvm@vger.kernel.org On Wed, Nov 14, 2012 at 05:46:45PM +0100, emdel wrote: > On Tue, Nov 13, 2012 at 10:29 AM, Gleb Natapov <gleb@redhat.com> wrote: > > > KVM does not implement VT-d spec if this is your question. Any help with > > this will be appreciated. > > > > Hello everybody, > following this link [1] it looks like that we can configure pass-through > devices for KVM guests, > so if it is the case and as you said KVM doesn't implement any Vt-d > specification, > are there any protections in place for DMA attacks? > > KVM uses VT-d on a host for device assignment. Guest running inside KVM will not see VT-d though since KVM does not emulate it. -- Gleb. ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <CALKiAsHyJykMD+taSBMwikWcMY6bbXT2vqedvnyXNo_+S3vSAw@mail.gmail.com>]
* Re: interrupt remapping support [not found] ` <CALKiAsHyJykMD+taSBMwikWcMY6bbXT2vqedvnyXNo_+S3vSAw@mail.gmail.com> @ 2012-11-14 17:35 ` Gleb Natapov 0 siblings, 0 replies; 4+ messages in thread From: Gleb Natapov @ 2012-11-14 17:35 UTC (permalink / raw) To: emdel; +Cc: Abhinav Srivastava, kvm@vger.kernel.org On Wed, Nov 14, 2012 at 06:31:30PM +0100, emdel wrote: > On Wed, Nov 14, 2012 at 6:06 PM, Gleb Natapov <gleb@redhat.com> wrote: > > > KVM uses VT-d on a host for device assignment. Guest running inside KVM > > will not see VT-d though since KVM does not emulate it. > > > > So another question comes up in my mind: > what's the purpose of the host devices assignment if I cannot use it for > the guest? > I do not think you understand what I am saying. You can use device assignment for a guest. -- Gleb. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-11-14 17:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-13 3:44 interrupt remapping support Abhinav Srivastava
2012-11-13 9:29 ` Gleb Natapov
[not found] ` <CALKiAsFsiiz6eyYWCzoYeL3WV1D56xQsHC57oP8tjX+wRjqixg@mail.gmail.com>
2012-11-14 17:06 ` Gleb Natapov
[not found] ` <CALKiAsHyJykMD+taSBMwikWcMY6bbXT2vqedvnyXNo_+S3vSAw@mail.gmail.com>
2012-11-14 17:35 ` Gleb Natapov
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).