From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "aliguori@us.ibm.com" <aliguori@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"aik@ozlabs.ru" <aik@ozlabs.ru>
Subject: Re: [PATCH v2 3/4] vfio: vfio-pci device assignment driver
Date: Tue, 14 Aug 2012 22:33:34 +0200 [thread overview]
Message-ID: <502AB61E.9040008@siemens.com> (raw)
In-Reply-To: <1344971368.4683.314.camel@ul30vt.home>
On 2012-08-14 21:09, Alex Williamson wrote:
>>> +static void vfio_map_bar(VFIODevice *vdev, int nr)
>>> +{
>>> + VFIOBAR *bar = &vdev->bars[nr];
>>> + unsigned size = bar->size;
>>> + char name[64];
>>> + uint32_t pci_bar;
>>> + uint8_t type;
>>> + int ret;
>>> +
>>> + /* Skip both unimplemented BARs and the upper half of 64bit BARS. */
>>> + if (!size) {
>>> + return;
>>> + }
>>> +
>>> + snprintf(name, sizeof(name), "VFIO %04x:%02x:%02x.%x BAR %d",
>>> + vdev->host.domain, vdev->host.bus, vdev->host.slot,
>>> + vdev->host.function, nr);
>>> +
>>> + /* Determine what type of BAR this is for registration */
>>> + ret = pread(vdev->fd, &pci_bar, sizeof(pci_bar),
>>> + vdev->config_offset + PCI_BASE_ADDRESS_0 + (4 * nr));
>>> + if (ret != sizeof(pci_bar)) {
>>> + error_report("vfio: Failed to read BAR %d (%s)\n", nr, strerror(errno));
>>> + return;
>>> + }
>>> +
>>> + pci_bar = le32_to_cpu(pci_bar);
>>> + type = pci_bar & (pci_bar & PCI_BASE_ADDRESS_SPACE_IO ?
>>> + ~PCI_BASE_ADDRESS_IO_MASK : ~PCI_BASE_ADDRESS_MEM_MASK);
>>> +
>>> + /* A "slow" read/write mapping underlies all BARs */
>>> + memory_region_init_io(&bar->mem, &vfio_bar_ops, bar, name, size);
>>> + pci_register_bar(&vdev->pdev, nr, type, &bar->mem);
>>> +
>>> + /*
>>> + * We can't mmap areas overlapping the MSIX vector table, so we
>>> + * potentially insert a direct-mapped subregion before and after it.
>>> + */
>>> + if (vdev->msix && vdev->msix->table_bar == nr) {
>>> + size = vdev->msix->table_offset & TARGET_PAGE_MASK;
>>> + }
>>> +
>>> + strncat(name, " mmap", sizeof(name) - strlen(name) - 1);
>>
>> This could generate an unterminated name if we actually have to cut the
>> appended string. You could set name[sizeof(name)-1] = 0.
>
> strncat adds the terminator, that's why we have the -1 so that there's
> space for it. strlen does not include the terminator.
Yep, you are right, forget what I said.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-08-14 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 19:17 [PATCH v2 0/4] VFIO-based PCI device assignment for QEMU 1.2 Alex Williamson
2012-08-02 19:17 ` [PATCH v2 1/4] Update kernel header script to include vfio Alex Williamson
2012-08-02 19:17 ` [PATCH v2 2/4] Update Linux kernel headers Alex Williamson
2012-08-02 19:17 ` [PATCH v2 3/4] vfio: vfio-pci device assignment driver Alex Williamson
2012-08-14 17:40 ` Jan Kiszka
2012-08-14 19:09 ` Alex Williamson
2012-08-14 20:33 ` Jan Kiszka [this message]
2012-08-02 19:17 ` [PATCH v2 4/4] vfio: Enable vfio-pci and mark supported 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=502AB61E.9040008@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--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).