public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
	kvm@vger.kernel.org, ddutile@redhat.com, mst@redhat.com,
	chrisw@redhat.com
Subject: Re: [PATCH v2 0/5] Extra capabilities for device assignment
Date: Thu, 09 Dec 2010 09:17:02 -0700	[thread overview]
Message-ID: <1291911422.2926.0.camel@x201> (raw)
In-Reply-To: <4D00F677.3000800@redhat.com>

On Thu, 2010-12-09 at 17:32 +0200, Avi Kivity wrote:
> On 12/09/2010 05:13 PM, Markus Armbruster wrote:
> > Avi Kivity<avi@redhat.com>  writes:
> >
> > >  On 12/06/2010 06:43 PM, Alex Williamson wrote:
> > >>  On Mon, 2010-12-06 at 18:34 +0200, Avi Kivity wrote:
> > >>  >   On 12/06/2010 06:21 PM, Alex Williamson wrote:
> > >>  >   >   v2:
> > >>  >   >     - Reimplement 2/5 to remove more cruft
> > >>  >   >
> > >>  >   >   v1:
> > >>  >   >
> > >>  >   >   Now that we've got PCI capabilities cleaned up and device assignment
> > >>  >   >   using them, we can add more capabilities to be guest visible.  This
> > >>  >   >   adds minimal PCI Express, PCI-X, and Power Management, along with
> > >>  >   >   direct passthrough Vital Product Data and Vendor Specific capabilities.
> > >>  >   >   With this, devices like tg3, bnx2, vxge, and potentially quite a few
> > >>  >   >   others that didn't work previously should be happier.  Thanks,
> > >>  >   >
> > >>  >
> > >>  >   Applied, thanks.  EFAULT is not the best error return, though.
> > >>
> > >>  Do you prefer EBUSY?  Bad address seemed appropriate here, but I'm not
> > >>  attached to it.  Feel free to change it, or I can send a follow-up.
> > >>  Thanks,
> > >
> > >  EBUSY isn't descriptive either, but EFAULT is wrong, it's the syscall
> > >  equivalent of a SEGV, which hasn't happened here.  How I hate errno.h.
> >
> > EEXIST?  EINVAL?
> 
> I guess EINVAL is best ("go read the source code").
> 

Patch sent.  Thanks,

Alex


      reply	other threads:[~2010-12-09 16:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 19:33 [PATCH 0/5] Extra capabilities for device assignment Alex Williamson
2010-12-03 19:33 ` [PATCH 1/5] device-assignment: Fix off-by-one in header check Alex Williamson
2010-12-03 19:33 ` [PATCH 2/5] pci: MSI-X capability is 12 bytes, not 16, MSI is 10 bytes Alex Williamson
2010-12-03 19:37   ` Chris Wright
2010-12-03 19:48     ` Alex Williamson
2010-12-03 19:54       ` Chris Wright
2010-12-03 19:33 ` [PATCH 3/5] pci: Error on PCI capability collisions Alex Williamson
2010-12-03 19:34 ` [PATCH 4/5] device-assignment: Error checking when adding capabilities Alex Williamson
2010-12-03 19:34 ` [PATCH 5/5] device-assignment: pass through and stub more PCI caps Alex Williamson
2010-12-06 16:21 ` [PATCH v2 0/5] Extra capabilities for device assignment Alex Williamson
2010-12-06 16:22   ` [PATCH v2 1/5] device-assignment: Fix off-by-one in header check Alex Williamson
2010-12-06 16:22   ` [PATCH v2 2/5] pci: Remove PCI_CAPABILITY_CONFIG_* Alex Williamson
2010-12-06 16:22   ` [PATCH v2 3/5] pci: Error on PCI capability collisions Alex Williamson
2010-12-06 16:22   ` [PATCH v2 4/5] device-assignment: Error checking when adding capabilities Alex Williamson
2010-12-06 16:23   ` [PATCH v2 5/5] device-assignment: pass through and stub more PCI caps Alex Williamson
2010-12-06 16:34   ` [PATCH v2 0/5] Extra capabilities for device assignment Avi Kivity
2010-12-06 16:43     ` Alex Williamson
2010-12-06 17:03       ` Avi Kivity
2010-12-09 15:13         ` Markus Armbruster
2010-12-09 15:32           ` Avi Kivity
2010-12-09 16:17             ` Alex Williamson [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=1291911422.2926.0.camel@x201 \
    --to=alex.williamson@redhat.com \
    --cc=armbru@redhat.com \
    --cc=avi@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=ddutile@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.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