From: Alex Williamson <alex.williamson@redhat.com>
To: Matt Renzelmann <mjr@cs.wisc.edu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] Align PCI capabilities in pci_find_space
Date: Wed, 26 Sep 2012 10:57:52 -0600 [thread overview]
Message-ID: <1348678672.28860.204.camel@bling.home> (raw)
In-Reply-To: <004401cd9c07$0b36d760$21a48620$@cs.wisc.edu>
On Wed, 2012-09-26 at 11:50 -0500, Matt Renzelmann wrote:
> > >
> > > hw/pci.c | 28 +++++++++++++++++++++-------
> > > 1 files changed, 21 insertions(+), 7 deletions(-)
> > >
> > > diff --git a/hw/pci.c b/hw/pci.c
> > > index f855cf3..2217dda 100644
> > > --- a/hw/pci.c
> > > +++ b/hw/pci.c
> > > @@ -1626,16 +1626,30 @@ PCIDevice *pci_create_simple(PCIBus *bus, int devfn,
> > const char *name)
> > > return pci_create_simple_multifunction(bus, devfn, false, name);
> > > }
> > >
> > > -static int pci_find_space(PCIDevice *pdev, uint8_t size)
> > > +static int pci_find_space(PCIDevice *pdev, uint8_t size, bool include_pcie)
> > > {
> > > - int config_size = pci_config_size(pdev);
> > > + int config_size;
> > > int offset = PCI_CONFIG_HEADER_SIZE;
> > > int i;
> > > - for (i = PCI_CONFIG_HEADER_SIZE; i < config_size; ++i)
> > > - if (pdev->used[i])
> > > - offset = i + 1;
> > > - else if (i - offset + 1 == size)
> > > + uint32_t *dword_used = &pdev->used[PCI_CONFIG_HEADER_SIZE];
> > > +
> > > + if (include_pcie) {
> > > + assert (pci_config_size(pdev) >= PCIE_CONFIG_SPACE_SIZE);
> > > + config_size = PCIE_CONFIG_SPACE_SIZE;
> > > + } else {
> > > + config_size = PCI_CONFIG_SPACE_SIZE;
> > > + }
> > > +
> > > + /* This approach ensures the capability is dword-aligned, as
> > > + required by the PCI specification */
> > > + for (i = PCI_CONFIG_HEADER_SIZE; i < config_size; i += 4, dword_used++)
> > {
> >
> > I don't believe there's ever a case where a driver would want space and
> > not care if it's in standard or extended config space. They'll want one
> > or the other. So we'd be searching two distinct ranges. Thanks,
> >
> > Alex
>
> Ah, that makes sense, so would something like this work? I can re-send as a patch once we've got it.
>
> static int pci_find_space(PCIDevice *pdev, uint8_t size, bool pcie_space)
> {
> int config_base;
> int config_size;
> int offset = PCI_CONFIG_HEADER_SIZE;
> int i;
> uint32_t *dword_used = &pdev->used[PCI_CONFIG_HEADER_SIZE];
This needs to change too.
Is there a different alignment requirement for pcie? Seems like you
might be better off creating some helper like:
pci_find_space(PCIDevice *pdev, unsigned start, unsigned size, unsigned
align)
Then a pci_find_legacy_space and pci_find_express_space could both call
into it. Thanks,
Alex
>
> if (pcie_space) {
> assert (pci_config_size(pdev) >= PCIE_CONFIG_SPACE_SIZE);
> config_base = PCI_CONFIG_SPACE_SIZE;
> config_size = PCIE_CONFIG_SPACE_SIZE;
> } else {
> config_base = PCI_CONFIG_HEADER_SIZE;
> config_size = PCI_CONFIG_SPACE_SIZE;
> }
>
> /* This approach ensures the capability is dword-aligned, as
> required by the PCI specification */
> for (i = config_base; i < config_size; i += 4, dword_used++) {
> if (*dword_used)
> offset = i + 4;
> else if (i - offset + 4 >= size)
> return offset;
> }
>
> return 0;
> }
>
> Thanks for all your help with this,
> Matt
>
> >
> > > + if (*dword_used) {
> > > + offset = i + 4;
> > > + } else if (i - offset + 4 >= size) {
> > > return offset;
> > > + }
> > > + }
> > > +
> > > return 0;
> > > }
> > >
> > > @@ -1826,7 +1840,7 @@ int pci_add_capability(PCIDevice *pdev, uint8_t
> > cap_id,
> > > int i, overlapping_cap;
> > >
> > > if (!offset) {
> > > - offset = pci_find_space(pdev, size);
> > > + offset = pci_find_space(pdev, size, false);
> > > if (!offset) {
> > > return -ENOSPC;
> > > }
> >
> >
>
>
next prev parent reply other threads:[~2012-09-26 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 15:30 [Qemu-devel] [PATCH v3] Align PCI capabilities in pci_find_space mjr
2012-09-26 16:26 ` Alex Williamson
2012-09-26 16:50 ` Matt Renzelmann
2012-09-26 16:57 ` Alex Williamson [this message]
2012-09-26 17:49 ` Matt Renzelmann
2012-09-26 17:55 ` Alex Williamson
2012-09-26 18:02 ` Don Slutz
2012-09-26 18:04 ` Don Slutz
2012-09-26 18:05 ` Matt Renzelmann
2012-09-26 18:15 ` Alex Williamson
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=1348678672.28860.204.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=mjr@cs.wisc.edu \
--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 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).