Hi,
And is it possible to use offset within BAR and/or memory BARs?
If yes I'd strongly prefer this.
What is the point? Do you want place virtio regions and vga framebuffer
in the same pci bar? Why? virtio is mmio and traps into qemu on
access, whereas the vga framebuffer is memory-backed
On Tue, Mar 24, 2015 at 01:08:46PM +0100, Gerd Hoffmann wrote:
virtio-input is basically evdev-events-over-virtio, so this driver isn't
much more than reading configuration from config space and forwarding
incoming events to the linux input layer.
Signed-off-by: Gerd Hoffmann
On Thu, Mar 26, 2015 at 08:12:39AM +0100, Gerd Hoffmann wrote:
On Mi, 2015-03-25 at 18:09 +0100, Michael S. Tsirkin wrote:
On Wed, Mar 25, 2015 at 04:37:16PM +0100, Gerd Hoffmann wrote:
Hi,
BTW can we teach virtio-gpu to look for framebuffer using
virtio pci caps?
The
On Thu, Mar 26, 2015 at 09:42:47AM +0100, Gerd Hoffmann wrote:
Hi,
And is it possible to use offset within BAR and/or memory BARs?
If yes I'd strongly prefer this.
What is the point? Do you want place virtio regions and vga framebuffer
in the same pci bar? Why? virtio is mmio and
pci core now disables msi on probe automatically,
drop this from device-specific code.
Cc: Bjorn Helgaas bhelg...@google.com
Cc: linux-...@vger.kernel.org
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
drivers/virtio/virtio_pci_common.c | 3 ---
1 file changed, 3 deletions(-)
diff --git
virtio-input is basically evdev-events-over-virtio, so this driver isn't
much more than reading configuration from config space and forwarding
incoming events to the linux input layer.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
MAINTAINERS | 6 +
On Thu, Mar 26, 2015 at 12:38:43PM +0100, Gerd Hoffmann wrote:
Hi,
Absolutely, it's pretty common to mix regions in a BAR.
For example, we have virtio kick (ioeventfd backed,
handled in kernel) in same BAR as common and device
specific configuration.
We did the same thing you are
On Thu, Mar 26, 2015 at 11:49:25AM +0100, Gerd Hoffmann wrote:
virtio-input is basically evdev-events-over-virtio, so this driver isn't
much more than reading configuration from config space and forwarding
incoming events to the linux input layer.
Signed-off-by: Gerd Hoffmann
Hi,
Absolutely, it's pretty common to mix regions in a BAR.
For example, we have virtio kick (ioeventfd backed,
handled in kernel) in same BAR as common and device
specific configuration.
We did the same thing you are now doing with the
virtio BAR, and now we have to maintain two code
On Wed, Mar 25, 2015 at 03:53:09PM +0100, Gerd Hoffmann wrote:
Signed-off-by: Dave Airlie airl...@redhat.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
Standard request from my side for new drm drivers (especially if they're
this simple): Can you please update the drivers to
Michael S. Tsirkin m...@redhat.com writes:
On Thu, Mar 26, 2015 at 11:49:25AM +0100, Gerd Hoffmann wrote:
virtio-input is basically evdev-events-over-virtio, so this driver isn't
much more than reading configuration from config space and forwarding
incoming events to the linux input layer.
On Thu, Mar 26, 2015 at 04:07:16PM +0100, Gerd Hoffmann wrote:
Hi,
I don't know. This seems exactly like the kind of thing
we had in mind when we added the virtio pci capability.
For example, we have text in spec that requires drivers
to skip unknown capabilities.
And yes, if
On Wed, Mar 25, 2015 at 03:47:39PM -0400, Konrad Rzeszutek Wilk wrote:
Ah nice. That could be spun out as a seperate patch to optimize the existing
ticket locks I presume.
Yes I suppose we can do something similar for the ticket and patch in
the right increment. We'd need to restructure the
On Mi, 2015-03-25 at 18:09 +0100, Michael S. Tsirkin wrote:
On Wed, Mar 25, 2015 at 04:37:16PM +0100, Gerd Hoffmann wrote:
Hi,
BTW can we teach virtio-gpu to look for framebuffer using
virtio pci caps?
The virtio-gpu driver doesn't matter much here, it doesn't use it
anyway.
Hi,
I don't know. This seems exactly like the kind of thing
we had in mind when we added the virtio pci capability.
For example, we have text in spec that requires drivers
to skip unknown capabilities.
And yes, if bios pokes at a specific bar then we do
need to list this info in the
15 matches
Mail list logo