All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
Cc: kvm@vger.kernel.org, guangrong xiao <guangrong.xiao@linux.intel.com>
Subject: Re: SR-PCIM support in KVM
Date: Mon, 31 Oct 2016 04:09:10 -0400 (EDT)	[thread overview]
Message-ID: <2129818337.9626448.1477901350808.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <8520D5D51A55D047800579B0941471982599A856@XAP-PVEXMBX01.xlnx.xilinx.com>

> > > As per the following link:
> > > https://www.linux-kvm.org/images/6/6a/KvmForum2008$kdf2008_7.pdf
> > >
> > > It says that for software based virtual mailbox we require SR-PCIM
> > > support.
> > >
> > > So for this purpose is SR-PCIM implemented as part of KVM ?
> > > Or is there any other method that KVM provides for communication
> > > between PF & VF ?
> > 
> > Hi, SR-IOV is not part of KVM (the virtual machine monitor kernel module).
> > In PCIe terms, when using KVM the "VI" or Virtualization Intermediary is
> > the Linux VFIO driver.  SR-IOV management is split between the PF driver
> > and VFIO.
> 
> Thanks Paolo.
> 
> If Linux VIFO driver acts as VI, as per spec SR-PCIM is "Software responsible
> for the configuration of the SR-IOV capability, management of Physical
> Functions and Virtual Functions" So if we use kvm who does above work of SR-PCIM ?

It's split between VFIO and the PF driver.

> Does VFIO driver provide any methods for PF & VF communication.

No, those are in the PF driver (ixgbe for example).

Paolo

  reply	other threads:[~2016-10-31  8:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 12:03 SR-PCIM support in KVM Bharat Kumar Gogada
2016-10-29 13:42 ` Paolo Bonzini
2016-10-31  6:17   ` Bharat Kumar Gogada
2016-10-31  8:09     ` Paolo Bonzini [this message]
2016-11-02  5:33       ` Bharat Kumar Gogada

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2129818337.9626448.1477901350808.JavaMail.zimbra@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=bharat.kumar.gogada@xilinx.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.