All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: muli@il.ibm.com
Cc: avi@redhat.com, kvm@vger.kernel.org, weidong.han@intel.com,
	benami@il.ibm.com, amit.shah@redhat.com, allen.m.kay@intel.com
Subject: Re: [v10] Userspace patches for PCI device assignment
Date: Thu, 30 Oct 2008 07:44:27 -0500	[thread overview]
Message-ID: <4909AC2B.2010709@codemonkey.ws> (raw)
In-Reply-To: <1225282801-3648-1-git-send-email-muli@il.ibm.com>

muli@il.ibm.com wrote:
> This patchset enables device assignment for KVM hosts for PCI
> devices. It uses the Intel IOMMU by default if available.
>   

This is still broken wrt CPU hotplug.  If a new CPU comes online, it 
won't have it's ioperm mask set correct and it will crash QEMU.  You 
need to keep track of the current ioperm settings and whenever a new 
VCPU comes online, issue an ioperm.

Regards,

Anthony Liguori

> Changes from v9->v10:
>
> - really emove nr_assigned_devices and device_assignment_enabled and
>   other cleanups
>
> Changes from v8->v9 in no particular order:
>
> - fixed DEBUG, removed uneeded headers
> - introduce USE_KVM_DEVICE_ASSIGNMENT modeled after KVM_USE_PIT, per
>   aliguori's suggestion
> - only call term_printf from the monitor
> - implement markmc's suggestions: don't overflow dev->regions, fix
>   disable_iommu bogosity, fix usage and comment with regards to
>   -pcidevice format, and some other bits
>
> Changes from v7->v8 in in particular order:
>
> - various formatting fixes, DEBUG cleanups, cast removals, etc.
> - s/strncpy/snprintf/
> - split initialization in two phases per aliguori's suggestion
> - bail out on errors when we can't limp on
> - do ioperm on every cpu and vcpu (Weidong Han)
> - use pwrite/pread where applicable
> - split r_virtbase into different fields for memory and IO
> - fix destruction of MMIO regions (Disheng Su and Weidong Han)
>
> Changes from v6->v7 in no particular order:
>
> - formatting changes: adhere to qemu style
> - use strncmp, strncpy etc. instead of the insecure ones
> - move from array to linked list
> - change iopl() to ioperm() (Weidong Han)
> - other small changes as suggested during the review of v6.
>   


  parent reply	other threads:[~2008-10-30 12:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 12:19 [v10] Userspace patches for PCI device assignment muli
2008-10-29 12:19 ` [PATCH 1/6] device assignment: add ioctl wrappers muli
2008-10-29 12:19   ` [PATCH 2/6] device assignment: introduce pci_map_irq to get irq nr from pin number muli
2008-10-29 12:19     ` [PATCH 3/6] device assignment: introduce functions to correlate pin number and irq muli
2008-10-29 12:19       ` [PATCH 4/6] device assignment: build vtd.c for Intel IOMMU support muli
2008-10-29 12:20         ` [PATCH 5/6] device assignment: support for assigning PCI devices to guests muli
2008-10-29 12:20           ` [PATCH 6/6] device assignment: support for hot-plugging PCI devices muli
2008-10-29 12:27           ` [PATCH 5/6] device assignment: support for assigning PCI devices to guests Mark McLoughlin
2008-10-29 14:40             ` Muli Ben-Yehuda
2008-10-30 11:29 ` [v10] Userspace patches for PCI device assignment Avi Kivity
2008-10-30 12:44 ` Anthony Liguori [this message]
2008-10-30 13:23   ` Han, Weidong

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=4909AC2B.2010709@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=allen.m.kay@intel.com \
    --cc=amit.shah@redhat.com \
    --cc=avi@redhat.com \
    --cc=benami@il.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=muli@il.ibm.com \
    --cc=weidong.han@intel.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 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.