From: Avi Kivity <avi@redhat.com>
To: "Shan, Haitao" <haitao.shan@intel.com>
Cc: "Liu, Kechao" <kechao.liu@intel.com>,
"'kvm@vger.kernel.org'" <kvm@vger.kernel.org>
Subject: Re: [PATCH][v2] kvm-userspace: Load PCI option ROMs
Date: Tue, 30 Dec 2008 17:51:03 +0200 [thread overview]
Message-ID: <495A4367.6050203@redhat.com> (raw)
In-Reply-To: <61563CE63B4F854986A895DA7AD3C177044E6ECA@pdsmsx502.ccr.corp.intel.com>
Shan, Haitao wrote:
>> Well, it may make sense to provide the ROMs as virtual PCI BARs, and
>> have the bios do the work. This way, if some driver relies on
>> remapping the BAR (graphic cards?), it can still work.
>>
>
> I do not quite understand this. Can you elaborate?
>
Which part?
I propose not to copy the card option rom to the bios. Instead, present
the bios as a virtual PCI BAR. The loop that scans the ROMs can then be
moved to the bios.
The advantage is that if a driver needs something in the ROM (mode
tables for graphics), they will be available.
I don't know if any card actually requires this. Maybe all the
information is in the driver.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-12-30 15:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 3:51 [PATCH][v2] kvm-userspace: Load PCI option ROMs Liu, Kechao
2008-12-29 8:28 ` Avi Kivity
2008-12-29 9:36 ` Liu, Kechao
2008-12-29 9:49 ` Avi Kivity
2008-12-30 1:01 ` Shan, Haitao
2008-12-30 15:51 ` Avi Kivity [this message]
2008-12-31 2:06 ` Shan, Haitao
2008-12-31 9:28 ` Avi Kivity
2009-01-03 2:29 ` Shan, Haitao
2009-01-04 2:12 ` Shan, Haitao
2009-01-04 3:54 ` Leendert van Doorn
2009-01-04 4:58 ` Shan, Haitao
2009-01-04 10:26 ` Avi Kivity
2009-01-04 17:12 ` Leendert van Doorn
2009-01-04 17:28 ` Avi Kivity
2009-01-04 17:29 ` Avi Kivity
2009-01-04 17:54 ` Leendert van Doorn
2009-01-04 19:51 ` Avi Kivity
2009-01-04 18:03 ` Kevin O'Connor
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=495A4367.6050203@redhat.com \
--to=avi@redhat.com \
--cc=haitao.shan@intel.com \
--cc=kechao.liu@intel.com \
--cc=kvm@vger.kernel.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