qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, agraf@suse.de, borntraeger@de.ibm.com,
	zyimin@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2 7/7] s390x/pci: search for subregion inside the BARs
Date: Tue, 21 Nov 2017 11:51:04 +0100	[thread overview]
Message-ID: <20171121115104.77bb4637.cohuck@redhat.com> (raw)
In-Reply-To: <1510854715-7081-8-git-send-email-pmorel@linux.vnet.ibm.com>

On Thu, 16 Nov 2017 18:51:55 +0100
Pierre Morel <pmorel@linux.vnet.ibm.com> wrote:

> When dispatching memory access to PCI BAR region, we must
> look for possible subregions, used by the PCI device to map
> different memory areas inside the same PCI BAR.
> 
> Since the data offset we received is calculated starting at the
> region start address we need to adjust the offset for the subregion.
> 
> The data offset inside the subregion is calculated by substracting
> the subregion's starting address from the data offset in the region.
> 
> The access to the MSIX region is now handled in a generic way,
> we do not need the specific trap_msix() function anymore.
> 
> Signed-off-by: Pierre Morel <pmorel@linux.vnet.ibm.com>
> Reviewed-by: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
> ---
>  hw/s390x/s390-pci-inst.c | 44 +++++++++++++++++++++++++-------------------
>  1 file changed, 25 insertions(+), 19 deletions(-)

This one also looks fine.

  reply	other threads:[~2017-11-21 10:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 17:51 [Qemu-devel] [PATCH v2 0/7] s390x/pci: Improve zPCI to cover more cases Pierre Morel
2017-11-16 17:51 ` [Qemu-devel] [PATCH v2 1/7] s390x/pci: factor out endianess conversion Pierre Morel
2017-11-21 10:35   ` Cornelia Huck
2017-11-21 17:41     ` Pierre Morel
2017-11-16 17:51 ` [Qemu-devel] [PATCH v2 2/7] s390x/pci: rework PCI STORE Pierre Morel
2017-11-21 10:38   ` Cornelia Huck
2017-11-21 14:25     ` Cornelia Huck
2017-11-21 18:03       ` Pierre Morel
2017-11-22 13:25         ` Cornelia Huck
2017-11-22 21:12           ` Pierre Morel
2017-11-21 17:52     ` Pierre Morel
2017-11-16 17:51 ` [Qemu-devel] [PATCH v2 3/7] s390x/pci: rework PCI LOAD Pierre Morel
2017-11-21 10:39   ` Cornelia Huck
2017-11-16 17:51 ` [Qemu-devel] [PATCH v2 4/7] s390x/pci: rework PCI STORE BLOCK Pierre Morel
2017-11-21 10:42   ` Cornelia Huck
2017-11-21 18:07     ` Pierre Morel
2017-11-22  5:15       ` Yi Min Zhao
2017-11-22 13:28         ` Cornelia Huck
2017-11-22 20:37           ` Pierre Morel
2017-11-16 17:51 ` [Qemu-devel] [PATCH v2 5/7] s390x/pci: move the memory region read from pcilg Pierre Morel
2017-11-21 10:48   ` Cornelia Huck
2017-11-16 17:51 ` [Qemu-devel] [PATCH v2 6/7] s390x/pci: move the memory region write from pcistg Pierre Morel
2017-11-21 10:49   ` Cornelia Huck
2017-11-16 17:51 ` [Qemu-devel] [PATCH v2 7/7] s390x/pci: search for subregion inside the BARs Pierre Morel
2017-11-21 10:51   ` Cornelia Huck [this message]
2017-11-21 10:52 ` [Qemu-devel] [PATCH v2 0/7] s390x/pci: Improve zPCI to cover more cases Cornelia Huck
2017-11-21 18:10   ` Pierre Morel

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=20171121115104.77bb4637.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=pmorel@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zyimin@linux.vnet.ibm.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).