From: Alex Williamson <alex.williamson@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] pci: split config update for dev assignment
Date: Sun, 14 Nov 2010 21:11:50 -0700 [thread overview]
Message-ID: <1289794310.2805.161.camel@x201> (raw)
In-Reply-To: <20101113212107.GA24071@redhat.com>
On Sat, 2010-11-13 at 23:21 +0200, Michael S. Tsirkin wrote:
> Device assignment in qemu-kvm wants to update
> config array without any side-efects.
> Make it easier to do so.
This isn't exactly true. The change is a side-effect of qemu-kvm
capability support currently being broken wrt wmask. Device assignment
is just trying to make use of it.
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>
> Alex, I think your work on dev assignment will be easier if I apply
> this on qemu.kvm. Right? Let me know.
It might make merging easier, I don't really know how you handle that,
but I wonder if the right (although much more work on my part) is to
push my 8/9 patch down in my queue. That removes
pci_default_cap_write_config, then my current 1/9 patch isn't really
needed and this merge conflict goes away. Let me know. Thanks,
Alex
> hw/pci.c | 12 ++++++++++--
> 1 files changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/hw/pci.c b/hw/pci.c
> index 8f6fcf8..30e1603 100644
> --- a/hw/pci.c
> +++ b/hw/pci.c
> @@ -996,10 +996,10 @@ uint32_t pci_default_read_config(PCIDevice *d,
> return le32_to_cpu(val);
> }
>
> -void pci_default_write_config(PCIDevice *d, uint32_t addr, uint32_t val, int l)
> +static void pci_update_config(PCIDevice *d, uint32_t addr, uint32_t val, int l)
> {
> - int i, was_irq_disabled = pci_irq_disabled(d);
> uint32_t config_size = pci_config_size(d);
> + int i;
>
> for (i = 0; i < l && addr + i < config_size; val >>= 8, ++i) {
> uint8_t wmask = d->wmask[addr + i];
> @@ -1008,6 +1008,14 @@ void pci_default_write_config(PCIDevice *d, uint32_t addr, uint32_t val, int l)
> d->config[addr + i] = (d->config[addr + i] & ~wmask) | (val & wmask);
> d->config[addr + i] &= ~(val & w1cmask); /* W1C: Write 1 to Clear */
> }
> +}
> +
> +void pci_default_write_config(PCIDevice *d, uint32_t addr, uint32_t val, int l)
> +{
> + int was_irq_disabled = pci_irq_disabled(d);
> +
> + pci_update_config(d, addr, val, l);
> +
> if (ranges_overlap(addr, l, PCI_BASE_ADDRESS_0, 24) ||
> ranges_overlap(addr, l, PCI_ROM_ADDRESS, 4) ||
> ranges_overlap(addr, l, PCI_ROM_ADDRESS1, 4) ||
prev parent reply other threads:[~2010-11-15 4:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 21:21 [Qemu-devel] [PATCH] pci: split config update for dev assignment Michael S. Tsirkin
2010-11-15 4:11 ` Alex Williamson [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=1289794310.2805.161.camel@x201 \
--to=alex.williamson@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).