From: Alexander Gordeev <agordeev@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: kvm@vger.kernel.org, drjones@redhat.com, jan.kiszka@web.de,
rkrcmar@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH kvm-unit-tests v5 13/14] pci: add msi support for 32/64bit address
Date: Tue, 22 Nov 2016 08:03:06 +0100 [thread overview]
Message-ID: <20161122070306.GA6720@agordeev.lab.eng.brq.redhat.com> (raw)
In-Reply-To: <20161122045920.GA425@pxdev.xzpeter.org>
On Tue, Nov 22, 2016 at 12:59:20PM +0800, Peter Xu wrote:
> On Mon, Nov 21, 2016 at 08:27:52PM +0100, Alexander Gordeev wrote:
>
> [...]
>
> > > +void pci_cap_walk(struct pci_dev *dev)
> > > +{
> > > + uint8_t cap_offset;
> > > + uint8_t cap_id;
> > > +
> > > + cap_offset = pci_config_readb(dev->bdf, PCI_CAPABILITY_LIST);
> > > + while (cap_offset) {
> > > + cap_id = pci_config_readb(dev->bdf, cap_offset);
> > > + printf("PCI detected cap 0x%x\n", cap_id);
> > > + if (cap_handlers[cap_id])
> > > + cap_handlers[cap_id](dev, cap_offset);
> > > + cap_offset = pci_config_readb(dev->bdf, cap_offset + 1);
> > > + }
> > > +}
> >
> > Are you sure the function above is safe without range (sanity) checks?
>
> No. :) But if something goes wrong, I guess that's possibly a QEMU PCI
> bug. I can add some check if you think is necessary, like, make sure
> the loop goes no more than a specific value?
Yes - I suppose PCI cap. list has a limit.
> Thanks,
>
> -- peterx
next prev parent reply other threads:[~2016-11-22 6:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 22:24 [PATCH kvm-unit-tests v5 00/14] VT-d unit test Peter Xu
2016-11-15 22:24 ` [PATCH kvm-unit-tests v5 01/14] pci: fix missing extern for pci_testdev() Peter Xu
2016-11-16 9:26 ` Andrew Jones
2016-11-15 22:24 ` [PATCH kvm-unit-tests v5 02/14] x86/asm: add cpu_relax() Peter Xu
2016-11-15 22:24 ` [PATCH kvm-unit-tests v5 03/14] libcflat: introduce is_power_of_2() Peter Xu
2016-11-15 22:24 ` [PATCH kvm-unit-tests v5 04/14] x86: intel-iommu: add vt-d init test Peter Xu
2016-11-15 22:25 ` [PATCH kvm-unit-tests v5 05/14] libcflat: add IS_ALIGNED() macro, and page sizes Peter Xu
2016-11-15 22:25 ` [PATCH kvm-unit-tests v5 06/14] libcflat: moving MIN/MAX here Peter Xu
2016-11-15 22:25 ` [PATCH kvm-unit-tests v5 07/14] vm/page: provide PGDIR_OFFSET() macro Peter Xu
2016-11-15 22:25 ` [PATCH kvm-unit-tests v5 08/14] pci: introduce struct pci_dev Peter Xu
2016-11-15 22:25 ` [PATCH kvm-unit-tests v5 09/14] pci: provide pci_scan_bars() Peter Xu
2016-11-16 9:50 ` Alexander Gordeev
2016-11-21 7:27 ` Peter Xu
2016-11-21 19:24 ` Alexander Gordeev
2016-11-22 2:16 ` Peter Xu
2016-11-15 22:25 ` [PATCH kvm-unit-tests v5 10/14] pci: provide pci_enable_defaults() Peter Xu
2016-11-15 22:25 ` [PATCH kvm-unit-tests v5 11/14] pci: edu: introduce pci-edu helpers Peter Xu
2016-11-15 22:25 ` [PATCH kvm-unit-tests v5 12/14] x86: intel-iommu: add dmar test Peter Xu
2016-11-15 22:25 ` [PATCH kvm-unit-tests v5 13/14] pci: add msi support for 32/64bit address Peter Xu
2016-11-21 19:27 ` Alexander Gordeev
2016-11-22 4:59 ` Peter Xu
2016-11-22 7:03 ` Alexander Gordeev [this message]
2016-11-22 7:21 ` Peter Xu
2016-11-22 12:30 ` Andrew Jones
2016-11-23 2:40 ` Peter Xu
2016-11-23 10:36 ` Andrew Jones
2016-11-23 10:39 ` Peter Xu
2016-11-15 22:25 ` [PATCH kvm-unit-tests v5 14/14] x86: intel-iommu: add IR MSI test Peter Xu
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=20161122070306.GA6720@agordeev.lab.eng.brq.redhat.com \
--to=agordeev@redhat.com \
--cc=drjones@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=rkrcmar@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;
as well as URLs for NNTP newsgroup(s).