From: Jan Kiszka <jan.kiszka@web.de>
To: David Kiarie <davidkiarie4@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Valentine Sinitsyn <valentine.sinitsyn@gmail.com>,
imammedo@redhat.com, Marcel Apfelbaum <marcel@redhat.com>,
Peter Xu <peterx@redhat.com>
Subject: Re: [Qemu-devel] [V9 1/4] hw/i386: Introduce AMD IOMMU
Date: Tue, 3 May 2016 18:18:05 +0200 [thread overview]
Message-ID: <5728CF3D.30000@web.de> (raw)
In-Reply-To: <CABdVeABO9UW9-FRQKERE3g2UHH7XcXVfLq2z-Jf+TW2cokGLig@mail.gmail.com>
[please shorten too long replies]
On 2016-05-03 18:11, David Kiarie wrote:
> On Sun, May 1, 2016 at 5:14 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
>> On Sat, Apr 30, 2016 at 01:42:40AM +0300, David Kiarie wrote:
>>> +
>>> +#include "hw/hw.h"
>>> +#include "hw/pci/pci.h"
>>> +#include "hw/pci/msi.h"
>>> +#include "hw/sysbus.h"
>>> +#include "sysemu/dma.h"
>>> +
>>> +/* Capability registers */
>>> +#define IOMMU_CAPAB_HEADER 0x00
>>> +#define IOMMU_CAPAB_REV_TYPE 0x02
>>> +#define IOMMU_CAPAB_FLAGS 0x03
>>> +#define IOMMU_CAPAB_BAR_LOW 0x04
>>> +#define IOMMU_CAPAB_BAR_HIGH 0x08
>>> +#define IOMMU_CAPAB_RANGE 0x0C
>>> +#define IOMMU_CAPAB_MISC 0x10
>>> +#define IOMMU_CAPAB_MISC1 0x14
>>
>>
>> Where are all these from? Most seem unused.
>>
>> Pls use AMD_IOMMU_ prefix to avoid polluting global namespace.
>
> Is it okay to move these macros to the amd_iommu.c file or to another
> file since these macros/defines are already prefix with IOMMU.
> Prefixing them with AMD_IOMMU makes them a bit too long I can barely
> write a line of code spanning less than 80 chars.
An alternative prefix: AMDVI (AMD-Vi is also used for "AMD IOMMU").
Jan
next prev parent reply other threads:[~2016-05-03 16:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 22:42 [Qemu-devel] [V9 0/4] AMD IOMMU David Kiarie
2016-04-29 22:42 ` [Qemu-devel] [V9 1/4] hw/i386: Introduce " David Kiarie
2016-05-01 14:14 ` Michael S. Tsirkin
2016-05-03 16:11 ` David Kiarie
2016-05-03 16:18 ` Jan Kiszka [this message]
2016-04-29 22:42 ` [Qemu-devel] [V9 2/4] hw/i386: ACPI table for " David Kiarie
2016-05-01 13:45 ` Michael S. Tsirkin
2016-05-02 8:27 ` David Kiarie
2016-05-02 9:13 ` Igor Mammedov
2016-04-29 22:42 ` [Qemu-devel] [V9 3/4] hw/core: Add AMD IOMMU to machine properties David Kiarie
2016-05-01 9:15 ` Marcel Apfelbaum
[not found] ` <1461969763-5193-5-git-send-email-davidkiarie4@gmail.com>
2016-05-01 9:15 ` [Qemu-devel] [V9 4/4] hw/pci-host: Emulate AMD IOMMU Marcel Apfelbaum
2016-05-01 13:47 ` [Qemu-devel] [V9 0/4] " Michael S. Tsirkin
2016-05-01 14:00 ` Michael S. Tsirkin
2016-05-02 8:33 ` David Kiarie
2016-05-04 6:12 ` Jan Kiszka
2016-05-04 7:05 ` David Kiarie
2016-05-04 7:26 ` Jan Kiszka
2016-05-04 7:39 ` Valentine Sinitsyn
2016-05-04 10:51 ` David Kiarie
2016-05-04 10:58 ` Valentine Sinitsyn
2016-05-04 11:02 ` David Kiarie
2016-05-04 11:05 ` Valentine Sinitsyn
2016-05-05 14:20 ` David Kiarie
-- strict thread matches above, loose matches on Subject: below --
2016-04-24 22:12 David Kiarie
2016-04-24 22:12 ` [Qemu-devel] [V9 1/4] hw/i386: Introduce " David Kiarie
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=5728CF3D.30000@web.de \
--to=jan.kiszka@web.de \
--cc=davidkiarie4@gmail.com \
--cc=imammedo@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=valentine.sinitsyn@gmail.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 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.