All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Isaku Yamahata <yamahata@valinux.co.jp>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Avi Kivity <avi@redhat.com>
Subject: Re: [PATCHv2-RFC 2/2] pci: add standard bridge device
Date: Tue, 21 Feb 2012 09:02:59 +0100	[thread overview]
Message-ID: <4F434FB3.1000006@redhat.com> (raw)
In-Reply-To: <20120220224001.GA22036@redhat.com>

  Hi,

>> This seems to not support 64bit prefetchable memory windows, at least
>> linux doesn't think it does, lspci looks like this:
>>
>> 00:10.0 PCI bridge: Red Hat, Inc. Device 0001 (prog-if 00 [Normal decode])
[ ... ]
>>         Memory behind bridge: f6000000-f60fffff
>>         Prefetchable memory behind bridge: f8000000-fbffffff

> What in the above tells you that 64 bit windows are not supported?

lspci prints 64bit addresses then, like this:

00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 1 (rev 03) (prog-if 00 [Normal decode])
[ ... ]
        I/O behind bridge: 00008000-00008fff
        Memory behind bridge: c0000000-c01fffff
        Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff

> BAR0 is 32 bit non prefetcheable. As far as I can see linux driver
> takes no precautions against access combining that can
> happen with prefetcheable BARs, so non-prefetcheable
> seems safer.

I'm not talking about bar #0, but about the prefetchable memory window
for devices behind the bridge.

cheers,
  Gerd

WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Isaku Yamahata <yamahata@valinux.co.jp>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCHv2-RFC 2/2] pci: add standard bridge device
Date: Tue, 21 Feb 2012 09:02:59 +0100	[thread overview]
Message-ID: <4F434FB3.1000006@redhat.com> (raw)
In-Reply-To: <20120220224001.GA22036@redhat.com>

  Hi,

>> This seems to not support 64bit prefetchable memory windows, at least
>> linux doesn't think it does, lspci looks like this:
>>
>> 00:10.0 PCI bridge: Red Hat, Inc. Device 0001 (prog-if 00 [Normal decode])
[ ... ]
>>         Memory behind bridge: f6000000-f60fffff
>>         Prefetchable memory behind bridge: f8000000-fbffffff

> What in the above tells you that 64 bit windows are not supported?

lspci prints 64bit addresses then, like this:

00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 1 (rev 03) (prog-if 00 [Normal decode])
[ ... ]
        I/O behind bridge: 00008000-00008fff
        Memory behind bridge: c0000000-c01fffff
        Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff

> BAR0 is 32 bit non prefetcheable. As far as I can see linux driver
> takes no precautions against access combining that can
> happen with prefetcheable BARs, so non-prefetcheable
> seems safer.

I'm not talking about bar #0, but about the prefetchable memory window
for devices behind the bridge.

cheers,
  Gerd

  reply	other threads:[~2012-02-21  8:02 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  9:15 [PATCHv2-RFC 0/2] RFC: standard pci bridge device Michael S. Tsirkin
2012-02-13  9:15 ` [Qemu-devel] " Michael S. Tsirkin
2012-02-13  9:15 ` [PATCHv2-RFC 1/2] shpc: standard hot plug controller Michael S. Tsirkin
2012-02-13  9:15   ` [Qemu-devel] " Michael S. Tsirkin
2012-02-13 10:03   ` Isaku Yamahata
2012-02-13 10:03     ` [Qemu-devel] " Isaku Yamahata
2012-02-13 11:49     ` Michael S. Tsirkin
2012-02-13 11:49       ` [Qemu-devel] " Michael S. Tsirkin
2012-02-13 14:30       ` Isaku Yamahata
2012-02-13 14:30         ` [Qemu-devel] " Isaku Yamahata
2012-02-13 14:49         ` Michael S. Tsirkin
2012-02-13 14:49           ` [Qemu-devel] " Michael S. Tsirkin
2012-02-17 13:20   ` Gerd Hoffmann
2012-02-17 13:20     ` [Qemu-devel] " Gerd Hoffmann
2012-02-13  9:16 ` [PATCHv2-RFC 2/2] pci: add standard bridge device Michael S. Tsirkin
2012-02-13  9:16   ` [Qemu-devel] " Michael S. Tsirkin
2012-02-17 13:25   ` Gerd Hoffmann
2012-02-17 13:25     ` [Qemu-devel] " Gerd Hoffmann
2012-02-19 14:57     ` Michael S. Tsirkin
2012-02-19 14:57       ` [Qemu-devel] " Michael S. Tsirkin
2012-02-19 23:44       ` Michael S. Tsirkin
2012-02-19 23:44         ` Michael S. Tsirkin
2012-02-17 13:33   ` Gerd Hoffmann
2012-02-17 13:33     ` [Qemu-devel] " Gerd Hoffmann
2012-02-20 22:40     ` Michael S. Tsirkin
2012-02-20 22:40       ` Michael S. Tsirkin
2012-02-21  8:02       ` Gerd Hoffmann [this message]
2012-02-21  8:02         ` Gerd Hoffmann
2012-02-13  9:33 ` [PATCH RFC] seabios: add OSHP method stub Michael S. Tsirkin
2012-02-13  9:33   ` [Qemu-devel] " Michael S. Tsirkin
2012-02-14  0:34   ` Kevin O'Connor
2012-02-14  0:34     ` [Qemu-devel] " Kevin O'Connor
2012-02-14  0:43     ` Michael S. Tsirkin
2012-02-14  0:43       ` [Qemu-devel] " Michael S. Tsirkin
2012-02-14  0:48       ` Kevin O'Connor
2012-02-14  0:48         ` [Qemu-devel] " Kevin O'Connor
2012-02-14  1:09         ` Michael S. Tsirkin
2012-02-14  1:09           ` [Qemu-devel] " Michael S. Tsirkin
2012-02-14 12:49           ` Paul Brook
2012-02-14 12:49             ` [Qemu-devel] " Paul Brook
2012-02-14 13:37             ` Michael S. Tsirkin
2012-02-14 13:37               ` [Qemu-devel] " Michael S. Tsirkin
2012-02-14 13:47               ` Paul Brook
2012-02-14 13:47                 ` Paul Brook
2012-02-14 14:11                 ` Michael S. Tsirkin
2012-02-14 14:11                   ` Michael S. Tsirkin
2012-02-29 11:25   ` [SeaBIOS] " Gerd Hoffmann
2012-02-29 11:25     ` [Qemu-devel] " Gerd Hoffmann
2012-02-13  9:38 ` [PATCHv2-RFC 0/2] RFC: standard pci bridge device Wen Congyang
2012-02-13  9:38   ` [Qemu-devel] " Wen Congyang
2012-02-13  9:56   ` Michael S. Tsirkin
2012-02-13  9:56     ` [Qemu-devel] " 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=4F434FB3.1000006@redhat.com \
    --to=kraxel@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yamahata@valinux.co.jp \
    /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.