From: Anthony Liguori <anthony@codemonkey.ws>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: amit.shah@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH] virtio-pci: fix bus master bug setting on load
Date: Tue, 22 Jun 2010 20:48:00 -0500 [thread overview]
Message-ID: <4C2167D0.3050703@codemonkey.ws> (raw)
In-Reply-To: <20100617151502.9916.3597.stgit@localhost.localdomain>
On 06/17/2010 10:15 AM, Alex Williamson wrote:
> The comment suggests we're checking for the driver in the ready
> state and bus master disabled, but the code is checking that it's
> not in the ready state.
>
> Signed-off-by: Alex Williamson<alex.williamson@redhat.com>
> Found-by: Amit Shah<amit.shah@redhat.com>
>
Applied. Thanks.
Regards,
Anthony Liguori
> ---
>
> hw/virtio-pci.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/hw/virtio-pci.c b/hw/virtio-pci.c
> index e101fa0..7a86a81 100644
> --- a/hw/virtio-pci.c
> +++ b/hw/virtio-pci.c
> @@ -155,7 +155,7 @@ static int virtio_pci_load_config(void * opaque, QEMUFile *f)
>
> /* Try to find out if the guest has bus master disabled, but is
> in ready state. Then we have a buggy guest OS. */
> - if (!(proxy->vdev->status& VIRTIO_CONFIG_S_DRIVER_OK)&&
> + if ((proxy->vdev->status& VIRTIO_CONFIG_S_DRIVER_OK)&&
> !(proxy->pci_dev.config[PCI_COMMAND]& PCI_COMMAND_MASTER)) {
> proxy->bugs |= VIRTIO_PCI_BUG_BUS_MASTER;
> }
>
>
>
>
prev parent reply other threads:[~2010-06-23 1:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 15:15 [Qemu-devel] [PATCH] virtio-pci: fix bus master bug setting on load Alex Williamson
2010-06-17 15:24 ` [Qemu-devel] " Michael S. Tsirkin
2010-06-17 15:57 ` Amit Shah
2010-06-17 16:01 ` Alexander Graf
2010-06-17 16:40 ` Juan Quintela
2010-06-23 1:48 ` Anthony Liguori [this message]
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=4C2167D0.3050703@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=amit.shah@redhat.com \
--cc=mst@redhat.com \
--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).