From: Alex Williamson <alex.williamson@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, chrisw@redhat.com
Subject: Re: [PATCH 6/8] device-assignment: Move PCI capabilities to match physical hardware
Date: Fri, 12 Nov 2010 06:53:55 -0700 [thread overview]
Message-ID: <1289570035.2805.73.camel@x201> (raw)
In-Reply-To: <20101112092038.GI7631@redhat.com>
On Fri, 2010-11-12 at 11:20 +0200, Michael S. Tsirkin wrote:
> On Thu, Nov 11, 2010 at 07:56:13PM -0700, Alex Williamson wrote:
> > Now that common PCI code doesn't have a hangup on capabilities
> > being contiguous,
>
> Hmm, this comment confused me : there's no requirement of
> contigious allocations in current code in pci.c, is there?
Exactly, but the code used to have cap.start and cap.length, which
implied it was contiguous. Since those were removed in 5/8, we don't
need to worry about where the physical capabilities land in config
space. Thanks,
Alex
next prev parent reply other threads:[~2010-11-12 13:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 2:54 [PATCH 0/8] PCI capability and device assignment improvements Alex Williamson
2010-11-12 2:55 ` [PATCH 1/8] pci: pci_default_cap_write_config ignores wmask Alex Williamson
2010-11-12 5:22 ` Michael S. Tsirkin
2010-11-12 6:03 ` Alex Williamson
2010-11-12 8:48 ` Michael S. Tsirkin
2010-11-12 15:49 ` Alex Williamson
2010-11-16 16:12 ` Michael S. Tsirkin
2010-11-12 2:55 ` [PATCH 2/8] pci: Remove pci_enable_capability_support() Alex Williamson
2010-11-12 2:55 ` [PATCH 3/8] device-assignment: Use PCI capabilities support Alex Williamson
2010-11-12 2:55 ` [PATCH 4/8] pci: Replace used bitmap with capability byte map Alex Williamson
2010-11-12 5:40 ` Michael S. Tsirkin
2010-11-12 6:07 ` Alex Williamson
2010-11-12 9:02 ` Michael S. Tsirkin
2010-11-12 15:32 ` Alex Williamson
2010-11-12 2:55 ` [PATCH 5/8] pci: Remove cap.length, cap.start, cap.supported Alex Williamson
2010-11-12 2:56 ` [PATCH 6/8] device-assignment: Move PCI capabilities to match physical hardware Alex Williamson
2010-11-12 9:20 ` Michael S. Tsirkin
2010-11-12 13:53 ` Alex Williamson [this message]
2010-11-12 2:56 ` [PATCH 7/8] pci: Pass ID for capability read/write handlers Alex Williamson
2010-11-12 2:56 ` [RFC PATCH 8/8] device-assignment: pass through and stub more PCI caps Alex Williamson
2010-11-12 5:36 ` Michael S. Tsirkin
2010-11-12 6:30 ` Alex Williamson
2010-11-12 9:11 ` Michael S. Tsirkin
2010-11-12 15:42 ` Alex Williamson
2010-11-16 16:08 ` Michael S. Tsirkin
2010-11-12 5:39 ` [PATCH 0/8] PCI capability and device assignment improvements Michael S. Tsirkin
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=1289570035.2805.73.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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.