similar to: Current bristuff error report

On Mon, 15 Dec 2014, Michael S. Tsirkin wrote: > From: Michael S Tsirkin <mst at redhat.com> > > Virtio drivers should map the part of the range they need, not > necessarily all of it. > To this end, support mapping ranges within BAR on s390. > Since multiple ranges can now be mapped within a BAR, we keep track of > the number of mappings created, and only clear out the

On Mon, 15 Dec 2014, Michael S. Tsirkin wrote: > From: Michael S Tsirkin <mst at redhat.com> > > Virtio drivers should map the part of the range they need, not > necessarily all of it. > To this end, support mapping ranges within BAR on s390. > Since multiple ranges can now be mapped within a BAR, we keep track of > the number of mappings created, and only clear out the

This is on top of 3.19 master + my bugfix patches, and adds virtio 1.0 support to virtio pci. This is 3.20 material I think. Would like to get feedback on s390 change as it's untested. Michael S Tsirkin (2): pci: add pci_iomap_range s390: add pci_iomap_range Michael S. Tsirkin (2): virtio_pci: modern driver virtio_pci: macros for PCI layout offsets. Rusty Russell (1): virtio-pci:

This is on top of 3.19 master + my bugfix patches, and adds virtio 1.0 support to virtio pci. This is 3.20 material I think. Would like to get feedback on s390 change as it's untested. Michael S Tsirkin (2): pci: add pci_iomap_range s390: add pci_iomap_range Michael S. Tsirkin (2): virtio_pci: modern driver virtio_pci: macros for PCI layout offsets. Rusty Russell (1): virtio-pci:

Changes since v2: handling for devices without config space (e.g. rng) reduce # of mappings for VQs These patches seem to work fine on my virtio-1.0 qemu branch. There haven't been any bugs since v2: just minor cleanups and enhancements. QEMU side is still undergoing polishing, but is already testable. Rusty, what do you think? Let's merge these for 3.20? Also - will you be doing that

Changes since v2: handling for devices without config space (e.g. rng) reduce # of mappings for VQs These patches seem to work fine on my virtio-1.0 qemu branch. There haven't been any bugs since v2: just minor cleanups and enhancements. QEMU side is still undergoing polishing, but is already testable. Rusty, what do you think? Let's merge these for 3.20? Also - will you be doing that

From: Michael S Tsirkin <mst at redhat.com> Virtio drivers should map the part of the range they need, not necessarily all of it. To this end, support mapping ranges within BAR on s390. Since multiple ranges can now be mapped within a BAR, we keep track of the number of mappings created, and only clear out the mapping for a BAR when this number reaches 0. Signed-off-by: Michael S. Tsirkin

From: Michael S Tsirkin <mst at redhat.com> Virtio drivers should map the part of the range they need, not necessarily all of it. To this end, support mapping ranges within BAR on s390. Since multiple ranges can now be mapped within a BAR, we keep track of the number of mappings created, and only clear out the mapping for a BAR when this number reaches 0. Signed-off-by: Michael S. Tsirkin

Virtio drivers should map the part of the range they need, not necessarily all of it. To this end, support mapping ranges within BAR on s390. Since multiple ranges can now be mapped within a BAR, we keep track of the number of mappings created, and only clear out the mapping for a BAR when this number reaches 0. Cc: Bjorn Helgaas <bhelgaas at google.com> Cc: linux-pci at vger.kernel.org

Virtio drivers should map the part of the range they need, not necessarily all of it. To this end, support mapping ranges within BAR on s390. Since multiple ranges can now be mapped within a BAR, we keep track of the number of mappings created, and only clear out the mapping for a BAR when this number reaches 0. Cc: Bjorn Helgaas <bhelgaas at google.com> Cc: linux-pci at vger.kernel.org

On Fri, Dec 19, 2014 at 03:13:37PM +0100, Sebastian Ott wrote: > On Mon, 15 Dec 2014, Michael S. Tsirkin wrote: > > From: Michael S Tsirkin <mst at redhat.com> > > > > Virtio drivers should map the part of the range they need, not > > necessarily all of it. > > To this end, support mapping ranges within BAR on s390. > > Since multiple ranges can now be

On Fri, Dec 19, 2014 at 03:13:37PM +0100, Sebastian Ott wrote: > On Mon, 15 Dec 2014, Michael S. Tsirkin wrote: > > From: Michael S Tsirkin <mst at redhat.com> > > > > Virtio drivers should map the part of the range they need, not > > necessarily all of it. > > To this end, support mapping ranges within BAR on s390. > > Since multiple ranges can now be

On Wed, 14 Jan 2015, Michael S. Tsirkin wrote: > Virtio drivers should map the part of the range they need, not > necessarily all of it. > To this end, support mapping ranges within BAR on s390. > Since multiple ranges can now be mapped within a BAR, we keep track of > the number of mappings created, and only clear out the mapping for a BAR > when this number reaches 0. >

On Wed, 14 Jan 2015, Michael S. Tsirkin wrote: > Virtio drivers should map the part of the range they need, not > necessarily all of it. > To this end, support mapping ranges within BAR on s390. > Since multiple ranges can now be mapped within a BAR, we keep track of > the number of mappings created, and only clear out the mapping for a BAR > when this number reaches 0. >

> ata1: port is slow to respond, this delay is known to occur on vacant SATA ports > ata1: port failed to respond (30 secs) > ata1: SRST failed (status 0xFF) > ata1: SRST failed (err_mask=0x100) > ata1: softreset failed, retrying in 5 secs > ata1: SRST failed (status 0xFF) > ata1: SRST failed (err_mask=0x100) > ata1: softreset failed, retrying in 5 secs > ata1: SRST

Hello, I have experienced a dom0 crash where the system became unreachable via the network and the console was unresponsive. I would appreciate help interpretting the logs and any configuration change suggestions. It is a stock Debian Lenny dom0 running xen 3.2.1 with kernel 2.6.26-2-xen-amd64 and an AMD Athlon IIx4 with 4 GB of RAM. It is running 4 VMs. One VM has two PCI NICs being

Hey, just bought an eSATA/USB dual drive docking station and my CentOS 5 can only see one drive at a time... Any one knows if there are specific parameters to set somewhere? Or do I need a more recent kernel (like upgrading to CentOS 6?) The docking is a Sharkoon Quickport Duo v2 + 2 drives + 1 eSATA cable... http://www.sharkoon.com/?q=en/content/sata-quickport-duo-v2 The eSATA controller is an

In this release: - Updates for FreeBSD and Hurd support - Fixed multifunction bridge enumeration - Fixed a crash when no PCI bus exists Full changelog: Adam Jackson (1): libpciaccess 0.15 Alan Coopersmith (2): Update README for gitlab migration Update configure.ac bug URL for gitlab migration Conrad Meyer (1): freebsd: Add !legacy open_device_io implementation Damien

I am trying to get my xterm window under gnome to open with large fonts, with light green foreground and dark green background. I have the following .Xdefaults file contents: $ cat .Xdefaults ! This is a comment ;-) #ifdef COLOR *customization: -color #endif !! Let's cast a wide net, for any app supporting these ! Blink instead of beeping *visualBell: True *scrollTtyOutput: False

The following changes since commit b97f880c8342fd6e49a02c9ef7507a678722b2b3: Merge branch 'for-3.19-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata (2015-01-21 07:54:16 +1200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git tags/virtio-next-for-linus for you to fetch changes up to