qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	kvm-devel <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [PATCHv2-repost] pcbios: enable io/memory unconditionally
Date: Wed, 02 Dec 2009 15:28:17 +0200	[thread overview]
Message-ID: <4B166B71.3070306@redhat.com> (raw)
In-Reply-To: <20091130141722.GB25613@redhat.com>

On 11/30/2009 04:17 PM, Michael S. Tsirkin wrote:
> On Thu, Oct 08, 2009 at 05:52:56PM +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.
>
>    

Applied, thanks.

-- 
error compiling committee.c: too many arguments to function

      parent reply	other threads:[~2009-12-02 13:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 15:52 [Qemu-devel] [PATCHv2] pcbios: enable io/memory unconditionally Michael S. Tsirkin
2009-11-30 14:17 ` [Qemu-devel] [PATCHv2-repost] " Michael S. Tsirkin
2009-11-30 14:18   ` [Qemu-devel] " Michael S. Tsirkin
2009-11-30 16:00   ` Anthony Liguori
2009-11-30 16:04     ` Avi Kivity
2009-12-02 12:56       ` Avi Kivity
2009-11-30 16:04     ` Michael S. Tsirkin
2009-12-02 13:28   ` Avi Kivity [this message]

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=4B166B71.3070306@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --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).