From: Avi Kivity <avi@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCHv2] seabios: enable io/memory unconditionally
Date: Fri, 09 Oct 2009 08:40:58 +0200 [thread overview]
Message-ID: <4ACEDAFA.8070202@redhat.com> (raw)
In-Reply-To: <20091009022953.GA26395@morn.localdomain>
On 10/09/2009 04:29 AM, Kevin O'Connor wrote:
> Hi Michael,
>
> On Thu, Oct 08, 2009 at 05:53:46PM +0200, Michael S. Tsirkin wrote:
>
>> VGA adapters need to claim memory and i/o
>> transactions even if they do not have any
>> i/o or memory bars. E.g. PCI spec, page 297,
>> gives an example of such a device:
>>
>> Programming interface 0000 0000b
>> VGA-compatible controller. Memory
>> addresses 0A 0000h through 0B
>> FFFFh. I/O addresses 3B0h to 3BBh
>> and 3C0h to 3DFh and all aliases of
>> these addresses.
>>
>> While we could check for these devices and special-case them, it is
>> easier to fix this by enabling i/o and memory space unconditionally:
>> devices that do not support it will just ignore this setting.
>>
> This doesn't sound correct to me - I would think the vga option rom
> should enable the memory and io bars. I don't have enough knowledge
> to say for sure though - can someone else with knowledge in this area
> confirm this approach?
>
>
The vga option rom is often itself in a BAR, so it cannot enable memory.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-10-09 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 15:53 [Qemu-devel] [PATCHv2] seabios: enable io/memory unconditionally Michael S. Tsirkin
2009-10-08 16:04 ` [Qemu-devel] " Gleb Natapov
2009-10-09 2:29 ` [Qemu-devel] " Kevin O'Connor
2009-10-09 6:40 ` Avi Kivity [this message]
2009-10-09 6:48 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2009-10-12 9:59 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=4ACEDAFA.8070202@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=mst@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).