From: "Michael S. Tsirkin" <mst@redhat.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] pci: w1cmask[PCI_BRIDGE_CONTROL] initialized incorrectly
Date: Wed, 26 Jan 2011 14:09:59 +0200 [thread overview]
Message-ID: <20110126120959.GB11913@redhat.com> (raw)
In-Reply-To: <426869a882ff2ab059e7c49e87862658cc29d62c.1296035044.git.yamahata@valinux.co.jp>
On Wed, Jan 26, 2011 at 06:45:27PM +0900, Isaku Yamahata wrote:
> pci_init_wmask_bridge() incorrectly set w1cmask[PCI_BRIDGE_CONTROL].
> This patch removes the line otherwise the assert(!(wmask & w1cmask)) in
> pci_default_write_config() is hit.
>
> Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
Maybe clear in wmask? This bit really should be w1c, should it not?
> ---
> hw/pci.c | 4 ----
> 1 files changed, 0 insertions(+), 4 deletions(-)
>
> diff --git a/hw/pci.c b/hw/pci.c
> index b8f5385..79a46e7 100644
> --- a/hw/pci.c
> +++ b/hw/pci.c
> @@ -643,10 +643,6 @@ static void pci_init_wmask_bridge(PCIDevice *d)
> PCI_BRIDGE_CTL_SEC_DISCARD |
> PCI_BRIDGE_CTL_DISCARD_STATUS |
> PCI_BRIDGE_CTL_DISCARD_SERR);
> - /* Below does not do anything as we never set this bit, put here for
> - * completeness. */
> - pci_set_word(d->w1cmask + PCI_BRIDGE_CONTROL,
> - PCI_BRIDGE_CTL_DISCARD_STATUS);
> }
>
> static int pci_init_multifunction(PCIBus *bus, PCIDevice *dev)
> --
> 1.7.1.1
next prev parent reply other threads:[~2011-01-26 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 9:45 [Qemu-devel] [PATCH] pci: w1cmask[PCI_BRIDGE_CONTROL] initialized incorrectly Isaku Yamahata
2011-01-26 12:09 ` Michael S. Tsirkin [this message]
2011-01-26 13:17 ` [Qemu-devel] " Isaku Yamahata
2011-01-26 13:46 ` Michael S. Tsirkin
2011-01-26 13:53 ` Isaku Yamahata
2011-01-26 13:57 ` Michael S. Tsirkin
2011-01-27 3:54 ` Isaku Yamahata
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=20110126120959.GB11913@redhat.com \
--to=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).