kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, avi@redhat.com, mst@redhat.com,
	jan.kiszka@siemens.com, shashidhar.patil@gmail.com
Subject: Re: [PATCH v2 0/8] pci-assign: better MSI-X table support
Date: Tue, 7 Feb 2012 18:04:24 -0200	[thread overview]
Message-ID: <20120207200424.GA21646@amt.cnet> (raw)
In-Reply-To: <20120201052203.9843.80792.stgit@bling.home>

On Tue, Jan 31, 2012 at 10:32:15PM -0700, Alex Williamson wrote:
> This series enables better runtime MSI-X table support so
> that we can track vector updates for routing, enabling
> guest interrupt smp_affinity, as well as vectors setup
> after the MSI-X PCI capability is enabled, allowing for
> MSI-X on devices assigned to FreeBSD guests.  Thanks,
> 
> Alex
> 
> v2:
>  - Dropping mem64, we can work on this elsewhere
>  - Fixed MemoryRegionOps to use .valid, tested 8-byte access
>  - Endian conversions when testing MSI-X vector mask bit
>  - Patch description updates
>  - Misc cleanups
> 
> ---
> 
> Alex Williamson (8):
>       pci-assign: Update MSI-X config based on table writes
>       pci-assign: Use MSIX_PAGE_SIZE
>       pci-assign: Allocate entries for all MSI-X vectors
>       pci-assign: Proper initialization for MSI-X table
>       pci-assign: Only calculate maximum MSI-X vector entries once
>       pci-assign: Use struct for MSI-X table
>       pci-assign: Update MSI-X MMIO to Memory API
>       pci-assign: Fix warnings with DEBUG enabled
> 
> 
>  hw/device-assignment.c |  262 +++++++++++++++++++++++++++++-------------------
>  hw/device-assignment.h |   10 ++
>  2 files changed, 169 insertions(+), 103 deletions(-)

Applied, thanks.


      parent reply	other threads:[~2012-02-07 20:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01  5:32 [PATCH v2 0/8] pci-assign: better MSI-X table support Alex Williamson
2012-02-01  5:32 ` [PATCH v2 1/8] pci-assign: Fix warnings with DEBUG enabled Alex Williamson
2012-02-01  5:32 ` [PATCH v2 2/8] pci-assign: Update MSI-X MMIO to Memory API Alex Williamson
2012-02-01  5:32 ` [PATCH v2 3/8] pci-assign: Use struct for MSI-X table Alex Williamson
2012-02-01  5:32 ` [PATCH v2 4/8] pci-assign: Only calculate maximum MSI-X vector entries once Alex Williamson
2012-02-01  5:32 ` [PATCH v2 5/8] pci-assign: Proper initialization for MSI-X table Alex Williamson
2012-02-01  5:32 ` [PATCH v2 6/8] pci-assign: Allocate entries for all MSI-X vectors Alex Williamson
2012-02-01  5:33 ` [PATCH v2 7/8] pci-assign: Use MSIX_PAGE_SIZE Alex Williamson
2012-02-01  5:33 ` [PATCH v2 8/8] pci-assign: Update MSI-X config based on table writes Alex Williamson
2012-02-01  7:22   ` Michael S. Tsirkin
2012-02-01 13:48     ` Alex Williamson
2012-02-01 14:13       ` Jan Kiszka
2012-02-01 15:13       ` Michael S. Tsirkin
2012-02-01  7:25   ` Michael S. Tsirkin
2012-02-01 13:51     ` Alex Williamson
2012-02-07 20:04 ` Marcelo Tosatti [this message]

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=20120207200424.GA21646@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=shashidhar.patil@gmail.com \
    /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 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).