From: Alex Williamson <alex.williamson@redhat.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] vfio/pci: use PCI_MSIX_FLAGS on retrieving the MSIX entries
Date: Fri, 19 Feb 2016 09:45:32 -0700 [thread overview]
Message-ID: <20160219094532.47e2f131@t450s.home> (raw)
In-Reply-To: <1455895091-7589-2-git-send-email-richard.weiyang@gmail.com>
On Fri, 19 Feb 2016 15:18:10 +0000
Wei Yang <richard.weiyang@gmail.com> wrote:
> Even PCI_CAP_FLAGS has the same value as PCI_MSIX_FLAGS, the later one is
> the more proper on retrieving MSIX entries.
>
> This patch uses PCI_MSIX_FLAGS to retrieve the MSIX entries.
>
> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> ---
> hw/vfio/pci.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index e66c47f..321423b 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -1210,7 +1210,7 @@ static int vfio_msix_early_setup(VFIOPCIDevice *vdev)
> }
>
> if (pread(fd, &ctrl, sizeof(ctrl),
> - vdev->config_offset + pos + PCI_CAP_FLAGS) != sizeof(ctrl)) {
> + vdev->config_offset + pos + PCI_MSIX_FLAGS) != sizeof(ctrl)) {
> return -errno;
> }
>
This is certainly trivial, I'll grab it for the respin of yesterday's
pull request. Thanks,
Alex
next prev parent reply other threads:[~2016-02-19 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 15:18 [Qemu-devel] [PATCH 0/2] use PCI_MSIX_FLAGS on retrieving the MSIX entries Wei Yang
2016-02-19 15:18 ` [Qemu-devel] [PATCH 1/2] vfio/pci: " Wei Yang
2016-02-19 16:45 ` Alex Williamson [this message]
2016-02-19 23:38 ` Wei Yang
2016-02-19 15:18 ` [Qemu-devel] [PATCH 2/2] s390x/pci: " Wei Yang
2016-02-22 13:15 ` Christian Borntraeger
2016-02-23 6:17 ` Yi Min Zhao
2016-02-23 22:24 ` Wei Yang
2016-02-24 9:40 ` Cornelia Huck
2016-02-24 14:29 ` Wei Yang
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=20160219094532.47e2f131@t450s.home \
--to=alex.williamson@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.weiyang@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 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).