From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 5/6] q35: use 64 bit window programmed by guest
Date: Tue, 10 Sep 2013 17:19:06 +0300 [thread overview]
Message-ID: <20130910141906.GB2750@redhat.com> (raw)
In-Reply-To: <20130910161209.327bdab3@nial.usersys.redhat.com>
On Tue, Sep 10, 2013 at 04:12:09PM +0200, Igor Mammedov wrote:
> On Wed, 4 Sep 2013 13:48:40 +0300
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > Detect the 64 bit window programmed by firmware
> > and configure properties accordingly.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > hw/pci-host/q35.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/hw/pci-host/q35.c b/hw/pci-host/q35.c
> > index 3f1d447..5cb1e8a 100644
> > --- a/hw/pci-host/q35.c
> > +++ b/hw/pci-host/q35.c
> > @@ -90,6 +90,9 @@ static void q35_host_get_pci_hole64_start(Object *obj, Visitor *v,
> > Error **errp)
> > {
> > Q35PCIHost *s = Q35_HOST_DEVICE(obj);
> > + PCIHostState *h = PCI_HOST_BRIDGE(obj);
> > +
> > + pci_bus_get_w64_range(h->bus, &s->mch.pci_info.w64);
> Shouldn't be it done at the time when BIOS initializes BAR, to avoid
> inconsistent state in between write and read.
What's inconsistent with what?
We just report the current state.
If you query it during initialization, you get what
has been programmed so far.
> Also missing remapping of existing 64-bit PCI hole alias to a new range.
We shouldn't remap the region - this is not how hardware works.
This property merely reports what BIOS decided to use.
> >
> > visit_type_uint64(v, &s->mch.pci_info.w64.begin, name, errp);
> > }
> > @@ -99,6 +102,9 @@ static void q35_host_get_pci_hole64_end(Object *obj, Visitor *v,
> > Error **errp)
> > {
> > Q35PCIHost *s = Q35_HOST_DEVICE(obj);
> > + PCIHostState *h = PCI_HOST_BRIDGE(obj);
> > +
> > + pci_bus_get_w64_range(h->bus, &s->mch.pci_info.w64);
> ditto
>
> >
> > visit_type_uint64(v, &s->mch.pci_info.w64.end, name, errp);
> > }
next prev parent reply other threads:[~2013-09-10 14:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 10:48 [Qemu-devel] [PATCH 0/6] pci: keep window properties up to date Michael S. Tsirkin
2013-09-04 10:48 ` [Qemu-devel] [PATCH 1/6] q35: make pci window address/size match guest cfg Michael S. Tsirkin
2013-09-10 13:37 ` Igor Mammedov
2013-09-10 13:46 ` Michael S. Tsirkin
2013-09-10 13:46 ` Igor Mammedov
2013-09-10 13:53 ` Michael S. Tsirkin
2013-09-10 14:09 ` Igor Mammedov
2013-09-10 14:16 ` Michael S. Tsirkin
2013-09-10 15:05 ` Igor Mammedov
2013-09-10 15:25 ` Michael S. Tsirkin
2013-09-04 10:48 ` [Qemu-devel] [PATCH 2/6] range: add Range to typedefs Michael S. Tsirkin
2013-09-04 10:48 ` [Qemu-devel] [PATCH 3/6] range: add min/max operations on ranges Michael S. Tsirkin
2013-09-10 9:35 ` Igor Mammedov
2013-09-10 12:51 ` Michael S. Tsirkin
2013-09-04 10:48 ` [Qemu-devel] [PATCH 4/6] pci: add helper to retrieve the 64-bit range Michael S. Tsirkin
2013-09-10 13:40 ` Igor Mammedov
2013-09-10 13:50 ` Michael S. Tsirkin
2013-09-10 17:05 ` Igor Mammedov
2013-09-10 17:28 ` Michael S. Tsirkin
2013-09-04 10:48 ` [Qemu-devel] [PATCH 5/6] q35: use 64 bit window programmed by guest Michael S. Tsirkin
2013-09-10 14:12 ` Igor Mammedov
2013-09-10 14:19 ` Michael S. Tsirkin [this message]
2013-09-04 10:48 ` [Qemu-devel] [PATCH 6/6] piix: " Michael S. Tsirkin
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=20130910141906.GB2750@redhat.com \
--to=mst@redhat.com \
--cc=imammedo@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).