From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Isaku Yamahata <yamahata@valinux.co.jp>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] qemu/pci: optimize pci config handling
Date: Wed, 7 Oct 2009 15:48:53 +0200 [thread overview]
Message-ID: <20091007134853.GA9769@redhat.com> (raw)
In-Reply-To: <4ACC9133.9060903@redhat.com>
On Wed, Oct 07, 2009 at 03:01:39PM +0200, Paolo Bonzini wrote:
> On 10/07/2009 02:33 PM, Michael S. Tsirkin wrote:
>> There's no need to save all of config space before each config cycle:
>> just the 64 byte header is enough for our purposes. This will become
>> more important as we add pci express support, which has 4K config space.
>
> You can even go a step further and save it only if something is actually
> being changed. Untested though.
I'm actively trying to get out of range-checking address.
What you porpose here is certainly more code than we had.
So why is this a good idea?
> Not-quite-signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>
> Paolo
> diff --git a/hw/pci.c b/hw/pci.c
> index 41e99a9..f9959fc 100644
> --- a/hw/pci.c
> +++ b/hw/pci.c
> @@ -541,19 +541,26 @@ uint32_t pci_default_read_config(PCIDevice *d,
>
> void pci_default_write_config(PCIDevice *d, uint32_t addr, uint32_t val, int l)
> {
> - uint8_t orig[PCI_CONFIG_SPACE_SIZE];
> + uint8_t orig[PCI_CONFIG_HEADER_SIZE];
> int i;
>
> - /* not efficient, but simple */
> - memcpy(orig, d->config, PCI_CONFIG_SPACE_SIZE);
> - for(i = 0; i < l && addr < PCI_CONFIG_SPACE_SIZE; val >>= 8, ++i, ++addr) {
> - uint8_t wmask = d->wmask[addr];
> - d->config[addr] = (d->config[addr] & ~wmask) | (val & wmask);
> + /* not efficient, but simple. If modifying the header, save it so we
> + can compare its contents later. */
> + if (addr < sizeof orig) {
> + memcpy(orig, d->config, sizeof orig);
> + }
> +
> + for(i = 0; i < l && addr+i < PCI_CONFIG_SPACE_SIZE; val >>= 8, ++i) {
> + uint8_t wmask = d->wmask[addr+i];
> + d->config[addr+i] = (d->config[addr+i] & ~wmask) | (val & wmask);
> + }
> +
> + if (addr < sizeof orig) {
> + if (memcmp(orig + PCI_BASE_ADDRESS_0, d->config + PCI_BASE_ADDRESS_0, 24)
> + || ((orig[PCI_COMMAND] ^ d->config[PCI_COMMAND])
> + & (PCI_COMMAND_MEMORY | PCI_COMMAND_IO)))
> + pci_update_mappings(d);
> }
> - if (memcmp(orig + PCI_BASE_ADDRESS_0, d->config + PCI_BASE_ADDRESS_0, 24)
> - || ((orig[PCI_COMMAND] ^ d->config[PCI_COMMAND])
> - & (PCI_COMMAND_MEMORY | PCI_COMMAND_IO)))
> - pci_update_mappings(d);
> }
>
> void pci_data_write(void *opaque, uint32_t addr, uint32_t val, int len)
next prev parent reply other threads:[~2009-10-07 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 12:33 [Qemu-devel] [PATCH] qemu/pci: optimize pci config handling Michael S. Tsirkin
2009-10-07 13:01 ` [Qemu-devel] " Paolo Bonzini
2009-10-07 13:48 ` Michael S. Tsirkin [this message]
2009-10-07 14:24 ` Paolo Bonzini
2009-10-07 19:21 ` Michael S. Tsirkin
2009-10-08 8:23 ` Paolo Bonzini
2009-10-08 8:57 ` Michael S. Tsirkin
2009-10-08 0:08 ` Isaku Yamahata
2009-10-08 8:54 ` Michael S. Tsirkin
2009-10-08 9:29 ` Michael S. Tsirkin
2009-10-13 12:17 ` 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=20091007134853.GA9769@redhat.com \
--to=mst@redhat.com \
--cc=pbonzini@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).