Displaying 20 results from an estimated 900 matches similar to: "[PATCH] virtio-pci: correctly unregister root device on error"
2007 Dec 21
0
[kvm-devel] [Virtio-for-kvm] [PATCH 05/13] [Mostly resend] virtio additions
From c8a8b56ccb6e12954b4752fd8ca46850fe354741 Mon Sep 17 00:00:00 2001
From: Anthony Liguori <aliguori@us.ibm.com>
Date: Mon, 12 Nov 2007 21:30:26 -0600
Subject: [PATCH] virtio: PCI device
This is a PCI device that implements a transport for virtio. It allows
virtio
devices to be used by QEMU based VMMs like KVM or Xen.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2007 Dec 21
0
[kvm-devel] [Virtio-for-kvm] [PATCH 05/13] [Mostly resend] virtio additions
From c8a8b56ccb6e12954b4752fd8ca46850fe354741 Mon Sep 17 00:00:00 2001
From: Anthony Liguori <aliguori@us.ibm.com>
Date: Mon, 12 Nov 2007 21:30:26 -0600
Subject: [PATCH] virtio: PCI device
This is a PCI device that implements a transport for virtio. It allows
virtio
devices to be used by QEMU based VMMs like KVM or Xen.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2018 Oct 29
1
question for CentOS6.2
Dear CentOS project's member
I hope to decide the following problem with your knowledge.
1.I installed the CentOS6.2 into the DELL PC(https://www.dell.com/support/manuals/jp/ja/jpbsd1/latitude-e7440-ultrabook/late7440om-v3/specifications?guid=guid-247916a5-f1d3-44b2-82b7-f14374bb9a73&lang=en-us) with bootable usb created with CentOS-6.2-x86_64-minimal.iso.
after that.I started the
2011 Mar 10
1
[PATCH 10/21] Staging: hv: Cleanup root device handling
Now we can complete the cleanup of the root device
management. Use the preferred APIs for creating and
managing the root device. As part of this cleanup get rid
of the root device object from vmbus_driver_context.
Signed-off-by: K. Y. Srinivasan <kys at microsoft.com>
Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com>
Signed-off-by: Mike Sterling <mike.sterling at
2011 Mar 10
1
[PATCH 10/21] Staging: hv: Cleanup root device handling
Now we can complete the cleanup of the root device
management. Use the preferred APIs for creating and
managing the root device. As part of this cleanup get rid
of the root device object from vmbus_driver_context.
Signed-off-by: K. Y. Srinivasan <kys at microsoft.com>
Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com>
Signed-off-by: Mike Sterling <mike.sterling at
2011 Mar 10
1
[PATCH 13/21] [PATCH 13/21] Staging: hv: Rename vmbus_driver_context structure
Now that struct vmbus_driver_context is properly
cleaned up, rename this structure appropriately and
cleanup the code.
Signed-off-by: K. Y. Srinivasan <kys at microsoft.com>
Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com>
Signed-off-by: Mike Sterling <mike.sterling at microsoft.com>
Signed-off-by: Abhishek Kane <v-abkane at microsoft.com>
Signed-off-by: Hank
2011 Mar 10
1
[PATCH 13/21] [PATCH 13/21] Staging: hv: Rename vmbus_driver_context structure
Now that struct vmbus_driver_context is properly
cleaned up, rename this structure appropriately and
cleanup the code.
Signed-off-by: K. Y. Srinivasan <kys at microsoft.com>
Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com>
Signed-off-by: Mike Sterling <mike.sterling at microsoft.com>
Signed-off-by: Abhishek Kane <v-abkane at microsoft.com>
Signed-off-by: Hank
2008 Dec 10
6
[PATCH 0/6] Clean up virtio device object handling [was Re: [PATCH] virtio: make PCI devices take a virtio_pci module ref]
(Moved from kvm at vger to virtualization at linux-foundation, changed
subject, cleaned up cc list)
On Wed, 2008-12-10 at 13:02 +0100, Kay Sievers wrote:
> On Wed, Dec 10, 2008 at 10:49, Mark McLoughlin <markmc at redhat.com> wrote:
> > On Tue, 2008-12-09 at 19:16 +0100, Kay Sievers wrote:
> >> On Tue, Dec 9, 2008 at 17:41, Mark McLoughlin <markmc at redhat.com>
2008 Dec 10
6
[PATCH 0/6] Clean up virtio device object handling [was Re: [PATCH] virtio: make PCI devices take a virtio_pci module ref]
(Moved from kvm at vger to virtualization at linux-foundation, changed
subject, cleaned up cc list)
On Wed, 2008-12-10 at 13:02 +0100, Kay Sievers wrote:
> On Wed, Dec 10, 2008 at 10:49, Mark McLoughlin <markmc at redhat.com> wrote:
> > On Tue, 2008-12-09 at 19:16 +0100, Kay Sievers wrote:
> >> On Tue, Dec 9, 2008 at 17:41, Mark McLoughlin <markmc at redhat.com>
2005 Aug 15
0
Unable to load module for TE406P
Hi,
I'm unable to load wct4xxp module for TE406P card.
I've compiled 2.6.13-rc6, got latest CVS (as of today) of zaptel, but
when I try to load the module I get this:
kobject_register failed for Unified t4xxp/t2xxp driver (-13)
[kobject_register+53/73] kobject_register+0x35/0x49
[bus_add_driver+62/153] bus_add_driver+0x3e/0x99
[driver_register+55/58] driver_register+0x37/0x3a
2005 Aug 16
0
Solved: Unable to load module for TE406P
It works out that name "Unified t4xxp/t2xxp driver" is not accepted
anymore by 2.6.13 kernel.
Need to remove "/" for it to load properly
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-
> bounces@lists.digium.com] On Behalf Of Boris Bakchiev
> Sent: Monday, 15 August 2005 18:17
> To:
2008 Dec 05
1
patched kernel addressing timekeeping issues under vmware
People at vmware have provided patches for RHEL 5 that aim to fix
timekeeping issues in vmware guests.
https://bugzilla.redhat.com/show_bug.cgi?id=463573
Description of problem (excerpt) :
"In a virtual environment, timekeeping for RHEL 64 bit kernels can be
problematic, since time is kept by counting timer interrupts for this kernel.
The problem arises when the VM is descheduled for some
2007 Dec 21
1
[kvm-devel] [Virtio-for-kvm] [PATCH 12/13] [Mostly resend] virtio additions
From 20a01e0c24f47e9805a88bebc9310163f99b5e99 Mon Sep 17 00:00:00 2001
From: Dor Laor <dor.laor@qumranet.com>
Date: Sun, 16 Dec 2007 23:35:35 +0200
Subject: [PATCH] Handle module unload Add the device release function.
Signed-off-by: Dor Laor <dor.laor@qumranet.com>
---
drivers/virtio/virtio.c | 7 +++++++
drivers/virtio/virtio_pci.c | 7 +++++++
2 files changed, 14
2007 Dec 21
1
[kvm-devel] [Virtio-for-kvm] [PATCH 12/13] [Mostly resend] virtio additions
From 20a01e0c24f47e9805a88bebc9310163f99b5e99 Mon Sep 17 00:00:00 2001
From: Dor Laor <dor.laor@qumranet.com>
Date: Sun, 16 Dec 2007 23:35:35 +0200
Subject: [PATCH] Handle module unload Add the device release function.
Signed-off-by: Dor Laor <dor.laor@qumranet.com>
---
drivers/virtio/virtio.c | 7 +++++++
drivers/virtio/virtio_pci.c | 7 +++++++
2 files changed, 14
2008 Jan 01
4
zaptel 1.2.22.1 on kernel 2.6.22: wctdm24xxp.ko needs unknown symbol pci_module_init
Hi,
Before I report a bug on http://bugs.digium.com, I
would like to know if someone is seeing the same error
message.
Personally I am not using wctdm24xxp but other modules
such as wcte12xp and wctdm. The latter modules load
fine and are compiled with pci_register_driver as
expected.
The only module that seems to require the deprecated
function pci_module_init is wctdm24xxp.
Is this normal?
2024 Nov 25
2
[PATCH] drm/nouveau: create module debugfs root
Typically DRM drivers use the DRM debugfs root entry. However, since
Nouveau is heading towards a split into a core and a DRM driver, create
a module specific debugfs root directory.
Subsequent patches make use of this new debugfs root in order to store
GSP-RM log bufferes (optionally beyond a device driver binding).
Signed-off-by: Danilo Krummrich <dakr at kernel.org>
---
Unless there are
2009 Jan 03
7
RH devel kernels for Centos repo
Hi,
RH devel kernels from http://people.redhat.com/dzickus/el5/ built
against Centos tree are available here:
http://fs12.vsb.cz/hrb33/el5/hrb-kernel/stable/x86_64/repodata/
http://fs12.vsb.cz/hrb33/el5/hrb-kernel/stable/i386/repodata/
Regards,
David Hrb??
2009 Jun 18
1
One of my servers crashed, need help
Hello all,
I just installed a new beta kernel from Dzickus over at redhat. Rebooting
causes this, no matter what kernel I boot from:
EXT3-fs error: device dm-0: ext3_check_descriptors: Block bitmap for group
5008 not in group (block 167772160)!
EXT3-fs: group dexcriptors corrupted!
Mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
Setuproot: /moving /dev failed: no such
2012 Nov 08
3
[PATCH] virtio: Don't access index after unregister.
Virtio wants to release used indices after the corresponding
virtio device has been unregistered. However, virtio does not
hold an extra reference, giving up its last reference with
device_unregister(), making accessing dev->index afterwards
invalid.
I actually saw problems when testing my (not-yet-merged)
virtio-ccw code:
- device_add virtio-net,id=xxx
-> creates device virtio<n>
2012 Nov 08
3
[PATCH] virtio: Don't access index after unregister.
Virtio wants to release used indices after the corresponding
virtio device has been unregistered. However, virtio does not
hold an extra reference, giving up its last reference with
device_unregister(), making accessing dev->index afterwards
invalid.
I actually saw problems when testing my (not-yet-merged)
virtio-ccw code:
- device_add virtio-net,id=xxx
-> creates device virtio<n>