qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Cao jin <caoj.fnst@cn.fujitsu.com>, qemu-devel@nongnu.org
Cc: stefano.stabellini@eu.citrix.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] bugfix: passing reference instead of value
Date: Tue, 29 Dec 2015 17:25:38 +0100	[thread overview]
Message-ID: <5682B402.7060808@redhat.com> (raw)
In-Reply-To: <568277CD.7040004@cn.fujitsu.com>

>>> Separated from previous "igd-passthru convert to realize" patch. Since
>>> these two don`t have dependency, can send it solely.
>>>
>>> Not test since it is easy to find out if reading carefully, just
>>> compiled.

This patch works but the added conversion to LE is conceptually wrong.
The conversion from LE to CPU and vice versa is already done by
host_pci_config_read and pci_default_write_config.  You don't have it in
host_pci_config_read because the code is not portable and x86 is
little-endian.

Generally, functions that accept/return integers take care themselves of
endianness conversions.

Paolo


>>>   hw/pci-host/piix.c | 10 ++++++----
>>>   1 file changed, 6 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/hw/pci-host/piix.c b/hw/pci-host/piix.c
>>> index 715208b..a9cb983 100644
>>> --- a/hw/pci-host/piix.c
>>> +++ b/hw/pci-host/piix.c
>>> @@ -761,7 +761,7 @@ static const IGDHostInfo igd_host_bridge_infos[] = {
>>>       {0xa8, 4},  /* SNB: base of GTT stolen memory */
>>>   };
>>>
>>> -static int host_pci_config_read(int pos, int len, uint32_t val)
>>> +static int host_pci_config_read(int pos, int len, uint32_t *val)
>>>   {
>>>       char path[PATH_MAX];
>>>       int config_fd;
>>> @@ -784,12 +784,14 @@ static int host_pci_config_read(int pos, int
>>> len, uint32_t val)
>>>           ret = -errno;
>>>           goto out;
>>>       }
>>> +
>>>       do {
>>> -        rc = read(config_fd, (uint8_t *)&val, len);
>>> +        rc = read(config_fd, (uint8_t *)val, len);
>>>       } while (rc < 0 && (errno == EINTR || errno == EAGAIN));
>>>       if (rc != len) {
>>>           ret = -errno;
>>>       }
>>> +
>>>   out:
>>>       close(config_fd);
>>>       return ret;
>>> @@ -805,11 +807,11 @@ static int igd_pt_i440fx_initfn(struct PCIDevice
>>> *pci_dev)
>>>       for (i = 0; i < num; i++) {
>>>           pos = igd_host_bridge_infos[i].offset;
>>>           len = igd_host_bridge_infos[i].len;
>>> -        rc = host_pci_config_read(pos, len, val);
>>> +        rc = host_pci_config_read(pos, len, &val);
>>>           if (rc) {
>>>               return -ENODEV;
>>>           }
>>> -        pci_default_write_config(pci_dev, pos, val, len);
>>> +        pci_default_write_config(pci_dev, pos, cpu_to_le32(val), len);
>>>       }
>>>
>>>       return 0;
>>>
>>
> 

  reply	other threads:[~2015-12-29 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28  4:42 [Qemu-devel] [PATCH v2] bugfix: passing reference instead of value Cao jin
2015-12-29 11:54 ` Cao jin
2015-12-29 12:08   ` Cao jin
2015-12-29 16:25     ` Paolo Bonzini [this message]
2015-12-30  2:57       ` Cao jin

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=5682B402.7060808@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=caoj.fnst@cn.fujitsu.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.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).