From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
"Prasad Joshi" <prasadjoshi124@gmail.com>,
"André Weidemann" <Andre.Weidemann@web.de>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Oswaldo Cadenas" <oswaldo.cadenas@gmail.com>,
"Nikolaev, Maxim" <maxim.nikolaev@siemens.com>
Subject: Re: Graphics pass-through
Date: Wed, 11 May 2011 17:14:31 +0300 [thread overview]
Message-ID: <4DCA99C7.60408@redhat.com> (raw)
In-Reply-To: <4DCA97F5.20106@siemens.com>
On 05/11/2011 05:06 PM, Jan Kiszka wrote:
> >
> > I doubt it. A 64-bit BAR would be configured as 32-bit on an older
> > BIOS, no?
> >
> > I'd guess 64-bit BARs are only needed for large BARs.
> >
>
> The BIOS can't configure the bars to 64 bit as it does not know which
> type of OS (32 or 64 bits) is going to pick them up.
If it's a really large BAR, it has no choice. BTW, a 32-bit OS can
handle 64-bit BARs, all it needs is PAE or PSE-36.
> But maybe 64-bit
> Windows reconfigures the bars before it starts the driver. Would we
> support this?
Yes. qemu doesn't know if it's the BIOS reprogramming the BARs or the
OS. Of course unmap+remap is not a heavily tested code path.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-05-11 16:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikNHRcDquYOL3NhsxkkBYcE48nMyu4+t8t=19e7@mail.gmail.com>
2011-01-25 23:03 ` Fwd: Graphics pass-through Prasad Joshi
2011-01-26 5:12 ` Alex Williamson
2011-01-26 8:17 ` Gerd Hoffmann
2011-01-27 11:56 ` André Weidemann
2011-01-28 0:45 ` Alex Williamson
2011-01-28 17:29 ` André Weidemann
2011-01-28 16:25 ` Alex Williamson
2011-05-05 8:50 ` Jan Kiszka
2011-05-05 15:17 ` Alex Williamson
2011-05-09 11:14 ` Jan Kiszka
2011-05-09 14:29 ` Alex Williamson
2011-05-09 15:02 ` Jan Kiszka
2011-05-09 14:55 ` Prasad Joshi
2011-05-09 15:27 ` Jan Kiszka
2011-05-09 15:40 ` Prasad Joshi
2011-05-09 15:48 ` Alex Williamson
2011-05-09 16:00 ` Jan Kiszka
2011-05-11 11:25 ` Avi Kivity
2011-05-11 13:08 ` Jan Kiszka
2011-05-11 13:26 ` Avi Kivity
2011-05-11 13:50 ` Jan Kiszka
2011-05-11 13:54 ` Avi Kivity
2011-05-11 14:06 ` Jan Kiszka
2011-05-11 14:14 ` Avi Kivity [this message]
2011-05-11 11:23 ` Avi Kivity
2011-05-11 12:31 ` Jan Kiszka
2011-05-10 10:53 ` Gerd Hoffmann
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=4DCA99C7.60408@redhat.com \
--to=avi@redhat.com \
--cc=Andre.Weidemann@web.de \
--cc=alex.williamson@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=maxim.nikolaev@siemens.com \
--cc=oswaldo.cadenas@gmail.com \
--cc=prasadjoshi124@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.