similar to: virtio-pci new configuration proposal

Add a flexible mechanism to specify virtio configuration layout, using pci vendor-specific capability. A separate capability is used for each of common, device specific and data-path accesses. Warning: compiled only. This patch also needs to be split up, pci_iomap changes also need arch updates for non-x86. There might also be more spec changes. Posting here for early feedback, and to allow

Add a flexible mechanism to specify virtio configuration layout, using pci vendor-specific capability. A separate capability is used for each of common, device specific and data-path accesses. Warning: compiled only. This patch also needs to be split up, pci_iomap changes also need arch updates for non-x86. There might also be more spec changes. Posting here for early feedback, and to allow

Here's an updated vesion. I'm alternating between updating the spec and the driver, spec update to follow. Compiled only. Posting here for early feedback, and to allow Sasha to proceed with his "kvm tool" work. Changes from v2: address comments by Rusty bugfixes by Sasha Changes from v1: Updated to match v3 of the spec, see: todo: split core changes out Signed-off-by:

Here's an updated vesion. I'm alternating between updating the spec and the driver, spec update to follow. Compiled only. Posting here for early feedback, and to allow Sasha to proceed with his "kvm tool" work. Changes from v2: address comments by Rusty bugfixes by Sasha Changes from v1: Updated to match v3 of the spec, see: todo: split core changes out Signed-off-by:

I Don't speak the language it is in, but is this spam? -----Original Message----- From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org] On Behalf Of SAGLAM SiGORTA Sent: Wednesday, November 14, 2001 10:40 PM To: samba@samba.org Subject: BASA GELEN CEKiLiR DEMEYiN.. Importance: High SA?LAM S?GORTA ARACILIK H?ZMETLER? Merhabalar, Size ?ncelikle firmam?z? tan?tarak

This is a first go at adding support for the modern (based on the 1.0 virtio spec) virtio-pci implementation. kvmtool makes it simple to add additional transports such as this because of it's layering, so we are able to add it as a 3rd (after legacy virtio-pci and virtio-mmio) transport layer, and still allow users to choose to use either the legacy or the modern implementations (but setting

This is a first go at adding support for the modern (based on the 1.0 virtio spec) virtio-pci implementation. kvmtool makes it simple to add additional transports such as this because of it's layering, so we are able to add it as a 3rd (after legacy virtio-pci and virtio-mmio) transport layer, and still allow users to choose to use either the legacy or the modern implementations (but setting

On Tue, Jun 04, 2013 at 03:01:50PM +0930, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > On Mon, Jun 03, 2013 at 09:56:15AM +0930, Rusty Russell wrote: > >> "Michael S. Tsirkin" <mst at redhat.com> writes: > >> > On Thu, May 30, 2013 at 08:53:45AM -0500, Anthony Liguori wrote: > >> >> Rusty

On Tue, Jun 04, 2013 at 03:01:50PM +0930, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > On Mon, Jun 03, 2013 at 09:56:15AM +0930, Rusty Russell wrote: > >> "Michael S. Tsirkin" <mst at redhat.com> writes: > >> > On Thu, May 30, 2013 at 08:53:45AM -0500, Anthony Liguori wrote: > >> >> Rusty

Some setups don't support enabling BAR0 (IO BAR). Reasons range from CPU limitations (e.g. on some powerpc setups) to architecture limmitations (e.g. a setup with >15 PCI bridges, with one virtio device behind each, on x86). PCI Express spec made IO optional, so future guests will disable IO for a device in more and more configurations. This patch makes it possible for host to mirror the

Some setups don't support enabling BAR0 (IO BAR). Reasons range from CPU limitations (e.g. on some powerpc setups) to architecture limmitations (e.g. a setup with >15 PCI bridges, with one virtio device behind each, on x86). PCI Express spec made IO optional, so future guests will disable IO for a device in more and more configurations. This patch makes it possible for host to mirror the

On 11/18/2015 12:52 PM, Gerd Hoffmann wrote: > Hi, > >> Thanks for testing! I didn't even thing about seabios as a testing target. > > Not surprising, support isn't upstream, ran into a bunch of issues[1][2] > last time I tried to combine the two, ran into some issues and nobody > seemed to care, so the seabios patches where just sitting in a branch in > my

On 11/18/2015 12:52 PM, Gerd Hoffmann wrote: > Hi, > >> Thanks for testing! I didn't even thing about seabios as a testing target. > > Not surprising, support isn't upstream, ran into a bunch of issues[1][2] > last time I tried to combine the two, ran into some issues and nobody > seemed to care, so the seabios patches where just sitting in a branch in > my

On 09/21/2014 11:02 AM, Michael S. Tsirkin wrote: > On Sun, Sep 21, 2014 at 09:47:51AM -0400, Sasha Levin wrote: >> > On 09/21/2014 04:09 AM, Michael S. Tsirkin wrote: >>>> > >> The virtio 0.9.5 spec says that ISR is "unused" when in MSI-X mode. I >>>>> > >> > don't think that you can depend on the device to set the

On 09/21/2014 11:02 AM, Michael S. Tsirkin wrote: > On Sun, Sep 21, 2014 at 09:47:51AM -0400, Sasha Levin wrote: >> > On 09/21/2014 04:09 AM, Michael S. Tsirkin wrote: >>>> > >> The virtio 0.9.5 spec says that ISR is "unused" when in MSI-X mode. I >>>>> > >> > don't think that you can depend on the device to set the

On 09/21/2014 04:09 AM, Michael S. Tsirkin wrote: >> The virtio 0.9.5 spec says that ISR is "unused" when in MSI-X mode. I >> > don't think that you can depend on the device to set the configuration >> > changed bit. >> > The virtio 1.0 spec seems to have fixed that. > Yes, virtio 0.9.5 has this bug. But in practice qemu always set this > bit,

On 09/21/2014 04:09 AM, Michael S. Tsirkin wrote: >> The virtio 0.9.5 spec says that ISR is "unused" when in MSI-X mode. I >> > don't think that you can depend on the device to set the configuration >> > changed bit. >> > The virtio 1.0 spec seems to have fixed that. > Yes, virtio 0.9.5 has this bug. But in practice qemu always set this > bit,

From: Dave Airlie <airlied at gmail.com> [ Upstream commit 7854ea0e408d7f2e8faaada1773f3ddf9cb538f5 ] This func ptr here is normally static allocation, but gsp r535 uses a dynamic pointer, so we need to handle that better. This fixes a crash with GSP when you use config=disp=0 to avoid disp problems. Signed-off-by: Dave Airlie <airlied at redhat.com> Link:

On Mi, 2015-11-18 at 23:01 -0500, Sasha Levin wrote: > On 11/18/2015 11:00 PM, Sasha Levin wrote: > > Anyways, I debugged it for a bit a found that seabios attempts to write to > > the notification BAR, I look further tomorrow to narrow it down and fix it. > > Err, *read*, obviously. > > I've never implemented that because the kernel doesn't try to do that (it

On Mi, 2015-11-18 at 23:01 -0500, Sasha Levin wrote: > On 11/18/2015 11:00 PM, Sasha Levin wrote: > > Anyways, I debugged it for a bit a found that seabios attempts to write to > > the notification BAR, I look further tomorrow to narrow it down and fix it. > > Err, *read*, obviously. > > I've never implemented that because the kernel doesn't try to do that (it