From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Andrew Barnes <umbramalison@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, qemu-devel@nongnu.org
Subject: Re: [IGDVFIO] [PATCH 3/8] RFC and help completing: Intel IGD Direct Assignment with VFIO
Date: Wed, 24 Sep 2014 22:31:43 +0200 [thread overview]
Message-ID: <54232A2F.9020107@redhat.com> (raw)
In-Reply-To: <1411588026.24563.153.camel@ul30vt.home>
Il 24/09/2014 21:47, Alex Williamson ha scritto:
> So the opregion is mapped by a config write on the IGD device itself and
> the other 3 regions, that we know about so far, are mapped via writes to
> the host bridge.
AFAIU the opregion is mapped by the (host) BIOS, that writes the address
to a well-known scratch dword in the configuration space. The host
reads from the dword and finds the opregion that way.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Andrew Barnes <umbramalison@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [IGDVFIO] [PATCH 3/8] RFC and help completing: Intel IGD Direct Assignment with VFIO
Date: Wed, 24 Sep 2014 22:31:43 +0200 [thread overview]
Message-ID: <54232A2F.9020107@redhat.com> (raw)
In-Reply-To: <1411588026.24563.153.camel@ul30vt.home>
Il 24/09/2014 21:47, Alex Williamson ha scritto:
> So the opregion is mapped by a config write on the IGD device itself and
> the other 3 regions, that we know about so far, are mapped via writes to
> the host bridge.
AFAIU the opregion is mapped by the (host) BIOS, that writes the address
to a well-known scratch dword in the configuration space. The host
reads from the dword and finds the opregion that way.
Paolo
next prev parent reply other threads:[~2014-09-24 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 13:20 [IGDVFIO] [PATCH 3/8] RFC and help completing: Intel IGD Direct Assignment with VFIO Andrew Barnes
2014-09-24 13:20 ` [Qemu-devel] " Andrew Barnes
2014-09-24 19:47 ` Alex Williamson
2014-09-24 19:47 ` [Qemu-devel] " Alex Williamson
2014-09-24 20:31 ` Paolo Bonzini [this message]
2014-09-24 20:31 ` Paolo Bonzini
2014-09-24 20:57 ` Alex Williamson
2014-09-24 20:57 ` Alex Williamson
2014-09-24 21:18 ` Paolo Bonzini
2014-09-24 21:18 ` Paolo Bonzini
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=54232A2F.9020107@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=qemu-devel@nongnu.org \
--cc=umbramalison@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.